What is true ROAS?
True ROAS is the revenue your own records tie to your ads, divided by what you actually spent on those ads. "True ROAS" is not a standardized metric. We use the term for a backend-verified version of ROAS: the revenue comes from your orders and payment data instead of an ad platform's pixel, and the spend comes from the platform's billing data.
ROAS (return on ad spend) itself is simple: revenue from ads divided by the cost of those ads. A ROAS of 3.0 means $3 of revenue for every $1 spent.
True ROAS = Revenue from orders your records tie to ads ÷ Actual ad spend
The hard part is not the division. It is deciding which revenue counts. Here is how the ROAS figures you will meet compare:
| Metric | Revenue used | Spend used | Needs attribution? |
|---|---|---|---|
| Platform ROAS (Ads Manager, Google Ads) | Revenue the platform credits to its own ads, using its own window and counting rules | Spend in that platform | Yes, the platform's |
| True ROAS | Orders in your backend that carry a click ID or UTM from the ad | Actual spend from the platform | Yes, but on your data |
| Blended ROAS | All store revenue | All ad spend, every channel | No |
| MER (marketing efficiency ratio) | All store revenue | All marketing spend, including agency, creative and tools | No |
Some teams use blended ROAS and MER interchangeably. We keep them apart because MER counts costs that blended ROAS ignores.
Why platform ROAS and true ROAS differ
Platform ROAS can be wrong in both directions, and the reasons are different.
Why platform ROAS can read too low
The pixel only reports what it sees. Several mechanisms hide real sales from it, and each has been measured on its own:
- Ad blockers. About 29.5% of internet users aged 16+ use one at least sometimes (GWI, Q2 2025). See our ad blocker statistics and the ad blocker loss calculator.
- App Tracking Transparency. Adjust measured a 38% opt-in rate in Q1 2026.
- Safari. It deletes cookies written by scripts after 7 days, and after 1 day when the visit came from a tracked link. Safari and Firefox together supplied 21.0% of page views worldwide and 33.7% in the United States in September 2026 (StatCounter).
- Checkout redirects and cross-device journeys. A person who clicks on a phone and buys on a laptop may not be tied back to the click.
These are the measured pieces. No source we could verify measures the total for a typical store, because it depends on your audience's devices, browsers and consent choices. Our state of conversion tracking report lists each source and what it does and does not show.
Why platform ROAS can read too high
Other effects push the platform's number up:
- View-through credit. Meta's default setting is 7-day click and 1-day view, so it can credit an ad that was seen and not clicked.
- Several platforms claiming the same order. Meta, Google and TikTok each count a conversion if their own ad touched the buyer inside their own window. One order can appear in all three reports. See why Facebook and Google numbers never match.
- Duplicate events. If the pixel and the server both send a purchase without the same
event_id, the platform can count it twice. See our deduplication guide. - Bot conversions and orders that are later refunded, which platform reports usually still include.
A worked example with both effects
These are illustrative numbers. One month, two platforms:
| Measure | Revenue | Spend | ROAS |
|---|---|---|---|
| Meta, as reported | $28,000 | $10,000 | 2.80 |
| Google Ads, as reported | $21,000 | $6,000 | 3.50 |
| Both platforms added together | $49,000 | $16,000 | 3.06 |
| True ROAS (backend orders tied to these ads, each counted once) | $40,000 | $16,000 | 2.50 |
| Blended ROAS (all store revenue, $60,000) | $60,000 | $16,000 | 3.75 |
The two platforms together claim $9,000 more than the backend can tie to their ads, so their combined ROAS (3.06) overstates the true ROAS (2.50). Blended ROAS is higher still because it also includes organic, email, direct and repeat orders. None of the three is "the" answer. They answer different questions.
True ROAS built from click IDs is also a floor for the influence of your ads, because it cannot see a sale that an ad influenced without a click.
And an example where the platform reads too low
Suppose Meta reports 100 purchases, and your order records show 125 orders that came from Meta clicks (each carries an fbclid or Meta UTM). The pixel missed 25 of 125, which is 20% of the true total, and the true ROAS is the reported ROAS times 1.25.
Uplift and loss use different denominators, which trips many people up:
Share the pixel missed (m) = uplift ÷ (1 + uplift)
True ROAS = Reported ROAS × (1 + uplift) = Reported ROAS ÷ (1 − m)
| Uplift over reported conversions | Share the pixel missed | A reported ROAS of 2.0 becomes |
|---|---|---|
| +10% | 9.1% | 2.20 |
| +25% | 20.0% | 2.50 |
| +40% | 28.6% | 2.80 |
| +100% | 50.0% | 4.00 |
Your own uplift has to come from your own comparison of backend orders and platform conversions. To see what a given uplift does to your numbers, and whether a campaign then clears your break-even ROAS, use the free ROAS Recovery Estimator.
How to calculate true ROAS
Step 1: Pick the period and your source of truth for revenue
Use one period, and your store or payment processor as the revenue source. Net out refunds, and decide whether you count tax and shipping. Match whatever the platform sends as the purchase value, or the comparison will not be fair.
Step 2: Tie orders to ads
Capture click IDs (fbclid, gclid, ttclid, msclkid) and UTM parameters on the first page view, store them with the session, and attach them to the order. Our guide to ad click IDs explains what each one carries. Orders that carry a click ID or a paid UTM are the ones you can tie to ads.
Step 3: Count each order once
When two platforms both claim an order, assign it to one of them. Common rules are the last paid click or the most recent click ID captured. The rule matters less than applying it consistently.
Step 4: Pull actual spend
Take spend from each platform's billing data or API, not from a manual spreadsheet. If you want a fully loaded figure, add agency fees, creative production and tooling. In that case you are calculating MER rather than ROAS.
Step 5: Divide at the right level
Campaign True ROAS = Backend revenue tied to the campaign ÷ Spend on the campaign
Channel True ROAS = Backend revenue tied to the channel ÷ Spend on the channel
Blended ROAS = Total store revenue ÷ Total ad spend
MER = Total store revenue ÷ Total marketing spend
MER and blended ROAS need no attribution at all, which is why they work as a sanity check next to channel ROAS. For MER alongside CAC and LTV, see Marketing Efficiency Ratio (MER), CAC & LTV: Beyond ROAS.
Step 6: Calculate true CPA alongside it
True CPA = Actual ad spend ÷ Orders tied to ads (each counted once)
For example, if the platform reports 100 purchases from $5,000 of spend, its CPA is $50. If your records tie 130 orders to those ads, your true CPA is $38.46.
When you review campaigns, a table with these columns keeps both views side by side:
| Column | What it shows |
|---|---|
| Platform ROAS | What the platform reports |
| True ROAS | Backend revenue tied to the campaign ÷ spend |
| True CPA | Spend ÷ backend orders tied to the campaign |
| Actual spend | From the platform's billing data |
| Verified revenue | Orders in your backend that carry the campaign's click ID or UTM |
A large, steady gap between the first two columns is the signal to investigate tracking before you change any budget.
What is break-even ROAS?
Break-even ROAS is the ROAS at which an order pays for its own advertising and nothing more. It depends on your margin before ad spend, which is the share of revenue left after cost of goods, shipping, payment fees and refunds:
Break-even ROAS = 1 ÷ margin before ad spend
Target ROAS = 1 ÷ (margin before ad spend − the profit margin you want)
For example, on a $100 order with $34 of cost of goods, $8 of shipping and packaging, $3 of payment fees and a $5 refund allowance, $50 is left before ads. That is a 50% margin, so the break-even ROAS is 1 ÷ 0.50 = 2.0.
| Margin before ad spend | Break-even ROAS |
|---|---|
| 20% | 5.00 |
| 25% | 4.00 |
| 30% | 3.33 |
| 40% | 2.50 |
| 50% | 2.00 |
| 60% | 1.67 |
| 70% | 1.43 |
If you want a 10% profit margin on a 40% margin product, the target ROAS is 1 ÷ (0.40 − 0.10) = 3.33.
Break-even ROAS applies to the first order. If customers buy again, you can choose to run below it on purpose when lifetime value repays the acquisition cost, but that should be a decision and not an accident. Our MER, CAC and LTV guide covers that case.
What is a good ROAS?
There is no universal good ROAS. A good ROAS is one that clears your break-even ROAS by enough to cover overhead and leave a profit. That depends on margin, repeat purchases and how you value growth.
You will often see 4:1 quoted as a good ROAS. We found no primary source for it, and it only works for some margins. At a 60% margin, a ROAS of 4.0 spends 25 cents of every revenue dollar on ads and leaves 35 cents. At a 25% margin, the same 4.0 leaves nothing.
When you compare ROAS across platforms, check the attribution windows first. Meta defaults to 7-day click and 1-day view, and Google Ads defaults to a 30-day click window for Search and Shopping, so the same sale can be credited to one platform and not the other.
How to use true ROAS in decisions
Run three checks before you pause or scale a campaign on its platform ROAS:
- Compare platform conversions with backend orders for the same period. If the platform reports far fewer orders than your backend ties to the campaign, the ROAS is understated. If it reports more, it is overstated.
- Check the windows and counting rules. A 7-day click and 1-day view number is not comparable with a 30-day click number.
- Check for duplicates and bots. Duplicate purchase events and fake conversions both inflate a ROAS.
Then pick the metric that matches the decision. Use blended ROAS or MER for budget-level decisions, because they need no attribution. Use true ROAS for channel and campaign comparisons. Remember that attributed ROAS, even when it is built on your own data, is not the same as incremental ROAS. Only a holdout or lift test shows what the ads caused.
How to get more accurate inputs
Better inputs make every version of ROAS more reliable:
- Send conversions from your server through Meta CAPI, Google Enhanced Conversions and the TikTok Events API. Browser blockers cannot stop a server event, although consent and the customer details you send still decide what platforms can match.
- Deduplicate with the same
event_idon the pixel and the server event. - Capture click IDs on landing so every order can be tied to the ad that drove it.
- Filter bots before events reach ad platforms. See how bot traffic wastes ad spend.
- Sync spend automatically from each platform's API instead of typing it into a spreadsheet.
How SignalBridge helps
SignalBridge covers these inputs in one platform:
- Server-side tracking: Sends conversions to Meta CAPI, Google Enhanced Conversions and the TikTok Events API
- Automatic ad spend sync: One-click OAuth connects your ad accounts and syncs spend data automatically
- True CPA and ROAS dashboard: Shows campaign-level True ROAS calculated from server-verified conversions and actual spend
- Bot filtering: Removes fake conversions before they inflate your numbers
Common ROAS calculation mistakes
Mistake 1: Comparing different attribution windows
Meta's default is 7-day click and 1-day view. Google Ads uses a 30-day click window for Search and Shopping. If you compare ROAS across platforms without normalizing the windows, the numbers are not comparable.
Fix: Use the same window across platforms when you compare them, or rely on backend data with one consistent rule.
Mistake 2: Counting duplicates
If you run both pixel and server-side tracking without deduplication, you can double-count conversions, which makes ROAS look inflated.
Fix: Send the same event_id through the pixel and the server API so the platform can deduplicate them.
Mistake 3: Ignoring bot conversions
Bot traffic can generate fake events. If a campaign's 100 reported conversions include 15 bot events, its real ROAS is lower than reported.
Fix: Filter bot traffic before it reaches ad platforms.
Mistake 4: Forgetting refunds, tax and shipping
Platform purchase values depend on what your site sends. Many setups send the order total with tax and shipping, and platforms usually keep counting an order after it is refunded.
Fix: Decide what counts as revenue, and use the same definition for platform and backend figures.
Mistake 5: Comparing ROAS across different time periods
Seasonality, promotions and market conditions all move ROAS. Comparing this month with last month without context leads to bad conclusions.
Fix: Compare the same periods year over year, or use rolling averages to smooth out the variation.
FAQ
What is true ROAS?
True ROAS is the revenue your own records tie to your ads, divided by your actual ad spend. It is not a standardized metric. We use it for a backend-verified version of ROAS, built on orders that carry a click ID or UTM and on spend from the platform's billing data, so it does not depend on one platform's pixel or counting rules.
How do I calculate blended ROAS?
Divide total store revenue by total ad spend across all channels. For example, $60,000 of revenue and $16,000 of ad spend gives a blended ROAS of 3.75. It needs no attribution, but it also counts organic, email, direct and repeat orders, so it cannot tell you which channel is working.
What is break-even ROAS and how do I calculate it?
Break-even ROAS is 1 divided by your margin before ad spend. At a 50% margin it is 2.0, at 40% it is 2.5, and at 25% it is 4.0. Below that number, the first order loses money after advertising.
What is a good ROAS for e-commerce?
It depends on your margins. A product with a 70% margin breaks even at a ROAS of about 1.43, while a product with a 30% margin needs 3.33. A good ROAS is one above your break-even by enough to cover overhead and leave a profit. Calculate your break-even ROAS first, then set a target above it.
How much higher is true ROAS than platform ROAS?
It can be higher or lower, and no source we could verify gives a typical gap. Tracking gaps push platform ROAS down. View-through credit, overlapping platforms and duplicate events push it up. Compare your backend orders with platform conversions for the same period to find your own gap.
Can I calculate true ROAS without server-side tracking?
Yes. Compare platform-reported conversions with your actual sales from Shopify, WooCommerce or your payment processor, and tie orders to ads with click IDs and UTMs. Server-side tracking makes the platform's own numbers more complete, but the calculation does not depend on it.
Should I use ROAS or MER (marketing efficiency ratio)?
They answer different questions. ROAS shows how specific campaigns or channels perform. MER shows how your total marketing spend performs against total revenue, with no attribution involved. Use ROAS for campaign-level decisions and MER for budget-level decisions.
Does true ROAS include organic conversions?
No. True ROAS measures ad-driven conversions. Orders are tied to the ad click that started them using click IDs such as gclid, fbclid and ttclid, and organic orders without an ad click are left out. That is correct, because ROAS should reflect ad performance.
Related Reading
- Marketing Efficiency Ratio (MER), CAC & LTV: Beyond ROAS — the blended metrics that sit next to channel ROAS
- E-Commerce KPIs That Actually Matter in 2026 — the wider KPI set that ROAS belongs to
- The State of Conversion Tracking in 2026 — what has been measured about tracking loss, and what has not
- Why Your Ads Are Lying to You (And How to See the Real Numbers) — why platform numbers and your backend disagree
- What Are Assisted Conversions? — which channels help a sale without getting last-click credit
- Marketing Attribution Models Explained — how the credit behind channel ROAS is divided
- Complete Guide to Event Match Quality — how match quality affects the conversion data platforms receive
- Why Your Facebook and Google Ads Numbers Never Match — the attribution problem that distorts cross-platform ROAS
- What is Server-Side Tracking? — the foundation for more complete conversion data
- How to Fix iOS Tracking Issues — recovering the conversions iOS hides from your pixels
- How Bot Traffic Wastes Your Ad Spend — why fake conversions corrupt your ROAS numbers
Ready to See Your True ROAS?
Stop making ad spend decisions on incomplete data. SignalBridge shows you True CPA and True ROAS per campaign, calculated from server-side verified conversions and actual ad spend, not pixel estimates.
Start your 14-day free trial today. No credit card required.
Related Articles
How to Calculate True ROAS for Taboola Campaigns
Calculate true ROAS for Taboola campaigns: Realize conversion value and spend, backend orders tied to tblci, refunds, break-even ROAS and worked examples.
Native Ad Conversion Tracking: Taboola, Outbrain & Beyond
Native ad conversion tracking in 2026: learn how Taboola, Outbrain, MGID and Revcontent click IDs and postbacks work, and why conversions go missing.
