Google Ads leads not converting? Read the reply log before you touch the campaign

When Google Ads shows conversions but the client sees no sales, read the reply log before you change a bid, a keyword or a landing page. Conversion tracking ends at the form submit. Nothing in the ad account records whether the business answered. In Leadferno's June 2024 test of 225 small-business contact forms, 42.6% of leads got no reply at all, and the average first human reply took 17 h 49 m⁴. A campaign cannot convert a lead that nobody answered.

This post treats the problem as a production incident. The symptom is in the ad account. The telemetry that explains it is not. The fix starts with one log that most agencies and advertisers never build.

What "leads but no sales" looks like from the ad account#

The "leads but no sales" symptom has a fixed shape: conversion count steady or rising, cost per conversion inside target, and a client who says the leads are bad. The ad account reports the first half truthfully. It cannot report the second half at all.

The stakes are concentrated in this channel. CallRail's January 2025 report, built on 1.1 million conversations, found that Google Ads drove 37% of small businesses' conversations and 47% of their qualified leads¹. If ad-sourced leads leak after delivery, roughly half of a typical small business's qualified pipeline leaks with them.

Agency discourse looks elsewhere. ideafast's July 2026 review of 149 r/PPC posts lists six recurring problems: ROAS pressure, click costs, cost per conversion, conversion tracking confusion, account verification delays and manual client reporting³. None of the six is "the client did not reply." Client-side handling is the unmonitored layer.

The path a lead takes after the click#

An ad-sourced written lead crosses six hops between the click and a booking, and the ad platform instruments only the first two. Draw the path before you debug it.

Hops 4 to 6 are where the Leadferno numbers sit. Only 10.6% of leads got a reply within an hour and 3.1% within five minutes⁴. Leadferno also reports that about two-thirds of the leads that got a reply received only that one response⁴. Treat that figure as reported; Leadferno's materials give it as both 65.5% and 65.9%.

Three hypotheses that are usually tested first#

Agencies usually test three hypotheses before the reply log, and each can be true while still explaining nothing. Rule them in or out with evidence, then move to hop 5.

Hypothesis 1: the traffic is bad#

Bad-traffic diagnosis means search terms, match types and geography. It is the cheapest check and should run. It cannot, though, explain a lead that filled in a complete form with a real phone number and never heard back. A search-terms report shows intent at hop 1. It says nothing about hop 5.

Hypothesis 2: the landing page does not convert#

The landing-page hypothesis is often correct about click-to-lead rate. BlakSheep Creative's February 2026 case study of a pest-control client spending "about $3,000 per month on Google Ads" puts it plainly: "If you are getting clicks but no calls, you do not have a traffic problem."² Their fixes were page speed (from eight seconds), mobile layout, real team photos and a sticky call button. They report: "Thirty days later, the lead volume doubled. Same ads. Same budget."² That is a hop 1 to 2 fix. More leads into an unanswered inbox produces more unanswered leads.

Hypothesis 3: conversion tracking is wrong#

Conversion tracking errors are real and common enough to top the r/PPC list³. Duplicate firing or a thank-you page that loads without a submit will inflate the count. Verify the form tool's own entry count against the ad platform's count for the same window. If the two agree within a few leads, tracking is not your incident. Move on.

Root cause: the reply layer is unmonitored#

The root cause in most "leads but no sales" accounts is a reply layer with no telemetry: nobody measures time to first reply, follow-up count or whether a time was offered. Three failure classes produce it.

Delivery failure at hop 3 to 4. The form notification is sent from a domain that is not authorised to send it, fails SPF or DKIM alignment, and lands in spam or nowhere. Joe Seabrook, a web developer, lists spam filtering of free mailboxes and single-channel dependency among the reasons clients miss submissions: "If the entire workflow depends on one thing (email), then all it takes is one small issue for a lead to be lost."⁵ Leadferno found 4.8% of the forms it tested broken outright⁴.

No reply at hop 5. The message arrives and nobody answers. This is the 42.6%⁴. Agencies see the result in their own forums. A thread in r/AskMarketing (10+ comments, c. May 2026) described leads that "just die in the CRM"¹⁰.

Reply without a next step at hop 5 to 6. The business answers once, offers no time and never follows up. In Pied Piper's April 2026 mystery shop of 3,211 home-services locations, 72% of inquiries got no follow-up within 24 hours, and only 28% were offered an appointment where scheduling was the natural next step⁶. Invoca's July 2026 home-services benchmarks found 55% of businesses do not ask the caller to book⁷. Both studies are home services; treat them as a reference class, not a measurement of your client.

The fix: build the reply log first#

The reply log is one row per ad-sourced lead with four timestamps and one outcome, and it is the first artifact to build when leads do not convert. It takes an afternoon for 90 days of a small account. It needs read access to the form tool's entries and either the client's sent folder or the client's help to match threads.

1. Fix the window. Pick the last 30 days for a busy account, 90 for a small one. Record the start and end dates; every number below uses the same window.
2. Export the lead list at source. Use the form tool's entries, call-tracking log or lead export, not the ad platform's conversion count. Columns: received timestamp, channel, source (ad, organic, other).
3. Reconcile counts. Ad-platform conversions vs form-tool entries vs notifications found in the inbox. A gap between the last two is a delivery fault (hop 3 to 4). Check the sending domain's SPF, DKIM and DMARC before continuing.
4. Match each lead to its reply. For every row, record first reply timestamp, number of follow-ups sent, whether a specific time was offered, and the outcome: never answered, answered once and dropped, time offered, booked, or lost with a reason.
5. Compute five numbers. Never-answered share; share answered within 1 h; median (p50) and p90 time to first reply; share offered a specific time; booked share. Report p90, not the mean; the leads that leak sit in the tail.
6. Apply the decision rule. If never-answered share is above 10%, or p90 first reply is over 24 h, or fewer than half of answered leads were offered a time: fix handling first and freeze campaign changes for one cycle. Otherwise, return to traffic and page hypotheses with the log as your baseline.
7. Re-run after one cycle. Same window length, same columns. Compare booked share before and after. Only then change bids or keywords, so the two changes do not mask each other.

The thresholds in step 6 are the Technical desk's working defaults, not published benchmarks. Leadferno's figures are the nearest external reference: 42.6% never answered and 10.6% within an hour⁴. An account that looks like the Leadferno sample has a handling incident, whatever its cost per conversion says.

What the log is worth in dollars#

The cost of an unanswered ad lead is the media spend that produced it. Illustration Take BlakSheep's example budget of $3,000 a month² and assume the account's leads go unanswered at Leadferno's rate of 42.6%⁴. That is about $1,278 a month, or roughly $15,300 a year, of spend whose leads were never answered. The figure assumes every lead costs the same; it is an order of magnitude, not a measurement.

Trade-offs and residual risk#

Building the reply log has costs, and three of them deserve a line in the engagement letter.

• Inbox access. Matching replies needs the client's sent mail. Prefer that the client labels and forwards the relevant threads, or exports them, rather than granting the agency full inbox access. The log holds names and contact details; keep it private and delete the agency's copy when the report is done.
• A one-cycle freeze. Holding campaign changes while handling is fixed costs a cycle of optimisation. Running both changes at once costs more, because you cannot attribute the result.
• Uncomfortable findings. A log that shows 40% of leads unanswered moves the conversation from the agency's work to the client's inbox. Present it as shared telemetry, not as blame.

The residual risk is sample size. A small account may produce 20 leads in 30 days; one slow week moves the p90 by hours. Use 90 days when volume is low, and state the n beside every percentage.

Reproduction notes#

Record the environment with every reply log so the next run is comparable: window dates; lead sources included; whether calls, texts and directory leads were counted; time zone; business hours used for "within 1 h"; and who matched the replies. For a full 90-day version with outcome definitions and formulas, use the Lost Lead Audit. For the notification failures at hops 3 and 4, see why contact-form leads never get a reply.

Where Valet fits#

Valet is a small business's own AI assistant for written inquiries: email, website contact forms and directory or marketplace lead emails. The owner forwards an address to Valet; it answers from the owner's own price list, calendar and policies, offers and holds real times, and follows up at most twice by default before stopping and telling the owner why. Every inquiry carries a state, a next step and a time, and every reply has a Valet receipt: what was asked, the rule used, the sources and where it was sent from. Those records are the reply log, kept as the work happens. It does not answer phone calls.

To see your client's numbers first, start with the free lead check: forward 10 to 20 recent inquiries, or show them on a call, and see what went unanswered, what stopped after one reply, and what it was worth.