Google Consent Mode v2: what it is, and which mode to choose

Consent Mode v2 is the signal your cookie banner uses to pass the visitor’s choice to Google tags (Analytics, Ads, Floodlight). It does not collect that choice: without a compliant banner behind it, it does nothing.

It tells Google tools what the visitor accepted, through four main parameters, each set to granted or denied:

Parameter What it controls
ad_storage Cookies and identifiers used for advertising
analytics_storage Cookies and identifiers used for analytics
ad_user_data Sending data about the visitor to Google for advertising
ad_personalization Personalised advertising (remarketing)

The last two are the ones “v2” added. The banner first declares a default state (consent default, everything denied for a visitor in Europe), then updates it when the visitor chooses (consent update).

Why Google has required it since March 2024

Google started enforcing its EU user consent policy in March 2024, when the EU’s Digital Markets Act (DMA) began to apply. Since then, without the ad_user_data and ad_personalization signals, Google Ads can no longer build audiences or run remarketing on visitors from the European Economic Area.

On 15 June 2026, Google went further: Consent Mode became the only setting that decides whether Google Analytics may collect Google Ads cookies and identifiers. The “Google Signals” setting now only links data to signed-in Google accounts.

Basic or advanced mode?

The mode decides what Google receives when a visitor rejects.

Basic mode Advanced mode
Before the choice Google tags do not load Tags load, with everything denied
If the visitor rejects Nothing is sent to Google, not even the rejection “Cookieless pings” are sent to Google
If the visitor accepts Tags load as usual Tags switch to normal mode
Data Google gets Only visitors who accept; the rest is estimated generically The pings are used to model conversions of visitors who reject

In advanced mode, according to Google’s documentation, the pings sent despite a rejection contain technical information (time, browser, referring page), the consent state, an ad-click indicator and a random number generated on each page.

In our view, advanced mode is a problem. Article 5(3) of the ePrivacy Directive requires consent for storing or reading any information on the visitor’s device, cookies included, and the EDPB’s 2023 guidelines read it broadly, covering pixels and requests a script makes from the device. A third-party script that loads and sends information about the browser to Google before consent, or despite a rejection, reads the visitor’s device. We have found no regulator decision on advanced mode itself. Basic mode avoids the question, and it is the one we recommend until regulators rule on it.

Consent Mode only governs Google tags, and only if the banner passes it a real choice. Meta Pixel, TikTok, Hotjar or a YouTube video ignore it: the banner has to block them until the visitor chooses.

It does not make Google Analytics exempt from consent either, even well configured (our guide to exempt cookies explains why). And it keeps no proof of the visitor’s choice: that is still the banner’s job. If the banner lets trackers through before the choice, Consent Mode protects you from nothing, as regulators’ fines show.

How to set it up

The simplest is for your banner to handle it: it declares the default state before any Google tag, then updates it after the choice. In Google Tag Manager, check that your Google tags have built-in consent checks turned on, and that non-Google third-party tags wait for consent.

Look at the commands Google tags receive, in a private window to start from scratch:

  1. Open the browser console (developer tools) and type dataLayer, or run Google’s Tag Assistant on the page.
  2. Before any click, you should see a consent default command with the four parameters set to denied.
  3. Make a choice in the banner: a consent update command should appear with the new state.

FAQ

Is Consent Mode v2 mandatory?

Not by law: it is a Google requirement. Without it, Google’s advertising features (audiences, remarketing, personalised conversion measurement) stop working for visitors in the European Economic Area. A site with neither Google Ads nor Google Analytics does not need it.

Does Consent Mode replace a cookie banner?

No. It passes on a choice, it does not collect one. You still need a compliant banner that asks for consent, and the banner is what updates Consent Mode.

Does this apply to your site?

Paste its address: Nodbar visits it like a first-time visitor, records what fires before consent and prepares a compliant banner. Free, no sign-up needed for the scan.