Your 3x campaign ROAS is hiding a product that's losing you £4 on every sale
This is one of the most painful discoveries in DTC: you find out a product you've been scaling has a COGS + shipping + returns cost that means every ad-driven sale is a loss. Campaign ROAS doesn't reveal this because it measures total campaign revenue against total campaign spend — and the high-revenue products mask the loss-making ones. Google Shopping's native reporting gives you campaign-level performance. Seeing it at SKU level requires data you currently don't have in one place.
Solved by Product-Level ROAS — Which products are profitable on ads. Which are draining you.
What Product-Level ROAS does
Standard ad platform ROAS is measured at campaign level. It tells you the campaign returned £X for every £1 spent, but it doesn't tell you which products within that campaign drove the return. Product-Level ROAS connects your Shopify catalogue to your ad spend so you can see exactly which SKUs are profitable on ads, which are breaking even, and which are draining your budget while inflating your revenue numbers.
- SKU-level ROAS tied to actual ad spend
- Shopify product catalogue sync — maps products to campaigns
- ROAS by product, collection, and category
- High-revenue vs high-margin product identification
- Low-margin product flag — products scaling on ROAS but not on profit
- Budget reallocation recommendations by product performance
Works with
Why teams look for a Product-Level ROAS solution
The real operational pain that drives people to Alpomi
Google Ads attributes revenue to the campaign — not to the specific product purchased
No native single-screen view in Google Shopping shows SKU-level profitability
A best-selling product can have a high ROAS but a negative contribution margin
BFCM scaling decisions made without product-level data often fund loss-making SKUs at volume
What you get when you use Product-Level ROAS
Real outcomes from teams using this feature in production
Identify loss-making SKUs before you scale them
Product-level ROAS before you invest — not post-season audit
Budget moves to margin-positive products
Stop funding low-margin SKUs with ad spend that erodes overall profitability
Smarter BFCM product selection
Run peak-period campaigns on products that can support the CAC — not just the ones that sell most units
Before Alpomi vs After Alpomi
From pain to clarity with Product-Level ROAS
Before
Campaign ROAS: 3.2. Looks good. Scale it. Revenue increases. Profit doesn't. Post-season audit reveals one SKU drove 60% of revenue but had a negative margin on every sale. Budget scaled into the wrong product.
With Alpomi
Alpomi: SKU breakdown shows Product A at 5.1 ROAS (margin-positive), Product B at 1.4 ROAS (loss-making at current CPA). Pause spend on Product B. Scale Product A.
Before
New product launch: run a campaign, check overall ROAS. No visibility on whether the new product is performing vs the established SKUs carrying the campaign.
With Alpomi
New product launch: product-level view shows the new SKU is underperforming vs your established range. Keep test budget limited until ROAS improves.
Built for your segment
See how Product-Level ROAS solves problems specific to your business type
For DTC brands
Your best-selling product might be your worst-performing one on ads
High revenue ≠ high margin. The product getting the most clicks might have the lowest margin in your range. Product-Level ROAS shows you the full picture — including which SKUs are profitable to scale and which ones are eating your budget.
- See which products actually generate margin, not just revenue
- Pause ad spend on loss-making SKUs immediately
- Scale campaigns for products where margin supports the CAC
Get started in three steps
Connect Shopify and your ad accounts
We sync your product catalogue and order data from Shopify and match it against spend data from Google Ads and Meta.
Products are mapped to campaigns
Alpomi maps which products were sold through which campaigns using order and product data — SKU-level attribution.
See profitability by product
ROAS at product level. Filter by collection, category, or campaign. Identify what to scale and what to pause.
Frequently asked questions
- Does this work for stores with hundreds of SKUs?
- Yes — you can filter, sort, and group by collection or category so you're not reviewing every SKU individually.
- Does Alpomi need my COGS data to calculate product profitability?
- For product-level ROAS, we use ad spend vs product revenue. For full margin analysis, you can optionally add COGS data — but product-level ROAS is available without it.
- Can I see product-level ROAS during BFCM in real time?
- Yes — data updates every 15 minutes so you can see which products are driving revenue during peak periods.
Explore related features
These features work alongside Product-Level ROAS. See how they fit together.
Ready to see Product-Level ROAS in action?
Book a demo and we'll show you how Product-Level ROAS connects to your stack and solves your reporting and attribution challenges.
Featured Articles
View all
10 Tips for Optimizing Your Facebook Ad Campaigns
Learn how to maximize your ROI with these proven Facebook advertising strategies that top marketers use.
The Complete Guide to Multi-Platform Advertising
Discover how to create cohesive campaigns across Facebook, Google, TikTok, and more for maximum impact.