Google Ads Conversion Lag Report: Why Your Local Service ROAS Is Understated (And How to Fix It)

The Problem No One Explains in the Dashboard

You launch a Google Ads campaign. After two weeks, the ROAS looks weak. You pause it. Three weeks later, the phone rings with four booked jobs — all tracing back to clicks from that campaign.

This is conversion lag, and it is one of the most common reasons profitable local service campaigns get killed early.

Conversion lag is the gap between when someone clicks your ad and when they complete the action you're counting as a conversion — a booked call, a submitted form, a scheduled estimate. For local services, that gap is rarely zero. Homeowners research. They call two or three contractors. They wait for a spouse to sign off. They bookmark you and come back.

Google Ads actually shows you this data. It's called the Conversion Lag Histogram, and most advertisers never look at it.

How to Find the Conversion Lag Histogram

Inside Google Ads:

1. Go to Tools & Settings → Measurement → Conversions 2. Click into a specific conversion action 3. Scroll to the "Conversion lag" section — Google renders a histogram showing what percentage of conversions came in on Day 0, Day 1, Days 2–3, Days 4–7, Days 8–14, Days 15–30, and Days 31+

This histogram is specific to your account and your conversion action. It reflects your actual buyer behavior, not a generic benchmark.

What to look for:

• A spike on Day 0–1 typically means you're counting phone calls or live chat (fast decisions)
• A longer tail into Days 7–30 typically means form leads, quote requests, or higher-ticket services
• A meaningful chunk of conversions in the Days 8–30 range is the signal that short reporting windows are lying to you

Typical Conversion Windows by Local Service Category (Labeled Estimates)

We don't have a single published benchmark that covers all local service categories cleanly, so treat the ranges below as illustrative estimates based on general buyer-behavior patterns — not cited research. Use your own lag histogram to validate.

| Service Category | Estimated Conversion Window | Why | |---|---|---| | Emergency plumbing / locksmith | Same day to 48 hours | High urgency, low comparison shopping | | HVAC tune-up or replacement | 3–14 days | Multi-quote process, seasonal timing | | Roofing / exterior remodel | 7–30 days | Large ticket, insurance involvement common | | Landscaping / lawn care | 3–10 days | Moderate urgency, some comparison | | Dental or med-spa new patient | 3–21 days | Insurance check, scheduling friction | | Legal consultation | 7–30 days | High stakes, deliberate decision process |

The practical rule of thumb: the higher the average job value, the longer the expected conversion window. If your average job is under $300, most conversions likely land within 7 days. If your average job is over $2,000, a 30-day window is the minimum before you should draw conclusions.

This connects directly to a point we make in Call vs. Form Conversions: Which Trains Smart Bidding Better? — the conversion action you're counting shapes how fast the data appears. Calls tend to be faster; forms tend to lag. If you're optimizing on form fills, expect a longer tail.

The Labeled Model: How a Short Window Understates ROAS

Here's a concrete worked example — all numbers are illustrative.

Scenario: A roofing company spends $4,000 in a calendar month. They check ROAS after 10 days.

What the 10-day snapshot shows:

• Spend attributed to that period: $4,000
• Conversions recorded so far: 6 (only fast-converting clicks have resolved)
• Average job value (illustrative): $4,500
• Apparent revenue: 6 × $4,500 = $27,000
• Apparent ROAS: 6.75x

What the 30-day window shows (same spend, more conversions resolved):

• Spend: still $4,000
• Conversions recorded: 10 (four more leads booked and closed in days 11–28)
• Revenue: 10 × $4,500 = $45,000
• Actual ROAS: 11.25x

The campaign didn't get better. The revenue was always there. The reporting window was just too short to see it.

If this campaign had been cut after the 10-day read, you'd have sacrificed $18,000 in projected revenue to protect a budget line based on incomplete data. That is the lag trap.

Note: Google's Smart Bidding algorithms also suffer from this. If your attribution window is too short, the algorithm under-values clicks that eventually convert — and bids less aggressively on exactly the audience segments most likely to book.

The Right Way to Set Your Reporting Window

Step 1: Read your own lag histogram first. Don't assume. Pull the histogram for your primary conversion action and identify the day range where 80–90% of conversions have resolved. That is your minimum safe evaluation window.

Step 2: Match your conversion window setting to buyer behavior. In Google Ads, conversion actions have a configurable conversion window (under the conversion action settings). By default, it's often set to 30 days for clicks. If your histogram shows meaningful conversions past 30 days, extend it to 60 or 90 days — Google allows up to 90 days for most action types.

Step 3: Never compare spend and revenue across mismatched windows. This is the most common mistake. Spend is reported in real-time. Revenue (from conversions) lags. If you pull a report on October spend vs. October conversions on November 1st, you are comparing a complete spend number to an incomplete conversion number. Always pull conversion data with at least a full lag buffer added.

Step 4: Use a 'conversion value by click date' view, not 'conversion date.' In Google Ads, switching segment reporting to click date instead of conversion date lets you see how much revenue a week's worth of clicks eventually generated — regardless of when the conversion was recorded. This is the most accurate picture of true campaign performance.

For more on how your conversion action choice shapes this entire problem, see our piece Call vs. Form Conversions: Which Trains Smart Bidding Better? — and if you're also running awareness-level video, the lag patterns differ significantly from bottom-funnel search (covered in Video vs. Static Ads: CPL for Local Service Campaigns).

Why This Also Breaks Your Lead Follow-Up

Conversion lag isn't only a reporting problem. It's also a signal that leads are sitting in your pipeline longer than you think — which means how fast your team responds and how persistently they follow up directly shapes whether those lagging conversions ever close.

A click that doesn't convert on Day 0 is often a lead that submitted a form, didn't get a same-day callback, and booked a competitor by Day 3.

We break down the data behind this in Lead Response Time vs Close Rate: Fix This Funnel Leak — but the short version is: if you fix the attribution window without fixing the follow-up speed, you're still leaving conversions on the table. The lag histogram shows you how long the window is open. Your sales process determines whether you close during it.

The Framework in One Place

To stop letting conversion lag break your campaign decisions:

1. Pull your lag histogram — find the window where 80–90% of your conversions resolve 2. Set your conversion window in Google Ads to match (up to 90 days) 3. Add a lag buffer to any reporting period before drawing conclusions 4. Segment by click date, not conversion date, when evaluating ROAS 5. Don't cut campaigns until a full lag cycle has elapsed — for most local services, that's a minimum of 3–4 weeks, often 6 6. Audit your follow-up speed — attribution fixes only help if your team is actually closing the leads that come in late

This is the kind of analysis that separates campaigns that scale from campaigns that get killed prematurely.

---

If you want someone to pull this report on your account and tell you exactly what your lag window looks like — and whether your current ROAS numbers are trustworthy — [book a free strategy call with Nika Spark](#). We'll show you what the data actually says.