Guides

How to check Consent Mode v2 in the browser

Updated September 2026 · 5 min read

Consent Mode lets Google’s tags adjust what they do to the visitor’s consent choices. Version 2 added two signals, ad_user_data and ad_personalization, to the original ad_storage and analytics_storage, and Google asks for them to use its advertising features with visitors in the European Economic Area. A banner that looks right can still send the wrong state. You can check it in Chrome DevTools.

The four signals

1. A default before the measurement tags

The initial state must be set before Google’s measurement tags send anything. How to check it depends on the implementation:

2. The state after the banner

Accept or reject in your banner and check that the effective state matches the choice. With gtag.js, look for the consent update commands in the configured data layer; with Tag Manager templates, check it in Tag Assistant. Rejecting can keep a state that was already denied, and in basic mode the tags can stay blocked without loading. Before repeating with the other choice, close every private window or clear the site’s data, so the first choice isn’t remembered.

3. What GA4 requests carry

In the Network tab, filter by collect. When they are present, check two parameters:

In advanced Consent Mode, GA4 can send cookieless pings while analytics_storage is denied; denying only the advertising signals doesn’t imply the same behavior. In basic mode, the tags stay blocked until the corresponding consent is granted; rejecting it doesn’t enable them.

4. Tags that don’t follow Consent Mode

Consent Mode controls Google’s tags. The Meta Pixel and other tags only respect the visitor’s choice if your consent tool or tag manager blocks or configures them. After rejecting advertising consent, filter the Network tab by facebook.com/tr and check whether new requests appear that your setup should have blocked.

This guide is about checking the technical setup. It is not legal advice.