What Is Google Consent Mode v2?
·
Consent Mode v2 is Google's framework for signaling a website visitor's cookie consent status to Google tags — Google Ads, Google Analytics, Floodlight — so those tags adjust their behavior instead of firing unconditionally. It defines consent signals, including ad_storage and analytics_storage, plus ad_user_data and ad_personalization added in v2, that a consent management platform sets to granted or denied based on the visitor's choice. Depending on the mode implemented, tags either don't fire without consent (basic) or fire in a cookieless, modeled form (advanced).
In practice
Consent Mode v2 sits between a site’s consent management platform (CMP) and Google’s tags. When a visitor makes a cookie choice, the CMP updates the consent state via gtag('consent', 'update', {...}), and every Google tag on the page reads that state before deciding what to send. In basic mode, tags are blocked from loading entirely until consent is granted — no requests reach Google without an explicit yes. In advanced mode, tags still load but send cookieless, consent-aware pings that Google Ads and GA4 use to model conversions and sessions that consent didn’t allow to be measured directly.
Why it matters
Google has required valid Consent Mode v2 signals for advertisers serving the EEA to keep using Google Ads features that rely on personalized measurement, such as remarketing and conversion tracking. Sites without valid v2 signals can see those features restricted for EEA traffic, independent of whether the site is otherwise compliant with GDPR or the ePrivacy Directive.
Common confusion
Consent Mode v2 is a technical signaling protocol, not a consent banner, a CMP, or a legal compliance mechanism by itself — it only carries the consent decision a CMP already made through to Google’s tags. Implementing it correctly does not make a site GDPR- or ePrivacy-compliant on its own; that depends on the CMP, the legal basis used, and the disclosures shown to visitors. This covers technical implementation, not legal advice.
How to check
In Google Tag Manager, the Consent Overview panel (Admin > Container Settings, or the dedicated Consent Overview view) shows which tags respect which consent types. In GA4, DebugView and the browser’s Network tab — filtering requests to google-analytics.com or googleads.g.doubleclick.net — show whether requests are cookieless (Consent Mode restricting data) or full requests (consent granted).
Related entries
Consent Mode v2 signals directly affect how much traffic GA4 buckets as Unassigned and interact with first-party tracking setups. For implementation help, see Consent Mode v2 services.
Related entries
- Knowledge BaseWhat Is GA4 Unassigned Traffic?What GA4's Unassigned channel is, why sessions land there, and how to check the acquisition report for the underlying cause.
- Knowledge BaseWhat Is First-Party Tracking?What first-party tracking means technically — same-domain cookies and endpoints — and why it isn't a consent bypass.
- ServiceConsent Mode V2
Not sure whether your tracking is actually broken?
Start with a Health Check — a fast, read-only diagnosis that tells you what is wrong before you spend anything fixing it. Prefer email? Send your store URL and one sentence about what looks off.