Privacy & first-party
What is Google Consent Mode v2?
Google’s framework for adjusting how its tags behave based on a user’s consent choices — required to use Google Ads/Analytics features for EEA users.
Definition
Consent Mode v2 is Google’s mechanism for communicating a user’s consent choices to Google tags (GA4, Google Ads, Floodlight). Based on consent signals, tags either collect normally, collect cookieless "pinged" signals, or don’t fire.
V2 added two parameters — `ad_user_data` and `ad_personalization` — that Google now requires for serving personalized ads and using audience features to EEA users.
Why it matters for agencies
For any agency with EEA traffic, Consent Mode v2 is mandatory to keep Google Ads audiences and conversion features working. A missing or misconfigured setup silently degrades remarketing and modeling.
It’s also a frequent source of "the tag is blocked and nobody noticed" — a consent banner that defaults to denied without Consent Mode wired up can zero out a client’s data while looking fine.
Google Consent Mode v2 in Phloz
Consent configuration is part of the tracking setup Phloz documents per client at onboarding, so an agency can verify Consent Mode v2 is actually wired up rather than assumed — closing one of the most common silent-data-loss gaps.
Frequently asked questions
- Is Consent Mode v2 required everywhere?
- It’s required to use Google Ads personalization and audience features for users in the EEA/UK. Outside those regions it’s good practice but not gating. Most agencies implement it globally for consistency.
- What’s the difference between basic and advanced Consent Mode?
- Basic Mode blocks Google tags entirely until consent; Advanced Mode loads tags in a cookieless state that sends anonymized pings, enabling conversion modeling for the un-consented. Advanced recovers more data but is more complex to configure correctly.
Related terms
Other tracking-infrastructure concepts agencies run into alongside this one.
14 days free · No credit card · Starter tier free forever