The Conversion That Died When a Button Changed Its Name
A contractor's phones were slowing and the account said website leads were zero. They were not zero. The only website conversion had been silently dead since someone renamed a form button from Send to Submit, breaking the click-text trigger behind it. The rebuilt trigger fired its first real conversion within two weeks, and the cleanup behind it collapsed rank-lost impression share to under one percent.
01 The numbers
- 0 Website conversions recording, before
- Send → Submit The break
- 86% Conversions carried by the two protected keyword themes
- <1%, from 27-48% Rank-lost impression share after cleanup
02 The breakdown
The Setup
A residential fence installer running one Google Search campaign. The call that started the engagement was the classic one: the phones are slowing down, what is wrong with the ads?
The surface diagnosis was real. Cost per click had climbed to roughly two and a half times its level of three months earlier. Between the costlier clicks and the 27 to 48% of impression share the account was losing to ad rank every week, click volume fell 75% on an unchanged budget. But underneath it sat something worse: the account’s website lead tracking was completely dead. The only conversions recording were taps on the ad’s call button. Every form fill on the site, the account’s second lead path alongside phone calls, counted for nothing.
What Was Broken
The website conversion existed. It was wired to a Tag Manager trigger that fired on a click whose text equaled “Send.”
At some point, the form’s submit button was renamed to “Submit.” Nobody touched the ads, nobody touched the tags, and the conversion died anyway. It had been sitting there Inactive, invisible unless someone went looking. Meanwhile the account also had automated recommendations applying themselves, including a bid-strategy change, with no human review.
A click-text trigger has two failure modes and this was both: it breaks on any copy edit, and it counts button presses instead of successful submissions, so even when it works it counts failures.
What I Did
Replaced the trigger with the event the form software emits. The form plugin fires a mail-sent event only on a successful submission. A small listener pushes that into the data layer, a custom event trigger picks it up, and the conversion tag fires on that. Verified live with a network capture: conversion ping, 200 OK. The new wiring survives button renames and counts only real submissions.
Cleaned up the account it was starving. Turned off the self-applying recommendations. Added competitor, DIY, and out-of-area negatives on top of the existing set. Removed duplicate keywords that were bidding against themselves.
The Result
The form conversion fired its first real lead shortly after the fix, confirmed in the following month’s audit. Rank-lost impression share, which had been running 27 to 48% weekly, collapsed to under 1% after the cleanup. Ninety-day account view at the follow-up audit: 582 clicks, 42 conversions, with the two winning keyword themes carrying 86% of conversions and both protected during the cleanup.
What I Did Not Claim
Cheaper clicks. The click-cost diagnosis traced to a weak-relevance keyword theme and query waste, part of which is still being worked, and no tag fix changes what an auction charges. What changed is that the account measures itself again, the waste stopped, and the follow-up audit showed the real growth constraint was budget, which is a decision, not a defect.
The Takeaway
Tracking does not fail loudly. A button rename in a page builder killed this account’s only website conversion, and the dashboards showed a business that looked like it was getting worse at marketing.
If your conversions are wired to what a button says, they are wired to the next copy edit. Wire them to what the software does.
When did someone last verify your conversions fire? A tracking audit answers that in a day.
03 More work
Other accounts, same approach.
gcs=G1-- (denied) consent state on beacons, before
A WooCommerce brand's visitors were accepting the cookie banner, and the Google beacons still fired with consent denied. The free tier of the consent platform never told Google about the yes. The ad account had been bidding on modeled data for users who had opted in. The fix was a small PHP snippet at the right priority.
Read the breakdown→
236 phone calls scored in the first pass
Part two of the law firm engagement. The account had clean tracking and qualified-call conversions, but every conversion imported at zero dollars, so Smart Bidding treated a $2,500 document review and a $15,000 litigation case as equals. I built a call-scoring system that reads every recorded paid call, prices it with the firm's own numbers, and feeds real matter value back into bidding. $1.32M in case value was written onto qualified leads, and the value is verifiably arriving on the primary conversion actions Google optimizes toward.
Read the breakdown→Ready to talk
Want this kind of breakdown on your account?
Thirty minutes on the phone. One clear set of next steps. Same person on the call as on the work.