Playbook Tracking and analytics
Consent Mode v2 for ecommerce
Consent Mode v2 is how Google keeps measuring and advertising while respecting a shopper's consent choices. In many regions it is required. Here is what it is, why it matters, and how to set it up correctly.
Consent Mode v2 is how Google keeps measuring and advertising while respecting what each shopper consented to, and in much of the world it is no longer optional. If you serve users in the European Economic Area and want Google’s advertising and audience features to keep working, the v2 consent signals are required. Here is what Consent Mode is, why it matters, and how to implement it without breaking either compliance or measurement.
What Consent Mode v2 does
Your consent banner asks the shopper what they allow. Google Consent Mode takes that answer and adjusts how Google’s tags behave: full collection when consent is granted, limited cookieless signals when it is not, which Google can use to model conversions without storing identifiers. For most stores this is the practical heart of consent mode ecommerce work, where GDPR tracking consent and measurement have to coexist. The v2 update added specific signals for advertising features and audience personalization, which is why it became a requirement for using those features on EEA traffic.
Consent Mode is not a cookie banner. It is the wiring that makes your tags actually obey the banner, while preserving as much measurement as consent allows.
Why it matters
It keeps Google features working in required regions
For EEA traffic, Google requires the v2 signals to use advertising and audience features. Without them you lose personalization and audiences for that traffic and your measurement degrades, so implementing it is how you keep those capabilities at all.
It preserves measurement from non-consenting users
Rather than collecting nothing when a user declines, Consent Mode lets Google model conversions from limited, anonymized signals. You recover modeled data you would otherwise lose entirely, more complete reporting within the bounds of consent.
It future-proofs you as privacy rules tighten
Even where it is not strictly required today, a correct consent implementation is the direction every privacy regime is heading. Building it now means you are not scrambling when the next rule lands.
Setting it up
Consent Mode v2, implemented right
- A consent banner or CMP that integrates with Consent Mode
- Consent signals set before your tags fire, not after
- Analytics storage, ad storage, ad user data, and ad personalization signals configured
- Granted state: tags collect normally
- Declined state: limited, cookieless signals, verified
- Both states tested, so neither over-collects nor silently collects nothing
Consent Mode sits at the intersection of measurement and compliance, which is why it belongs in your tracking-analytics foundation alongside your server-side setup. It pairs naturally with server-side tracking and the Conversions API, which together let you respect consent while still measuring as much as consent permits.
If you are unsure whether your consent setup is both compliant and preserving the measurement it should, that review is exactly the kind of work a tracking audit is built to deliver.