Lead Tracking After a Website Relaunch
Every confirmed lead counted once, per site, in four tools
Read case studyBidding algorithms can only be as good as the signal you feed them. Most accounts I look into are optimizing hard toward conversions that are duplicated, mistimed, misattributed, or simply not the ones the business cares about. The algorithm is doing exactly what it was told. What it was told is wrong.
No single setting fixes that. It is an architecture problem, and it builds on the rest of the measurement stack: Google Tag Manager, Google Analytics 4, and Consent Mode V2.
Automated bidding learns from whatever you mark as a conversion. The signal usually goes wrong in one of these ways:
Each of these teaches the algorithm something false, and it keeps optimizing toward that until the data changes.
Any of these steps can break. A redirect can strip the click ID, a missing Conversion Linker means nothing gets stored, and denied consent limits what the tag may send. When reported conversions drop suddenly, I walk this chain from the top.
Google Ads lets you mark each conversion action as primary or secondary, and that decides what the bidding algorithm learns from.
| Type | Used for bidding | Typical examples |
|---|---|---|
| Primary | Yes | Purchases, qualified leads, bookings |
| Secondary | No, observation only | Newsletter signups, brochure downloads, add to cart |
The counting setting matters too. For leads, counting “one” conversion per click is usually right, because a person who submits a form three times is still one lead. For purchases, “every” is usually right, because each order has its own value.
Browser-side tags
The standard setup: a tag in the browser sends the conversion directly. It is quick to install and exposed to ad blockers, browser privacy features, and consent restrictions.
Server-side tagging
The browser sends data to a server container you control, and the server forwards it to Google Ads. Match rates improve, more conversions get past ad blockers and ITP/ETP restrictions, and you decide exactly what data leaves your systems. In exchange you pay for hosting and have one more thing to maintain.
Offline and CRM imports
The conversion is recorded later in the CRM and uploaded to Google Ads with the original click ID. It is the only way to connect a deal that closes weeks after the click to the ad that started it.
Most accounts I work on end up with a mix: browser or server-side tags for immediate actions, and offline imports for outcomes that happen later.
Conversion tracking is the last step in the measurement chain, and the one with money attached.
It can only be as trustworthy as the layers underneath. The conversion events usually share their taxonomy with Google Analytics 4, they fire through Google Tag Manager, and the signals from Consent Mode V2 decide whether they are observed or modeled.
A campaign that “looks like it is underperforming” sometimes has a tracking problem instead. I have seen budget pulled from channels that were working, and poured into channels that only won on paper because the tracking flattered them.
Once the conversion signal is clean, automated bidding finds more of what is working, and finds it faster.
1. Audit
I review the current conversion setup to find what is firing, what is duplicated, what is missing, and where the reported numbers differ from what the CRM or finance sees.
2. Define the conversion hierarchy
Which actions are primary and which are secondary, how each is counted, and whether it should influence bidding at all.
3. Architect the tracking
Browser-side, server-side, or a mix, chosen from the traffic, the tech stack, and the privacy requirements rather than from what is easiest to install.
4. Wire in Enhanced Conversions and offline imports
Where they improve match rates or attribution enough to be worth the work.
5. Validate against real transactions
I check that what Google Ads reports reconciles with what the business closed.
6. Document and hand off
So the setup survives new campaigns, new landing pages, and new people on the team.
If you want a second look at your setup, hire me.
Every confirmed lead counted once, per site, in four tools
Read case studyNo health data sent to Google, bookings measured
Read case studyConsent to conversion, end to end, in 2 days
Read case study8+ issues fixed in 2 days, every conversion verified
Read case studyOne event standard across every data flow
Read case studyNext step
See how I work and what it costs, or email me. I usually reply within one working day.