Free
£0/mo
Test the Playbook to Action Board loop before you pick a paid tier.
Connection slots
6Manual syncs / month
8AI credits / month
100- Playbook and Action Board included
- 1 user
- Pro+ cross-domain Playbook on Pro
Sales Domain
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.
Identify loss-making SKUs before you scale them
Budget moves to margin-positive products
Smarter BFCM product selection
What you get
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 ad spend in Insights so you see which SKUs are margin-positive, which break even, and which drain budget—then review Playbook proposed tasks before you reallocate. Multi-touch attribution (first/last/linear/time-decay/position-based; Markov & Shapley when journey volume supports it). Requires Alpomi pixel and sufficient converted journeys.
- 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
Sound familiar?
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
The impact
What you get when you use Product-Level ROAS
What changes when you close the loop on this feature
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
The shift
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.
Who it's for
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
How it works
Get started in three steps
Step 1
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.
Step 2
Products are mapped to campaigns
Alpomi maps which products were sold through which campaigns using order and product data — SKU-level attribution.
Step 3
See profitability by product
ROAS at product level. Filter by collection, category, or campaign. Identify what to scale and what to pause.
FAQ
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 — product-level views refresh on the scheduled sync. Data refreshes on a scheduled sync (typically hourly; near-real-time where connectors allow).
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.
No credit card required
Human-in-the-loop — you approve proposed tasks
Start free. No credit card.
See performance. Decide in Playbook. Act on the Action Board.
Connect your stack on the free tier. Run your first audit. Get a Playbook with ranked priorities. Your team approves tasks before anything runs.
Starter & Pro billing
Most popular
Pro
$470/mo
$350/mo
Early-adopter flat rate
Teams that need cross-domain Playbook, roles, and room to scale.
Connection slots
25Manual syncs / month
60AI credits / month
500- AI Playbook and cross-domain recommendations
- Team workspace with role-based access
Quick setup first, then checkout—stay on Free anytime.
Starter
$250/mo
$120/mo
Early-adopter flat rate
Brands running Google Ads, Meta, and Shopify who have outgrown spreadsheets.
Connection slots
12Manual syncs / month
25AI credits / month
200- Unified marketing dashboard
- Flat fee, no % of ad spend
- Pro+ cross-domain Playbook on Pro
Quick setup first, then checkout—stay on Free anytime.
Featured Articles
Browse all articles
Paid Advertising
The Triple Whale Switching Playbook: Run Both Tools for 2–4 Weeks
12 min read
Week-by-week parallel-run checklist to switch from Triple Whale. Five source-of-truth metrics, go/no-go rules, honest stay scenarios, and cutover steps.
Ecommerce Strategy
Triple Whale vs Polar Analytics vs Northbeam: Which Fits Your GMV Band?
10 min read
Compare Triple Whale, Polar Analytics, and Northbeam by UK GMV band. Matrix, scenarios, job-to-be-done table, and 2-week eval script.
Ecommerce Strategy
Why Your Triple Whale Bill Keeps Climbing (Even When ROAS Flatlines)
11 min read
GMV pricing explained for UK Shopify brands. See illustrative £ bands, hidden costs, flat vs GMV break-even math, and a renewal checklist.