Consent & Cookies
What is Google Consent Mode v2?
Google Consent Mode v2 is Google's framework through which a website's consent banner tells Google tags what the visitor agreed to — via four consent states including the v2 additions ad_user_data and ad_personalization — and it has been required since March 2024 for advertisers using Google's ad features for EEA and UK traffic.
Consent Mode is the bridge between your CMP and Google's tags. Rather than simply blocking Google scripts, the CMP sets consent states that the tags read and obey: analytics_storage and ad_storage (from v1) control whether cookies may be used for analytics and advertising, while v2 added ad_user_data (may user data be sent to Google for advertising purposes) and ad_personalization (may that data drive personalized ads and remarketing).
The v2 mandate has commercial teeth rather than a legal penalty: since March 2024, Google requires the v2 signals for EEA and UK traffic as a condition of its ads ecosystem. Advertisers who fail to send them lose ad personalization, remarketing audiences stop accumulating new EEA/UK users, and conversion measurement degrades. The requirement is Google enforcing its own EU User Consent Policy obligations down through its customers.
Consent Mode comes in two flavors. In basic mode, Google tags are fully blocked until consent and fire only for consenting users. In advanced mode, tags load for everyone but send cookieless 'pings' for non-consenting users, which Google uses to model conversions statistically. Advanced mode recovers more measurement but is legally contested in strict EU jurisdictions, since even cookieless pings transmit data — many advisers recommend basic mode for conservative implementations.
Implementation runs through Google Tag Manager or gtag.js, with the CMP setting default (denied) states before any tag fires and updating them on the visitor's choice. The order matters: defaults must be in place before tags load, or the first pageview leaks.
Why it matters for eCommerce
If you run Google Ads or GA4 against European traffic, Consent Mode v2 is the difference between functioning campaigns and quietly dying ones — remarketing lists that stop growing and conversions that vanish from reports. Implement it through your CMP, choose basic or advanced mode deliberately, and verify the default-denied state is set before your tags load.
Frequently asked questions
- Is Google Consent Mode v2 mandatory?
- For advertisers using Google's advertising features on EEA and UK traffic, effectively yes — since March 2024, Google conditions ad personalization, remarketing, and full measurement on receiving the v2 signals. Sites with no Google ads stack and no EEA/UK traffic are not affected.
- What is the difference between basic and advanced Consent Mode?
- Basic mode blocks Google tags entirely until consent. Advanced mode loads tags for all visitors and sends cookieless pings for non-consenting users so Google can model conversions. Advanced yields more data but is viewed skeptically by some EU regulators; basic is the conservative choice.
- Does Consent Mode replace my CMP?
- No — it is the signaling layer between your CMP and Google's tags. You still need a compliant banner, consent records, and blocking for non-Google vendors. Consent Mode only governs how Google tags behave.
Related terms
Wondering how this applies to your own site? Get a free compliance scan — see every tracker that fires before consent, graded against CIPA, GDPR, CCPA/CPRA, and MHMD.
Run a free scan