Platform-Reported ROAS vs. Actual Revenue: How Big Is the Gap for Local Service Google and Meta Campaigns?

Why This Question Matters More Than Your Dashboard Says

Your Google Ads dashboard says 4.2x ROAS. Your Meta Ads Manager says 3.8x. Your bookkeeper sees a slower month.

For local service businesses—HVAC, dental, roofing, law, home services—this gap is not a rounding error. It is a structural feature of how advertising platforms count conversions. Understanding it is the difference between scaling a profitable campaign and doubling down on an illusion.

This is not a platform attack. Google and Meta are useful, often powerful channels. But their attribution systems are optimized to show their contribution, not to give you an unambiguous picture of actual closed revenue. Your job—or your agency's job—is to reconcile the two.

The 4 Structural Reasons Platform ROAS Overstates Real Revenue

1. View-Through Attribution (VTA)

Meta, by default, counts a conversion as a 'result' if someone saw your ad—without clicking it—and then converted within a 1-day window. For local service leads, that means someone who Googled your business name directly, found you on Yelp, or remembered you from a neighbor's referral can get attributed to your Meta campaign. The platform gets credit; the attribution is genuinely ambiguous.

2. Cross-Device and Cross-Session Gaps

A homeowner sees your Google Search ad on desktop at work, closes it, then books through your website on their phone three days later while at home. If your conversion tracking relies on a single cookie or device ID, this conversion may be counted twice (once by Google, once by whatever session originally landed on the booking page) or not at all, depending on your setup. Most small-business Google Tag Manager implementations are not hardened against this.

3. Offline Close Rate Reality

For local service businesses, the conversion a platform counts is almost never a closed job—it is a lead: a form fill, a call, a chat. Platform ROAS is calculated on that lead event, not on whether the person actually booked, showed up, and paid. If your team closes 40% of inbound leads (a rough, common estimate for competitive local service categories), then a platform-reported 4x ROAS based on lead value may translate to closer to 1.6x on actual collected revenue—before accounting for the other issues on this list.

4. Deduplication Failures

When you run Google and Meta simultaneously—as most local advertisers do—a single customer journey often touches both platforms. Google claims the conversion. Meta claims the conversion. You count one paying customer. Your combined platform ROAS is therefore mechanically overstated by however much overlap exists in your customer journeys. This is sometimes called 'double-counting,' and it is the norm, not the exception, in multi-channel local campaigns.

A Labeled Reconciliation Model: Calculating Your Deflation Factor

This model uses illustrative numbers. Plug in your own actuals.

Step 1 — Pull platform-reported conversions over a 30-day window

> Illustrative example: Google reports 80 conversions. Meta reports 60 conversions. Combined platform total: 140 conversions.

Step 2 — Pull your actual lead count from your CRM or call-tracking tool

Count every unique, qualified lead that arrived during the same period, regardless of source.

> Illustrative: CRM shows 90 unique inbound leads.

Your raw deduplication ratio = 90 ÷ 140 = 0.64. The platforms are collectively overcounting by ~36% before you touch revenue.

Step 3 — Apply your offline close rate

> Illustrative: 90 leads × 40% close rate = 36 closed jobs.

Step 4 — Calculate actual revenue

> Illustrative: 36 jobs × $850 average ticket (your real number) = $30,600 actual revenue.

Step 5 — Compare to what platforms implied

If you told both platforms your lead was worth $850 (a common but flawed setup), they reported: > 140 × $850 = $118,900 in 'conversion value'

Your deflation factor = $30,600 ÷ $118,900 = ~0.26. Actual revenue was roughly one-quarter of what the dashboards implied.

The deflation factor formula: ``` Deflation Factor = (Unique CRM Leads × Close Rate × Avg Ticket) ÷ (Platform-Reported Conversions × Per-Conversion Value) ```

For most local service businesses running simultaneous Google and Meta, a deflation factor between 0.25 and 0.55 is a reasonable rough estimate, depending on your category, close rate, and how tightly your conversion tracking is configured. Businesses with stronger CRM discipline and accurate offline conversion imports will sit higher in that range.

What a 'Healthy' Gap Looks Like vs. a Warning Sign

Not every gap signals a problem. Some degree of platform over-reporting is structurally unavoidable. What you are looking for is whether the gap is stable and understood or growing and unexplained.

Signals the gap is manageable:

• Your deflation factor is consistent month over month (±10–15%)
• You can explain the majority of the gap through known attribution windows and a measurable close rate
• Your actual revenue trend correlates with ad spend trend, even if the absolute ROAS numbers differ

Warning signs the gap is a real problem:

• Platform ROAS is climbing while actual booked revenue is flat or falling
• You cannot reconcile more than half of platform-reported conversions to CRM records
• You recently changed attribution windows (e.g., Meta defaulted you from 7-day click to 7-day click + 1-day view) without noticing

This connects directly to a broader principle we cover in *LTV vs CPL: Why Chasing Cheap Leads Kills ROAS*: optimizing for the metric the platform shows you—rather than downstream revenue—creates a compounding misalignment that gets worse as budgets scale.

Three Practical Fixes to Narrow the Gap

1. Import offline conversions

Both Google and Meta support offline conversion imports. When a lead closes in your CRM, that closed-won event gets sent back to the platform. This is the single highest-leverage technical fix available to most local service advertisers. It shifts platform optimization from 'generate leads' to 'generate leads that close.'

2. Use a single source of truth for lead counting

Pick one system—call tracking software, your CRM, or a combined dashboard—and use it as your authoritative conversion count. Platform numbers become reference inputs, not the answer. If you are running seasonal pushes, see *Seasonal Ad Spend vs CPA: Stop Overpaying for Leads* for how this discipline changes budget allocation decisions.

3. Audit attribution settings quarterly

Platforms update default attribution windows. Meta has changed its defaults multiple times in recent years. A quarterly audit—checking your active attribution window in both platforms—catches silent setting changes that inflate your reported numbers without any change in actual performance.

For context on how this applies across different funnel stages, *Cost Per Acquisition by Funnel Stage | Local Business* walks through why the CPA number at the top of funnel rarely predicts CPA at the revenue stage.

The Bottom Line: Use Platform ROAS as a Directional Signal, Not a Revenue Report

Platform-reported ROAS is a useful, real-time signal about ad system efficiency. It is not a revenue report. The structural sources of overstatement—view-through attribution, cross-device gaps, offline close rates, and deduplication failures—are not bugs. They are features of systems designed to measure platform contribution, not business outcomes.

Your reconciliation framework: 1. Pull platform-reported conversions 2. Compare to unique CRM leads 3. Apply your real close rate 4. Calculate actual revenue 5. Divide to get your deflation factor

Track that factor monthly. When it drops sharply, you have an attribution or performance problem worth diagnosing before you scale spend.

Want a second set of eyes on your current attribution setup? Nika Spark runs a structured campaign audit as part of our onboarding process—specifically to surface this kind of gap before it compounds. Book a 20-minute call and we will tell you whether your reported ROAS and your actual revenue are telling the same story.