How to set up Consent Mode v2
Symptom: Audiences are shrinking and measurement is degrading for European traffic
Consent Mode v2 governs what your Google tags send based on a user's consent, and for European traffic it is required to keep audiences and full measurement working. This workflow wires the consent banner to pass all four signals, chooses between basic and advanced implementation, and validates the setup in the tag debugger before trusting the numbers.
A 47-point written audit of your Google, Meta or Shopping account, back in five business days.
Get your auditBook a call- A consent management platform or banner
- Google Tag Manager access
- A privacy review of what data may be sent
- The tag debugger for validation
- 1
Confirm the four consent signals
Consent Mode v2 uses four signals: analytics storage, ad storage, ad_user_data, and ad_personalization. Ensure your consent management platform can set all four based on the user's choices.
The two v2 additions, ad_user_data and ad_personalization, are what gate advertising data use and are required for European Economic Area traffic.
- 2
Wire the banner to the signals
Connect your consent banner so that a user's accept or decline updates the correct consent state before tags fire. In Google Tag Manager, configure default and updated consent states so tags respect the choice.
Set a sensible default, typically denied, until the user makes a choice, so nothing fires prematurely.
- 3
Choose basic or advanced
Decide between basic Consent Mode, which blocks tags until consent is granted, and advanced, which loads tags in a restricted state and sends anonymous cookieless pings even before or without consent.
Advanced recovers more conversions through modeling but needs a careful privacy review, which is the trade most measurement-serious advertisers make deliberately.
- 4
Implement the chosen mode
For basic, ensure tags are fully gated on consent. For advanced, configure tags to send the cookieless pings when consent is denied, carrying no identifiers.
Follow your privacy review precisely, since advanced mode sends signals from non-consented users that must contain no personal data.
- 5
Validate in the tag debugger
Use the tag debugger to confirm that consent states change correctly on accept and decline, and that tags behave as intended in each case. Verify all four signals are being set.
A misconfigured banner silently starves both bidding and audiences, so this validation is non-negotiable before trusting any reported number.
- 6
Monitor audiences and modeling
After launch, watch that remarketing audiences resume growing and that conversion modeling is working for declined users. A sudden audience decline usually points back to a consent misconfiguration.
Re-validate after any change to the banner or the site's tagging.
- Missing the two v2 signals, breaking audiences for European traffic
- A default consent state that fires tags before the user chooses
- Choosing advanced mode without a privacy review of what pings send
- Assuming it works without validating consent changes in the debugger
- Not re-validating after a banner or tagging change
Common questions
Want this checked on your own account?
A 47-point written audit of your Google, Meta, or Shopping account. Five business days, no sales call.
