Challenge
A new multi-market client’s campaigns recorded zero conversions while 15,949 clicks became 961 elsewhere in the account.
Solution
Traced three layers to one character, an unrecognized template token, then fixed it with a catch-all backstop.
Result
6,411 clicks and $4,836 of spend recovered from "worthless."
Challenge
A new multi-market client's campaigns were showing no recorded conversions at all. Not a decline, zero, while the search campaigns in the same account over the same window turned 15,949 clicks into 961 conversions. The spend was real and the clicks were real, which normally points at the media or at the landing pages. Both looked healthy.
Solution
The cause was three layers away from where the symptom appeared, and it was one character. The account-level tracking template referenced an ad group variable that does not exist in that ad platform. It exists in two competing platforms, which is how the mistake gets made, and the real mechanism there is a custom parameter, spelled with a leading underscore. Unrecognized tokens are passed through as literal text rather than rejected, so the campaign name arrived at the landing page as an unresolved string in braces. The landing page tags were configured to fire only when the URL identified a real product line. Given a string that identified nothing, they correctly did not fire. Every component did exactly what it was told, and the result was a revenue number of zero against a business that was selling.
The diagnostic tell was in the URL itself: the parameters the platform did recognise but could not populate came through empty, while the one it did not recognise kept its braces. Proof it was not a tag fault came from a phone tag on the same pages that triggers on hostname alone, which fired normally throughout.
We corrected the template at account level through the API, set per-campaign parameters where they were missing, and added a catch-all conversion action blocked by every existing market trigger, so that a future gap produces a count rather than a silence. Blocking by trigger rather than by text exclusion matters here: a market added next year cannot fall through a gap in a pattern match. All three cases were verified in preview before publishing.
Result
The gap covered 6,411 clicks and $4,836 of spend that had been reporting as worthless, and it had also been starving an automated bidding strategy of the signal it optimises against, so the reporting failure was quietly degrading the media buying as well. The lesson we carry into every engagement is that a URL is a contract between the ad platform, the site and the analytics. When a contract that quiet breaks, the number it produces is not wrong in a way anybody notices. It is confidently, precisely zero.
Work like this is delivered through our Technical Services and, where it is ongoing, our Platform Management bundles.
< Related Engagements >
More from this category
Zero Clicks and Eroding Sales to +56% Conversions in 75 Days
Result: +56% conversions in 75 days; record sales months within six.
Read the full overview →CRM ReconciliationReconciling Marketing Data Against the System of Record
Result: 24% of revenue from 17% of leads; the biggest lead source proved the worst converter.
Read the full overview →RepairsReporting Error Repairs & Integration Fixes
Result: Relaunched with confidence; never recurred.
Read the full overview →← All case studies · Next: Reconciling Marketing Data Against the System of Record →
Have a problem shaped like this one?
Bring us the messy version. The free audit tells you what is actually broken and what it takes to fix it.
Bring Us Your Challenge