How to Calculate True ROAS (Not the Number Your Ad Platform Shows You)
The ROAS number in your Meta or Google dashboard is not your real ROAS. Understanding the difference is essential for making sound investment decisions in paid acquisition.
Platform-reported ROAS is based on the platform's attribution model, which is inherently biased toward claiming credit. When you make decisions based solely on platform-reported metrics, you're optimizing for numbers that may not reflect reality.
Why platform ROAS lies
Every ad platform has incentives to show you favorable numbers. They want you to keep spending. This doesn't mean they're dishonest—but their attribution models are designed to maximize the credit they can reasonably claim.
Meta uses a default 7-day click, 1-day view attribution window. If someone sees your ad, doesn't click, but converts within 24 hours after viewing, Meta claims credit. Was it the ad? Maybe. Was it the email they received, the retargeting from another platform, or their own direct navigation? Also maybe.
Understanding these dynamics is central to how we approach paid acquisition services for our clients.
Google's conversion tracking similarly claims credit for conversions that may have happened anyway. View-through conversions, cross-device attributions, and modeled conversions all add uncertainty.
The result is that if you add up ROAS across all your platforms, you'll often get a number that exceeds your actual total revenue. Everyone claims credit for the same conversions.
What true ROAS actually requires
True ROAS requires a source of truth outside your ad platforms. This typically means:
First, you need accurate revenue data from your actual commerce or CRM system—not platform estimates. What did you actually collect in revenue, including refunds, chargebacks, and cancellations?
Second, you need properly configured first-party tracking. Server-side conversion APIs help, but they're still platform-reported. You need your own measurement infrastructure.
Third, you need to account for all costs. Platform spend is obvious. But what about creative production, agency fees, landing page costs, and tools? True ROAS should reflect total acquisition cost.
These principles apply broadly, but we see particular impact when working with SaaS and technology companies.
A practical framework for calculation
Start with your commerce or CRM data. What was total revenue from new customers acquired during the measurement period?
Subtract returning customer revenue unless you're specifically measuring retention campaigns. Many businesses conflate new customer acquisition ROAS with total ROAS, which inflates the number.
Calculate total acquisition spend across all channels—not just the platform you're evaluating.
Divide attributed new customer revenue by total acquisition spend. This is your blended ROAS.
For channel-specific ROAS, you need attribution modeling—which is imperfect but better than platform self-reporting. Multi-touch attribution, incrementality testing, or holdout experiments provide more reliable channel-level insights.
Why this matters for scaling
Making scaling decisions based on platform-reported ROAS is dangerous. You might scale a channel that looks profitable at 4x ROAS but is actually contributing at 2x when properly measured. The difference could be the margin that makes or breaks your business.
Conversely, you might underinvest in channels that appear less efficient but are actually driving incremental revenue that other channels claim credit for.
SaaS companies tracking true customer acquisition cost find that proper measurement often reveals very different economics than platform dashboards suggest. The implications for budget allocation are significant.
Building reliable analytics infrastructure is a prerequisite for sound paid acquisition decisions. Without it, you're optimizing for numbers that may not mean what you think they mean.
How This Fits Into Our Work
This framework is part of how we deliver paid acquisition services for teams in SaaS and technology companies. If you're facing similar challenges, we can help you build the infrastructure to address them systematically.
Need more help with this topic?
Contact our team →