If you ship Google tags into a regulated market, Consent Mode v2 is no longer a "policy thing" — it sits inside the request layer of every Google tag your site fires.
The four consent signals
Consent Mode v2 communicates four parameters from your CMP to every Google tag on the page:
-
ad_storage— can advertising cookies be written? -
analytics_storage— can analytics cookies be written? -
ad_user_data— can user data (click IDs, hashed email, etc.) be sent to Google for ads? -
ad_personalisation— can the user be added to remarketing or personalised ad lists?
Each signal flips between granted and denied based on the visitor's banner choice. Google tags read those signals before every request and adjust behaviour in real time.
Cookieless pings (the part developers miss)
When a user denies consent, the tag does not go silent. It still fires — but as a cookieless ping carrying no identifiers, only event-level signals (timestamp, page, conversion type). Those pings are the raw input for Google's conversion-modelling layer.
If you stop at basic mode, no pings are sent on denial. That kills the modelling layer and your reported conversions collapse with it. Advanced mode is where the recovery happens.
What it means at the campaign layer
Smart Bidding (Target CPA, Target ROAS, Maximise Conversions) runs on conversion volume. Without Consent Mode v2 advanced, EU traffic shows up to 70% fewer reported conversions, so the bidding model overcorrects and CPA inflates.
Pair this with server-side tagging and you also reduce browser-side dependency, which improves both signal quality and page performance.
Implementation reality
Most teams misconfigure ad_user_data or skip advanced mode entirely. The fix is choosing a Google-certified CMP that wires all four parameters automatically, then verifying with Tag Assistant.
A clean teardown of the bidding-level impact lives in this Consent Mode v2 advertiser guide — worth a read before your next deploy.
Top comments (0)