ROAS (Return on Ad Spend) is the revenue generated for every dollar spent on advertising. It's the most direct measure of ad efficiency, expressed as a multiple (4x) or a percentage (400%). Unlike ROI, ROAS uses revenue, not profit — so it tells you how much top-line the ads produced, not how much you kept.
How to calculate ROAS.
Revenue Attributed to Ads ÷ Ad Spend
A $4 return on every $1 of spend is a ROAS of 4x (or 400%). Two things determine whether the number is meaningful for SaaS:
- Which revenue window? For SaaS, you must be explicit. A single month's MRR gives a low first-month ROAS; annualized or lifetime-value (LTV) ROAS is much higher. Comparing monthly-MRR ROAS to annualized ROAS is meaningless.
- Revenue-based vs pixel-based. Ad-platform ROAS is built from pixel conversions (often $0 trial events) and each platform's own attribution window. Revenue-based ROAS uses real revenue — the only version that reflects money you actually earned.
- Revenue-based ROASUses real collected subscription revenue (Stripe MRR/ARR) reconciled against spend.
- Pixel-based ROASUses ad-platform tracking pixels that often over-report and count unbilled trial signups.
ROAS example.
- Revenue attributed
- —
- $20,000
- Ad spend
- —
- $5,000
- ROAS
- $20,000 ÷ $5,000
- 4x (400%)
If that $20,000 is monthly subscription revenue, the annualized ROAS is far higher — always state the revenue window when you report it.
Why ROAS matters for attribution.
ROAS is only as accurate as the revenue you attribute — which makes it fundamentally an attribution metric. The ROAS in your ad platform counts pixel conversions with the platform's own window, so it over-claims and often optimizes toward $0 trial signups. Revenue-based ROAS, tied to real Stripe revenue, is the version you can trust and report.
It's also most useful per channel: a blended ROAS averages your best and worst campaigns into one number that hides where the return actually comes from. Signal Sparrow computes true, revenue-based ROAS by channel from reconciled attribution, alongside CAC and payback — so ROAS becomes a decision you can act on, not a pixel estimate you have to caveat.
