Google Consent Mode v2 explained
Consent Mode v2 is Google’s way of letting your tags respect a visitor’s cookie choice while still measuring what it legitimately can. Get it right and you stay compliant without throwing away measurable revenue. Get it wrong and you either break the law or blind your analytics. Here is how it works.
What Consent Mode actually does
Consent Mode sends Google a set of signals describing what the user has agreed to, chiefly analytics_storage and ad_storage (plus ad_user_data and ad_personalization in v2). When consent is granted, tags behave normally. When it is denied, tags still fire but in a cookieless, privacy-safe way, sending pings that Google uses to model the conversions and visits you can no longer measure directly.
Why v2, and why it’s not optional
Version 2 added the ad_user_data and ad_personalization signals to meet EU rules. Crucially, Google now requires Consent Mode v2 for EEA and UK traffic to keep using features like remarketing audiences and full conversion measurement. No valid consent signals means degraded ads features, so this is a commercial issue, not just a legal one.
The two modes
- Basic Consent Mode: tags don’t load at all until consent is granted, so denied users are invisible.
- Advanced Consent Mode: tags load and send anonymous, cookieless pings even before/without consent, so Google can model the gap. This recovers far more measurable data and is usually the better choice.
Is consent silently killing your data?
We’ll check whether your banner is blocking tags or passing consent correctly. Free 10-second scan.
Check my tracking freeWhere it goes wrong
The classic failures: a cookie banner that blocks Google’s tags outright instead of passing consent signals; Consent Mode set to Basic when Advanced would recover far more; the consent platform and GTM not wired together, so the signals never actually reach the tags; and different behaviour on each domain of a multi-site business. Any of these quietly removes a slice of measured revenue.
Getting it right
Your consent platform (CMP) and GTM need to speak to each other so the consent state is passed to Google’s tags, Advanced mode is usually the right default, and it all needs testing on every domain with consent granted and denied. Done properly, you stay compliant and keep modelling the conversions you would otherwise lose.
Get Consent Mode v2 set up properly
We wire your CMP to GTM, configure Advanced Consent Mode and test it on every domain. The audit comes off any build.
See how it works & pricingRelated guides
How cookie consent breaks tracking What is server-side tracking? Free cookie consent check PricingDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Ads, Meta and server-side tracking. See pricing · All guides · Back to datahound.agency
Consent Mode v2: common questions
What is Google Consent Mode v2?
It’s Google’s framework for passing a user’s cookie consent choice to your tags. When consent is denied, tags fire in a cookieless way so Google can model the conversions and visits it can no longer measure directly. V2 added signals required for EEA and UK traffic.
Is Consent Mode v2 mandatory?
For EEA and UK traffic, effectively yes if you want to keep using Google ads features like remarketing and full conversion measurement. Without valid consent signals, those features are degraded.
What’s the difference between Basic and Advanced Consent Mode?
In Basic mode, Google’s tags don’t load until consent is granted, so denied users are invisible. In Advanced mode, tags load and send anonymous cookieless pings regardless, letting Google model the gap, which recovers much more measurable data.