Ecommerce Analytics to Track Return on Ad Spend by SKU
by Om Rathod
|
10 min read
Jul 10, 2026
To track return on ad spend by SKU using ecommerce analytics, assign ad spend to the specific products it promoted, calculate net revenue from orders attributed to those campaigns by SKU, then divide SKU-level net revenue by the ad spend attributed to it, using margin-adjusted revenue rather than gross revenue where possible. Blended ROAS tells you how the account performed. SKU-level ROAS tells you which products are paying for themselves and which are quietly subsidized by the ones that are.
A campaign running four products with a blended 3.2x ROAS might include one SKU at 6.1x that is cross-subsidizing two SKUs running below 1.5x. The blended number masks this entirely. The SKU-level breakdown is where every profitable scaling and cut decision actually lives.
DEFINITION: Ecommerce Analytics to Track ROAS by SKU
Ecommerce analytics to track return on ad spend by SKU means measuring how much revenue each individual product generates relative to the ad spend specifically promoting it, rather than calculating one blended ROAS across all products and campaigns combined. SKU-level ROAS reveals which products within a campaign are driving profitability and which are diluting it, a distinction that is invisible in account-level or campaign-level reporting.
Why Does Blended Campaign ROAS Hide What You Actually Need to Know?
Because it combines every product's performance into one number that smooths over the range underneath it.
A campaign running a hero product alongside two supporting products often has one SKU at 5-7x ROAS carrying two SKUs at 1-2x. Scaling budget based on the campaign's blended 3x ROAS increases spend on all three equally, pumping more money into the underperformers just as much as the winner. The decision to separate creative and budget by SKU only becomes obvious once the SKU-level data is visible.
The pattern we see consistently: when brands break out ROAS by SKU for the first time, they find that 20-30% of their promoted SKUs account for 70-80% of campaign-level ROAS contribution. Reallocating budget away from the bottom tier of SKUs typically produces an immediate improvement in blended ROAS without requiring any creative change.
How Do You Attribute Ad Spend to a Specific SKU?
Ad spend attribution to SKUs requires connecting campaign-level spend to the product-level orders it generated, which is a different data structure than what most ad platform dashboards show natively.
Tag campaigns by product or SKU using consistent naming conventions or product sets that align directly with specific SKUs. A campaign named "Spring Collection" cannot be attributed to a SKU. A campaign named "SKU-1042 | Retargeting | Meta" can.
Pull product-level conversion data from Shopify order records, matching the SKUs sold in attributed orders to the campaigns that drove those clicks or views.
Assign spend proportionally where campaigns promote multiple SKUs, using revenue contribution as the allocation key rather than splitting spend equally.
Apply the formula: SKU ROAS = (Net revenue from orders containing that SKU and attributed to the campaign) divided by (Ad spend allocated to that SKU's promotion).
This requires connecting ad platform data to order-level Shopify data, which is where most manual attempts at SKU-level ROAS stall.
What Is the Difference Between SKU Revenue ROAS and SKU Margin ROAS?
SKU revenue ROAS compares ad spend to gross revenue. SKU margin ROAS compares ad spend to the gross profit the SKU generates after COGS and channel costs, which is the number that actually matters for profitability decisions.
A SKU with a 4x revenue ROAS but a 30% gross margin generates $1.20 of gross profit per $1 of ad spend. A SKU with a 2.8x revenue ROAS but a 55% gross margin generates $1.54 of gross profit per $1 of ad spend. The second SKU is the better investment despite appearing weaker by the most commonly used ROAS metric.
SKU Margin ROAS formula: (SKU net revenue multiplied by SKU gross margin percentage) divided by SKU-attributed ad spend.
Tracking margin ROAS rather than revenue ROAS changes which SKUs get additional budget and which get cut, often in ways that revenue ROAS would have predicted wrong.
What Return Rate Does to SKU-Level ROAS, and Why It Gets Ignored
Return rate is one of the most important inputs to SKU-level ROAS and one of the least commonly applied.
A SKU with a 12% return rate on a $80 order has an effective net revenue of roughly $70.40 per attributed sale. A SKU with a 3% return rate on the same $80 order has an effective net revenue of $77.60. If both SKUs received the same ad spend, the second SKU's actual ROAS is meaningfully higher, even before margin differences are applied.
Calculate SKU-level ROAS using net revenue after estimated returns, not gross order value. This adjustment alone changes the ranking of SKUs in a typical ROAS comparison, since high-return-rate SKUs consistently look better on pre-return ROAS than post-return.
How Do You Track SKU-Level ROAS Across Amazon and Shopify?
A multi-channel brand promoting the same SKU on both Amazon Sponsored Products and Meta Ads faces an attribution challenge: the same product is being promoted across platforms with different ad structures, different fee environments, and different attribution windows.
Track SKU ROAS separately by channel rather than combining it:
Amazon ROAS by SKU: Amazon provides ASIN-level ad report data through Seller Central or third-party integrations, which maps directly to SKU-level revenue from Sponsored Products campaigns.
Shopify ROAS by SKU: Connect Shopify order line-item data to ad campaign data using UTM parameters and order attribution, then allocate spend to the SKU-level products in each attributed order.
Do not blend the two into one SKU ROAS number, since Amazon's margin profile, including referral and FBA fees, is fundamentally different from Shopify's, and combining them produces a blended ROAS that accurately reflects neither.
Trivas.ai connects to both Amazon and Shopify alongside Meta Ads, Google Ads, TikTok, and 40+ other platforms, enabling SKU-level performance comparison across channels in one reconciled view without separate manual exports.
What Does a Real SKU-Level ROAS Dashboard Look Like?
Here is a simplified example for a brand running four SKUs through the same campaign on Meta:
Revenue ROAS ranks SKU-A first, SKU-B second, SKU-C third, and SKU-D fourth. Margin ROAS produces the same ranking for A and reverses B and C, while revealing D as a negative-margin investment by margin ROAS. SKU-D is consuming $1,600 in monthly ad spend to generate $0.70 of margin per $1 spent, which means the ad is destroying value on every order.
This table produces three immediate decisions: increase SKU-A budget, reduce SKU-B and evaluate whether the high return rate can be fixed, increase SKU-C attention despite lower revenue ROAS given its margin efficiency, and cut or pause SKU-D entirely.
How Often Should SKU-Level ROAS Be Reviewed?
Weekly for active, high-spend SKUs, biweekly or monthly for smaller ones. ROAS at the SKU level can shift quickly with creative fatigue, audience changes, and seasonal return rate fluctuations, and a SKU that ranked well three weeks ago may not still rank well today.
Brands that review SKU-level ROAS monthly typically catch a declining SKU 3-4 weeks after the decline started, which means 3-4 weeks of continued ad spend on a losing SKU. Weekly review catches the same decline within the first 7-10 days.
How Do You Track This Without Manually Joining Three Data Sources Every Week?
Joining Shopify order line items, ad platform campaign data, and return records by SKU into one ROAS calculation manually is a multi-hour project each time it needs to run, which is why most brands default to campaign-level or account-level ROAS and miss the SKU-level story.
A connected platform solves this by linking the data sources automatically. Trivas.ai pulls SKU-level revenue from Shopify, campaign spend and attribution from Meta, Google Ads, TikTok, and Amazon, and generates SKU-level ROAS calculations that update continuously as new order and spend data flows in.
Original Named Framework
THE MARGIN ROAS RANKING: A method for ranking the profitability of promoted SKUs using gross margin-adjusted ROAS rather than revenue ROAS, combined with net revenue after estimated returns rather than gross order value. It works by applying two corrections to the standard ROAS calculation, margin adjustment and return rate adjustment, before ranking SKUs, so budget decisions are based on actual profit generated per ad dollar rather than revenue generated. Brands that switch to Margin ROAS Ranking consistently find their top-revenue SKU and their top-margin SKU are different products, and the budget shift toward margin-first SKUs improves contribution margin within 30-60 days.
Conclusion and CTA
Ecommerce analytics to track return on ad spend by SKU is the difference between knowing your campaign is working and knowing which products within it are actually paying for themselves. Revenue ROAS at the campaign or account level hides both the winners worth scaling and the losers worth cutting. Margin ROAS at the SKU level shows you both.
The founders who make better ad spend decisions are not always running better campaigns. They are often just looking at the same campaign data at the right level of granularity.
Try Trivas.ai free and get clarity on your numbers today: trivas.ai
FAQ Section
How do you track return on ad spend by SKU using ecommerce analytics? Attribute ad spend to specific SKUs using campaign naming conventions and product-level order data, then calculate margin ROAS by dividing gross profit per attributed order by the ad spend allocated to that SKU. Adjust net revenue for estimated return rates before applying the margin calculation.
Why is SKU-level ROAS more useful than blended campaign ROAS? Blended ROAS combines every product's performance into one number, hiding the fact that a small number of SKUs typically generate most of the return while others run at negative or near-zero margin. SKU-level ROAS reveals which specific products deserve more budget and which should be paused.
What is the difference between revenue ROAS and margin ROAS by SKU? Revenue ROAS compares ad spend to gross revenue. Margin ROAS compares ad spend to gross profit after COGS and channel costs. A SKU with lower revenue ROAS but higher gross margin can still generate more actual profit per ad dollar than a SKU with higher revenue ROAS and thin margins.
How does return rate affect SKU-level ROAS calculations? Return rate reduces net revenue per attributed order, which lowers the true ROAS below what gross order value suggests. A SKU with a 12% return rate generates meaningfully less net revenue per sale than a 3% return rate SKU at the same price point, making pre-return ROAS an overstatement for high-return products.
How do you track ROAS by SKU across Amazon and Shopify? Track separately for each channel since the margin profiles differ significantly. Amazon provides ASIN-level ad data through Seller Central. Shopify order line-item data can be matched to ad campaign attribution using UTM parameters. Platforms like Trivas.ai connect both automatically to generate cross-channel SKU-level ROAS without manual data joining.
Can software automate SKU-level ROAS tracking for ecommerce brands? Yes. Trivas.ai connects to Shopify, Amazon, Meta Ads, Google Ads, TikTok, and 40+ other platforms, linking SKU-level revenue from order records to campaign-level ad spend attribution automatically, so margin ROAS by SKU updates continuously without manually joining data sources each week.
How often should SKU-level ROAS be reviewed? Weekly for active, high-spend SKUs. ROAS at the SKU level can shift quickly with creative fatigue, audience changes, and return rate fluctuations. Monthly review typically catches a declining SKU 3-4 weeks after the decline started, meaning weeks of continued ad spend on a product that should have been paused sooner.
What is the first thing to do when a SKU's ROAS drops below target? Check whether the decline is driven by rising ad spend with flat revenue, which suggests audience saturation or creative fatigue, or by increased return rate reducing net revenue without a spend change. These two causes require different fixes: creative refresh for the first, product quality or expectation-setting review for the second.
Ecommerce Analytics to Measure Holiday Season Perf
Revenue growth leader and co-founder driving Trivas's commercial strategy. Om has led the product vision and execution from scratch. With a strong background in SaaS sales and GTM strategy, Om bridges product innovation with real-world customer needs.
Continue Reading
explore more insights
Ecommerce Analytics for Subscription Box Brands: A Guide
3 min read
What is Real-Time Ecommerce Analytics?
3 min read
What Is Proactive Analytics in Ecommerce? (And Why Reactive Reporting Is Costing You Sales)
.d53b12e5.png&w=3840&q=75 "Trivas.ai")
