Consent Mode v2 matters most when you use Google advertising features in regions where consent choices affect how those features can operate. This guide focuses on implementation and validation, not legal advice, and it explains how to test whether the required signals are being sent in the right order.
What v2 adds over v1
v1 introducedanalytics_storageandad_storage. v2 adds two additional consent types. If you also operate a server-side container, the same signals need to flow through yourserver-side consent setup— they do not bypass it.
- ad_user_data: Controls whether user data can be sent to Google for advertising-related measurement use cases, including enhanced conversions.
- ad_personalization: Controls whether user data can be used for personalised advertising and remarketing audiences.
If you use Google tags in consent-sensitive advertising or measurement setups, you should review whether all four signals are being sent. Only transmitting the two original v1 signals can leave newer consent-dependent features partially configured, and it can compound any underlyingGDPR-related GA4 compliance gapsyou already had.
Basic vs advanced mode
Basic:Tags do not load until consent is granted. No Google data is sent before consent. This is simpler to reason about, but it also means less pre-consent measurement context and less input for consent-aware modeling.
Advanced:Tags load immediately. Anonymous cookieless pings can be sent before consent, then full data collection resumes only after consent is granted. This can improve modeled reporting for eligible properties, but it should be chosen deliberately with your CMP and legal approach in mind. UK teams should also review this againstUK PECR regulations and GA4rather than treating Advanced mode as automatically compliant.
Set defaults before any tags fire
Use the Consent Initialization trigger so the default consent state is available before other Google tags evaluate whether to fire. Many implementations set denied defaults for the regions where consent must be established first, then update the state after the CMP resolves the user choice. If you use wait_for_update, treat the value as an implementation detail to test, not a universal default. A wait_for_update value shorter than your CMP's typical initialization time will cause GA4 to fire before consent is resolved, defeating the purpose. Test this value against your CMP's actual timing on a slow mobile connection.
Update consent after the user chooses
Install your CMP's GTM Community Template and configure it to map consent categories to signals: marketing / advertising to ad_storage, ad_user_data, and ad_personalization; analytics to analytics_storage. The CMP template fires the consent update event when users make a banner choice (accept, reject, or partial). Verify it fires for all three interaction paths.
Enable built-in consent checks on GA4 and Ads tags
In your GA4 and Google Ads tags, verify the relevant consent checks are enabled and that the tags react to the signals your CMP sends. In advanced implementations, Google tags can send cookieless pings before consent and resume fuller measurement after consent is granted.
Verify signals in GTM preview mode
Load the site in GTM Preview mode without interacting with the consent banner. In the Network tab, inspect requests to Google endpoints and confirm consent parameters are present before and after the banner interaction. Then use the GTM Consent Overview to verify each tag sees the expected granted or denied state.
Confirm signals in GA4 consent settings
In GA4 Admin > Data Settings > Consent Settings, check whether GA4 reports receiving consent signals for the traffic you expect. If the interface shows no signals received, review whether the default consent command is firing early enough and whether the CMP is actually updating all relevant consent types.
Want to verify your Consent Mode v2 implementation is transmitting all four signals correctly?
Common implementation mistakes
The most frequent implementation failure is placing the consent default tag on a Page View trigger instead of a Consent Initialization trigger. Page View fires after other tags on the same trigger, which means GA4 and Ads tags may fire without any consent state set. The Consent Initialization trigger is specifically designed to fire before all other triggers — seeCMP and GA4 timing validationfor the browser checks that catch this in practice.
The second most common mistake is mapping only two of the four signals. Teams that upgraded from v1 often updateanalytics_storageandad_storagebut never addad_user_dataandad_personalization. GA4 Admin Consent Settings will show partial signal receipt in this case.
Consent mode v2 checklist
- Default consent behavior is defined on the Consent Initialization trigger for the regions where you need it
- Consent Initialization trigger used, not Page View trigger, for the default tag
- Any wait_for_update value is tested against your CMP timing instead of copied as a universal setting
- CMP template fires consent update in GTM Preview after user interaction with banner
- All four signals mapped in CMP template: ad_user_data and ad_personalization included
- GA4 and Ads tags have built-in consent checks configured
- GA4 Admin Consent Settings shows signals received for the traffic where you expect consent signals to be present
- Network requests and GTM Preview both show the expected consent parameters before and after user choice
Related guides
CMP and GA4 Timing Validation
How to verify your CMP fires before GA4 tags and what the consequences are when it does not.
GDPR and GA4 Compliance
The full legal and technical requirements for GDPR-compliant GA4, including DPA and retention settings.
Consent Mode: Analytics vs Ads
How the same consent signals affect GA4 and Google Ads differently, and what data each loses.
Consent Mode v2 and Unassigned Traffic
How consent changes can contribute to Unassigned traffic and what else you should verify before drawing a conclusion.
Verify your consent mode v2 implementation
G4 Audits checks your Consent Mode signals, CMP integration, and related tagging configuration across your GA4 property.