Journal · Consent Mode

What is Consent Mode v2? A plain English guide

5 June 20266 min readBy Walter Masseroni Gonzalez, Leon Aves, Daragh McCarthy and Alana Rossi

Consent Mode v2 is how your cookie banner tells Google’s tags what a visitor allowed. It is not a banner itself. It passes four signals: analytics_storage, ad_storage, ad_user_data and ad_personalization, the last two new in v2. Google expects a consent signal for EEA visitors on its tags, and basic or advanced mode decides what Google receives after a rejection.

Each signal answers one question for Google’s tags, and Google’s consent mode overview defines all four, alongside three other storage types for functionality, personalisation and security. The first two below come from the original Consent Mode. Version 2 added the last two.

Four signals, four separate questions.

SignalWhat it decidesAdded in
analytics_storageAnalytics cookies, such as GA4’sv1
ad_storageAdvertising cookies, used for attributionv1
ad_user_dataSending user data to Google for advertisingv2
ad_personalizationUsing data for personalised adsv2
The first two signals cover what a tag may store on the device. The two added in v2 cover what may go to Google for advertising and how it may be used.

A visitor can grant one signal and deny another. The two v2 signals are the ones most often mixed up, so we split them apart in ad_user_data vs ad_personalization.

No. Consent Mode carries a choice, and it does not ask for one. Google’s overview is plain about this: “You are responsible for obtaining users’ consent”. You still need a banner or a consent management platform to ask the visitor and record the answer. Passing the signals is one half of what a platform does; capturing and proving the choice is the other.

It depends on where your visitors are. Google’s EU user consent policy covers the EEA, the UK and Switzerland, but the duty to send a consent signal is narrower. If you measure EEA visitors with Google tags, or use audience or ad personalisation features, you have to pass their choices to Google. Consent Mode is one way to do that, and the TCF is another.

For UK and Swiss traffic, Google says it does not expect advertisers to send a verified consent signal. The policy’s consent duty still applies there. Outside those three regions the policy does not apply at all.

That includes Canada, though a Canadian site can still need Consent Mode for its EEA visitors and for Quebec. We cover that case in do Canadian websites need Google Consent Mode v2.

If an advertiser does not act within a reasonable time, the policy lets Google suspend audience features such as remarketing, along with conversion measurement. None of this replaces the law: you still need valid consent under your local rules. The same page says Google’s IP based ads measurement and personalisation start launching in these regions from August 2026, so check it again before you rely on this summary.

What is the difference between basic and advanced?

Version and mode are separate questions. v1 or v2 says which signals exist; basic or advanced says when your tags load. The same four signals can run either way, and the names undersell the difference.

Basic means Google tags do not load at all until the visitor consents. Clean and simple, but when someone rejects, Google receives nothing, not even a cookieless signal that a visit occurred. Google Ads can then apply only a general model, not one built from your own site.

Advanced means tags load before the choice, respect it completely once made, and send cookieless pings when consent is denied. No cookies are set and no identifiers are stored, but Google learns that a conversion happened, with no cookie to tie it to. Those pings are the raw material for conversion modelling. Google can use them to estimate some denied conversions with a model specific to your account, but only when that account meets its eligibility thresholds, which we list in what consent modelling is.

Same four signals. Different data after a rejection.

Basic

Tags wait for consent

  • No Google request after a rejection
  • General model only, in Google Ads

Advanced

Tags load, then follow the choice

  • No cookies set when denied
  • Cookieless pings when denied
  • Account specific model, if eligible
Basic and advanced read the same four signals. Only advanced sends cookieless pings after a rejection, and Google builds an account specific model from them only when the account meets its eligibility thresholds.

Where should the default state be set, and for which regions?

The default is the state your tags see before the visitor chooses, and it has to be set before any Google tag fires. A tag that loads first runs without consent information. Google’s consent mode setup guide lets you scope defaults by region: denied for visitors where the law needs consent first, granted elsewhere if your legal advice allows it. The wait_for_update setting tells tags how many milliseconds to wait for the banner’s update before they send anything; Google’s own examples use 500.

How do you tell which one you are running?

  1. Open your site in a private window

    Open the browser network tab before touching the banner, and filter for requests to Google domains. What fires before you make a choice is the whole diagnostic.

  2. Read what happens before you consent

    If no Google requests appear at all until you accept, you are on basic. If requests fire with gcs or gcd parameters showing a denied state, you are on advanced.

  3. Confirm the defaults in Tag Assistant

    The consent tab shows the four signals and their state on page load. The defaults should be set before any tag fires, then update when the visitor chooses.

For the full walkthrough, including how to decode the gcs code and rule out a broken tag that only looks like basic mode, see basic vs advanced Consent Mode, which one you are running.

Velo runs the advanced implementation by default and sets the default state as soon as it loads, so install it ahead of your other tags. It also keeps a consent log, so you can prove what was set and when.

Your next step in website privacy.

Velo sets your consent defaults, passes the four signals to Google’s tags and keeps a record of every choice your visitors make.

Common questions

What is Consent Mode v2 in plain English?

It is the way your cookie banner tells Google’s tags what a visitor allowed. Four signals cover analytics cookies, advertising cookies, sending user data to Google for ads, and personalised ads. Google’s tags read them and change what they store and send.

Is Consent Mode v2 a cookie banner?

No. It passes a visitor’s choice to Google’s tags but does not ask for it. You still need a banner or a consent management platform to collect and record consent.

Is Consent Mode v2 required?

For EEA visitors, Google requires you to pass consent choices if you measure them with its tags or use audience or ad personalisation features, through Consent Mode or the TCF. For UK and Swiss traffic it does not expect a verified signal, and elsewhere, including the US, its policy does not apply. It is not a legal requirement on its own: you still need valid consent under your local rules.

What is the difference between Consent Mode v1 and v2?

Version 1 had two signals, ad_storage and analytics_storage. Version 2 adds ad_user_data and ad_personalization, which say whether user data may go to Google for advertising and whether it may power personalised ads.

Does Consent Mode v2 recover conversions when visitors reject cookies?

No. Rejected visitors are not identified or followed with cookies. In advanced mode Google receives cookieless pings and may model some conversions, but only when your account meets its eligibility thresholds. Modelled figures are estimates, not observed conversions.

Keep reading


Start with a scan

See what your homepage already loads before you install anything. The free scanner reads the page and your public Tag Manager container.


A first pass, not a verdict. Four checks on your homepage, and we open your container.
V
Free scanNo account needed

Free for one site and 1,500 monthly sessions. Pro from €7 a month, plus VAT, for unlimited sites.

Step by step installs for WordPress, Shopify, Webflow, Wix and more.

Free for one site

Banner, scan and consent records for one site, free. Pro from €7 a month, plus VAT, for unlimited sites.