Google Ads Conversion Lag Report vs. Reported ROAS: Why Local Service Campaigns Systematically Overstate Performance

The Problem in One Sentence

Your Google Ads ROAS number is a snapshot. Conversions that belong to last week's clicks are still trickling in — and if you optimize, pause, or scale before that trickle finishes, you are flying on incomplete data.

This is not a glitch. It is how attribution works. Google assigns a conversion to the click date, not the conversion date, but the conversion itself may not be recorded until days or weeks later. The gap between click and recorded conversion is conversion lag, and for local service businesses with longer consideration cycles — think HVAC, legal, dental, home remodeling, financial advisory — that lag is long enough to meaningfully distort a two-week performance read.

What Google's Own Lag Reports Show

Google Ads surfaces conversion lag data directly inside your account: Tools → Attribution → Conversion Lag. This report breaks your conversions into buckets by how many days elapsed between the click and the recorded conversion (same day, 1–2 days, 3–7 days, 8–14 days, 15–30 days, 30+ days).

Google has publicly documented that lag distributions vary significantly by industry and conversion action type. For lead-form and phone-call conversions — the primary conversion types for most local service campaigns — a meaningful share of total conversions routinely arrive 7–14 days or more after the originating click. The exact distribution for your account depends on your category and how leads move through your sales process, which is why pulling your own lag report is step one of this framework.

What this means practically: if you pull a ROAS figure covering the last 14 days, some portion of the conversions that will ultimately be attributed to those 14 days have not been recorded yet. Your dashboard is showing you an incomplete numerator.

A Labeled Lag-Adjustment Model (Apply This to Your Account)

Below is an illustrative model — not measured research, but a structured way to think through the math. Plug in your own numbers.

Setup assumptions (illustrative):

• Reporting window pulled: last 14 days
• Reported conversions in that window: 20
• Reported ad spend: $2,000
• Reported revenue (from those 20 conversions): $10,000
• Reported ROAS: 5.0×

Step 1 — Pull your lag distribution. Open the Conversion Lag report. Suppose your account shows (illustrative example):

• Same day / 0–1 day: 40% of conversions
• 2–7 days: 30%
• 8–14 days: 20%
• 15–30 days: 10%

Step 2 — Identify the at-risk share. For a 14-day reporting window, the conversions attributed to days 7–14 of that window have had at most 7 days to be recorded. Based on the distribution above, roughly 30% of their eventual conversions may still be outstanding. Conversions attributed to days 1–6 are more fully baked, but still not complete.

A rough rule of thumb for a 14-day window in a campaign with this lag profile: expect 15–25% of final conversions to still be unrecorded at pull time.

Step 3 — Adjust the numerator downward. If 20 reported conversions represent ~80% of what will ultimately be recorded (illustrative), your lag-adjusted conversion count is closer to 16.

• Lag-adjusted revenue (at same average order value): ~$8,000
• Same $2,000 spend
• Lag-adjusted ROAS: 4.0×

That is a full turn of ROAS — the difference between a campaign that looks like a star and one that looks like a solid performer. Neither read is wrong; they are just measuring different things. The lag-adjusted number is the one you should use before scaling budget.

Step 4 — Build a lag buffer into your decision cadence. For local service businesses with 7–30 day sales cycles, a practical rule is: never make a major budget or bid decision on data younger than 21–30 days, and always cross-reference with your CRM-recorded close dates, not just Google's reported conversions.

Why This Hits Local Service Campaigns Hardest

E-commerce transactions happen at the click. A user sees an ad, visits a product page, and buys — often within minutes. The lag is negligible.

Local service businesses work differently. A homeowner clicks an HVAC ad, fills out a form, waits for a callback, schedules an estimate, and books the job — a sequence that can span 7 to 21 days. Each step in that sequence is an opportunity for lag to accumulate between the click and the recorded conversion.

This is compounded by how many local campaigns use phone-call conversions, which often depend on call duration thresholds (e.g., calls over 60 seconds) being met before Google records them. A call on day 1 that gets returned on day 4 and results in a booked job on day 9 is a conversion that shows up 9 days after the click.

If you are also dealing with geo-radius targeting that's broader than your actual service area, you may be pulling in low-intent leads with longer decision cycles, making lag worse. (See our article Geo-Radius Targeting: Where Expanding Reach Wastes Budget for how radius inflation quietly damages lead quality and, by extension, distorts your lag profile.)

Two Other Places Lag Hides in Your Account

1. Smart Bidding optimization signals. Google's automated bidding strategies (Target ROAS, Maximize Conversions) learn from conversion data. If you are feeding the algorithm a 7-day lookback that is systematically undercounting conversions, Smart Bidding undervalues clicks that eventually convert and may suppress bids on your best-performing segments. This is a secondary cost that rarely shows up in reporting. Our article Manual vs. Automated Budget Delivery: Hidden CPA Cost covers how automation assumptions interact with incomplete data in more depth.

2. Landing page quality obscured by lag. When reported ROAS looks strong, teams rarely audit the landing page. But if lag-adjusted conversion rates are lower than the raw number suggests, a weak landing page may be partially responsible. Mismatched ad-to-page messaging is a common silent leak — covered in What a Mismatched Ad-to-Landing Page Costs You.

A Simple 3-Step Lag Audit Checklist

Run this once a month before any budget review:

1. Pull the Conversion Lag report (Tools → Attribution → Conversion Lag). Screenshot the distribution so you have a baseline. 2. Apply a lag haircut to any ROAS or CPA figure drawn from a window shorter than 30 days. Use the at-risk percentage from your own distribution — or use 20% as a conservative rule of thumb if your data is thin. 3. Cross-reference with CRM data. Count actual closed jobs or booked appointments by the week the lead originated, not the week it closed. This gives you a ground-truth conversion timeline that Google's dashboard cannot provide on its own.

If your lag-adjusted numbers still support scaling, scale confidently. If they don't, you have just avoided a budget increase that would have been justified by phantom ROAS.

The Bottom Line

Reported ROAS is a useful signal. Lag-adjusted ROAS is a decision-quality signal. For local service businesses with multi-day sales cycles, the gap between those two numbers is often large enough to change the call.

The framework above is not complicated — but it requires pulling one extra report and applying one honest discount to your headline number. Most local advertisers never do it, which means most local advertisers are optimizing on flattering but incomplete data.

If you want a second set of eyes on your lag distribution and what it means for your current campaigns, [book a call with Nika Spark](https://nikaspark.com/contact). We will walk through your actual numbers — no pitch, just data.