Skip to content

Google Consent Mode v2 setup: basic vs advanced, and how to check it works

What Google Consent Mode v2 is, the four consent signals, basic vs advanced mode, how to set the default before tags run, and how to verify it in a browser.

Lukas Kontur · · 5 min read

Google Consent Mode is how your consent banner tells Google tags (Google Analytics, Google Ads, Floodlight) what the visitor chose. It does not block anything by itself: it sets consent signals, and Google's tags change their behaviour based on them. Version 2 added two signals for advertising. This guide explains the signals, the two ways to run it, and how to check in a browser that it really works.

The four signals you need to know

Google documents seven consent types; four of them control measurement and advertising (Google: consent mode overview):

SignalWhat it controls
analytics_storageStorage, such as cookies, for analytics
ad_storageStorage, such as cookies, for advertising
ad_user_dataSending user data to Google for online advertising
ad_personalizationPersonalised advertising

ad_user_data and ad_personalization are the two that "v2" added. Google states that consent mode users need to send these two in addition to ad_storage and analytics_storage (Google: set up consent mode). The other three types (functionality_storage, personalization_storage, security_storage) cover site features, recommendations and security.

Basic vs advanced mode

Google describes two implementations:

  • Basic: Google tags are blocked until the visitor interacts with the banner. Before consent, "no data is transferred to Google at all". Google then uses a general model to fill gaps.
  • Advanced: Google tags load immediately with the signals set to "denied". While consent is denied they send consent state and "measurements without cookies" (cookieless pings). Only after a grant do they send full measurement data. Google uses an advertiser-specific model.

What this means in a browser: with basic mode you see no requests to Google before consent. With advanced mode you do see requests to Google before consent, but no _ga or _gcl_au cookie. A scanner that sees Google requests before consent is therefore not automatically reporting a bug; it depends on which mode you chose and what your banner text promises.

Setting it up: the default comes first

Whatever tool you use, the order is the same:

  1. Default: set every signal to denied before any Google tag runs.
  2. Update: when the visitor clicks Accept or saves settings, send an update with the granted signals.

Google's direction is to call the default "on every page of your site before any commands that send measurement data", and it warns: "The order of the code here is vital." The gtag.js default from Google's guide:

<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}
  gtag('consent', 'default', {
    'ad_storage': 'denied',
    'ad_user_data': 'denied',
    'ad_personalization': 'denied',
    'analytics_storage': 'denied'
  });
</script>

Place it before the Google tag snippet. Google notes these values are placeholders that you set according to your own requirements. Its guide also describes a region parameter for regional defaults and wait_for_update, a delay in milliseconds that gives the consent tool time to send the update before tags send data.

Most consent platforms set the default and update for you:

Consent Mode only governs Google tags. Meta, TikTok, Hotjar and other tags ignore it; they need consent triggers or blocking from your consent tool.

How to check that it works

  1. Open your site in a new private window with the developer tools open (F12).
  2. In Network, filter for collect. Click a request to google-analytics.com or your server-side tagging endpoint and look at its parameters. The gcs parameter carries the consent state: G100 means both storage signals are denied, G111 means both are granted. Newer tags also send a gcd parameter with the state of each signal.
  3. Before any click, requests should either be absent (basic) or show denied (advanced), and there must be no _ga cookie.
  4. Click Reject: the state stays denied, no _ga appears, also after a reload.
  5. In a fresh window, click Accept: the state changes to granted and _ga appears.
  6. In Google Tag Manager preview, the Consent tab shows the default and update values for each event.

If you see Google requests without any consent state, or a granted state before anyone clicked, Consent Mode is missing or runs too late. The consent mode not detected guide and GTM Consent Mode v2 mistakes cover the usual causes. For a full banner test beyond Google, see how to test your cookie consent banner.

Sample scan

78 / 100

High risk · Trackers: 23 · Pre-consent tracking: yes

See sample report →

Check your site in 1 minute

Our free scan reads the Consent Mode default and update your site sends, compares them with what the browser actually does, and flags a mismatch. No signup needed. Run a free scan.

Get alerted when it breaks

A new GTM container version or plugin update can drop the default or send it too late. With monitoring, we re-scan your site on a schedule and email you when Consent Mode disappears or stops matching the banner. Create an account and add your site.

Last updated: