Lead Tracking After a Website Relaunch
Every confirmed lead counted once, per site, in four tools
Read case studyPrivacy regulation and data quality are usually treated as a trade-off: tighten one and you lose the other. Most sites “handle” consent by putting a cookie banner on top of their existing tags and calling it compliant. Then either the tracking keeps firing when it should not, or it stops completely and half the data disappears the moment someone clicks “reject.”
The banner is only the visible part of Consent Mode V2. Underneath, it is a signaling layer between the site, Google Tag Manager, and Google's platforms, and when that layer is built properly you can stay compliant and still see what is happening. This note is one of four on the measurement stack, together with Google Analytics 4 and Google Ads Conversion Tracking.
A banner collects a choice. Something else has to carry that choice to every tag, at the right moment and for the right region. When that part is missing, consent fails in one of two directions:
From the outside, both look fine. The banner appears and the site works. The problem shows up later, in an audit or as a slow decline in reported conversions.
Consent Mode is a small set of commands that tell Google tags what the visitor agreed to, and the tags adjust their own behavior to match.
The order matters. The default has to be set before any Google tag runs, and the update has to arrive the moment the visitor chooses. Waiting for the next page load is too late.
Version 2 added two signals to the original two. Google requires them for advertising features when visitors are in the European Economic Area.
| Signal | What it controls |
|---|---|
analytics_storage |
Whether analytics cookies, such as GA4’s, may be stored. |
ad_storage |
Whether advertising cookies may be stored. |
ad_user_data |
Whether user data may be sent to Google for advertising. New in V2. |
ad_personalization |
Whether data may be used for personalized ads, such as remarketing. New in V2. |
Basic mode
Google tags do not load at all until the visitor consents, so nothing is sent before the choice. It is simple, but when a visitor declines, Google gets no signal and has nothing to model from.
Advanced mode
Google tags load with consent denied by default and send cookieless pings without identifiers. When a visitor declines, Google can use those pings to model the conversions it cannot observe directly.
The right mode depends on the legal advice for the business and the regions it serves. Pick one deliberately, because that choice decides whether modeled conversions are possible.
Consent is the first gate in the measurement chain, and every layer after it inherits its decisions.
Google Tag Manager enforces the consent state on each tag. Depending on how this layer was built, Google Analytics 4 and Google Ads Conversion Tracking then receive full data, modeled data, or nothing.
ad_user_data and ad_personalization are missing, which limits advertising features for EEA traffic.Get it wrong in one direction and the site is non-compliant, exposed to fines and to platform penalties that can shut down ad accounts overnight. Get it wrong in the other and you are legally safe but flying without instruments. Reporting undercounts conversions, bidding learns from incomplete signals, and performance slides for reasons that do not show up anywhere.
The businesses that handle this well plan consent as part of the tracking from the start, before launch, instead of adding it afterward for the lawyers.
1. Audit the current consent setup
Which signals exist, which ones the tags actually respect, and where compliance and data quality are working against each other.
2. Map the regulatory footprint
Where the users are, what the law requires there, and what is only best practice.
3. Architect the consent signal flow
In Google Tag Manager, connected to the CMP and to every tag downstream.
4. Configure conversion modeling
So a declined consent leads to modeled data instead of a gap.
5. Test every consent state
Accept, reject, and each custom combination. I check the state in Tag Manager’s Preview mode and in the network requests the tags send.
6. Document
So the setup stays compliant when someone else adds tags later.
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 studyNext step
See how I work and what it costs, or email me. I usually reply within one working day.