How a Broken Form Cost an Agency Months of Leads

How does a broken form cost an agency months of leads?

A broken form costs an agency months of leads when the campaign keeps performing but the submission never reaches the client. Ads serve, people click, the form appears to send, and the conversion even fires in the platform — yet the email notification, CRM hand-off, or database write silently fails. Nobody notices because every dashboard still looks healthy.

That is exactly what happened in the case Danny Gavin, founder of the agency Optidge, described on PPC Live The Podcast. His team ran Google Ads for an autism therapy provider. Inside the ad account, performance looked strong: clicks were coming, cost per lead was healthy, the funnel read as a success. But for roughly one to two months, the client received almost nothing. The leads were being generated — they just never arrived. The form, or the path behind it, was broken.

The most dangerous failure in lead generation is the one that leaves every metric looking green. A leak you can see gets fixed in a day; a leak you cannot see costs you a quarter.

This is the gap most SEO and PPC guides skip. They obsess over getting more clicks and lower cost per acquisition, and assume the plumbing between the form and the client works. It frequently does not. A single stale notification email, an expired CRM API key, a spam filter, or a tag that stops firing can sever the connection between a 'converting' campaign and a business that is starving for new customers.

Why a form can break while your dashboard still looks fine

The reason this failure mode is so common is that a lead has to survive a chain of independent systems, and your reporting usually watches only the first link. Picture the full path a single enquiry travels:

1. The visitor clicks the ad or organic result and lands on the page.
2. They fill the form and hit submit.
3. The page shows a confirmation and fires a conversion event to Google Ads, GA4, or a pixel.
4. A notification email is sent to the agency or client inbox.
5. The data writes to a CRM, spreadsheet, or database.
6. A human on the client side actually sees it and follows up.

Conversion tracking typically confirms only step 3. The platform records a 'conversion' the moment the thank-you page loads or the event fires — it has no idea whether steps 4 through 6 succeeded. So your dashboard can show 40 conversions this month while the client's inbox shows zero. Both numbers are 'correct'; they are just measuring different things.

Common, real-world causes of this silent break include:

• Notification routing failures — the recipient address changed, an employee left, or messages now land in spam or a quarantine folder.
• Form plugin or builder updates — a CMS, theme, or plugin update resets the email handler or breaks the webhook.
• CRM integration drift — an expired API token, a renamed field, or a deactivated automation quietly stops the hand-off.
• Tag and consent changes — a consent-mode or tag-manager change suppresses the event, or double-fires it, distorting the count.
• Spam protection gone wrong — an aggressive honeypot or reCAPTCHA setting silently rejects legitimate submissions.

None of these throw an obvious error. The visitor sees a success message and leaves happy. That is what makes the leak invisible until someone asks the right question.

The communication failure behind the technical one

Gavin made a point that matters as much as the bug itself: the technical fault was only half the story. The other half was that nobody asked the obvious question. The client was growing frustrated that no enquiries were arriving, while the agency was looking at a dashboard that said everything was working. For weeks, two parties stared at two different realities and never reconciled them.

The fix Optidge put in place was organizational, not just technical. They introduced dedicated account managers whose core job is to stay in close contact with clients — to surface exactly this kind of disconnect early. The simple, unglamorous question — 'Are you actually receiving the leads?' — is one of the highest-leverage things anyone in performance marketing can ask, and almost nobody builds it into their routine.

What most guides get wrong is treating tracking and client communication as separate disciplines. They are the same safety net. A weekly check-in that compares 'leads we reported' against 'leads you received and called' would have caught this in days instead of months. The dashboard is a proxy for reality; the client's phone ringing is reality.

How to catch and prevent broken-form lead leaks

Treat your lead path like production infrastructure, because that is what it is. The goal is to detect a leak in hours, not after a client churns. Here is a layered approach that combines monitoring, reconciliation, and routine testing.

A few practices make the biggest difference:

• Submit a real test lead end to end. Do not stop at the thank-you page. Confirm the email arrives in the actual inbox and the record lands in the CRM. Tag test submissions so they are easy to filter out.
• Reconcile two numbers, not one. Each reporting period, compare the conversions your platform claims with the leads the client says they received and worked. Any persistent gap is your alarm.
• Alert on the drop, not just the rise. A form-fill count falling to near zero is more urgent than a good week. Set automated alerts on a sudden decline in submissions or sessions to key pages.
• Re-test after every change. CMS updates, theme changes, new consent banners, and plugin upgrades are the usual culprits. Add a form test to your post-deploy checklist.
• Watch the traffic, not only the conversion. If sessions to the landing page hold steady but submissions collapse, the page or form broke — not the campaign.

This last point is where traffic analytics earns its keep. Sentinel SERP tracks visits, landing-page sessions, and conversion trends together, so a sudden divergence — steady traffic, cratering form-fills — shows up as a visible anomaly rather than a surprise three months later. Pairing that signal with a routine end-to-end test turns an invisible, quarter-long leak into a same-week fix.

A simple lead-path QA routine you can ship today

You do not need an enterprise observability stack to avoid this. A disciplined routine beats expensive tooling that no one checks. Put these on a recurring calendar for every lead-gen client.

1. Map the path once. Document every hop a lead takes — page, form, event, email, CRM, owner. You cannot monitor a path you have not drawn.
2. Schedule a weekly live test. Submit a real form, verify the email and the CRM entry, and log the result. Rotate who does it so it never gets skipped.
3. Hold a short reconciliation with the client. 'Here is what we tracked; how many did you actually receive and contact?' Make this a standing agenda item.
4. Automate one anomaly alert. Pick the single most important conversion and alert on a sharp drop in volume.
5. Re-test on every deploy. Any change to the site, tags, or integrations triggers a fresh end-to-end test before you call it done.

The agencies that avoid the months-long leak are rarely the ones with the fanciest tools. They are the ones that assume the form will break eventually and build a habit of checking it — and that keep talking to the client about the only number that matters: leads that actually arrived.