Consent Mode v2
The consent banner, wired into Google — two new signals, a March 2024 deadline, and modeling where consent says no.
- Term
- Consent Mode v2
- Adds
- ad_user_data, ad_personalization
- Mandatory
- EEA ad features, March 2024
- Pairs with
- Conversion modeling for declined users
Forms & parts of speech
Definition in plain terms
Consent Mode v2 is Google's framework for communicating each user's consent choices from your banner to Google's tags, so measurement and advertising behave according to what the user actually allowed. Version 2 added two signals to the original storage controls: ad_user_data (may user data go to Google for advertising) and ad_personalization (may it power remarketing). Google made the implementation effectively mandatory for advertisers using its ad personalization features on EEA traffic from March 2024 — without the signals, audience building and remarketing for those users stops.
The mechanics
The framework rides your consent management platform: when a visitor accepts or declines, the CMP sets the consent state — analytics_storage and ad_storage from v1, plus v2's ad_user_data and ad_personalization — and Google's tags adjust behavior accordingly. Two implementation modes exist with different physics. Basic mode holds tags entirely until consent, clean and blunt; advanced mode lets tags send cookieless pings for declined users — no identifiers, just anonymous signals — which feed CONVERSION MODELING so declined traffic is estimated rather than erased (the Consent Mode pattern is the canonical input to Google's modeled conversions; see the conversion-modeling entry for how to read the estimates). The v2 mandate's enforcement is practical rather than legal: Google's EEA ad features simply require the signals, so non-implementation means audience lists stop filling, remarketing shrinks, and measurement degrades — the platform enforcing what regulators demanded of it under the Digital Markets Act era. Implementation discipline is mostly plumbing accuracy: the CMP must set all four signals correctly before tags fire, defaults must reflect region-appropriate assumptions, and the setup deserves end-to-end testing because a silently mis-set signal degrades data with no error message.
When it matters
Consent Mode v2 matters to anyone advertising with Google into EEA (and UK-equivalent) traffic — since March 2024 it is the toll for using remarketing and audience features there at all, and the input that keeps EEA measurement modeled rather than missing. It matters operationally at CMP changes, tag migrations, and site replatforms, where signals silently break. The discipline is to implement advanced mode where legal posture allows (preserving modeled signal), verify all four parameters fire correctly per region, and read the resulting reports knowing which portion is modeled — the framework keeps the numbers alive, and honesty about their estimated layer keeps decisions sound.
Synonyms & antonyms
Synonyms
Antonyms
Origin & history
Google introduced Consent Mode in 2020 as the bridge between consent banners and its tags; version 2 arrived for the Digital Markets Act era, adding ad_user_data and ad_personalization signals and becoming effectively mandatory for EEA ad personalization in March 2024 — the platform's compliance passed through as an advertiser requirement.
Etymology: source.
Usage trends
Search interest for this term over the last five years:
Common questions
- What is Consent Mode v2?
- Google's framework for passing users' consent choices to its tags — v2 added ad_user_data and ad_personalization to the storage signals, controlling whether data reaches Google for advertising and remarketing.
- Why was Consent Mode v2 mandatory in March 2024?
- Google required the signals for ad personalization features on EEA traffic — without them, audience building and remarketing for those users stops, enforcing the requirement through feature loss.
- What is the difference between basic and advanced mode?
- Basic holds tags entirely until consent; advanced sends anonymous cookieless pings for declined users, feeding conversion modeling so declined traffic is estimated rather than erased.
Related tools & calculators
- toolCAC calculator
- toolLTV:CAC calculator
Resources & people to follow
- referenceGoogle — consent mode for EEA traffic
- referenceCookiebot — the March 2024 consent mode deadline
- referenceRGM analysis — the failure mode is silence; test all four signals end-to-end after every CMP or tag change
Curated, non-competitor resources verified per term.
Related training
- modulePerformance marketing
Disciplines
Areas of marketing where consent mode v2 is a core concern: