Google Consent Mode v2 explained for small businesses

If you run Google Analytics, Google Ads or Tag Manager on a website with visitors in Europe, you have probably been told to "enable Consent Mode v2". It sounds technical, but the idea is simple: your cookie banner and your Google tags need to speak the same language about what the visitor allowed.

#What is Google Consent Mode?

Consent Mode is a feature of Google's tags. Your consent banner sets a consent state, "granted" or "denied", for several purposes, and Google tags read that state and adjust what they do. If a purpose is denied, the tag does not set the related cookies and limits the data it collects.

It is a technical bridge, not a legal basis. The banner is still responsible for obtaining valid consent. Consent Mode only passes the result to Google.

#The four main signals

Google also supports functionality_storage, personalization_storage and security_storage for other uses.

#Why "v2" matters

In 2023 Google added the two new signals and announced that, from March 2024, advertisers serving people in the European Economic Area and the United Kingdom need to send them to keep using audience and conversion features. In practice, if you advertise with Google to European visitors and your banner does not send ad_user_data and ad_personalization, parts of your measurement and remarketing stop working.

If you only use Google Analytics without ads, v2 is still the version to set up, because a banner that sends all four signals keeps your setup ready if you start advertising.

#Default state and update

Two moments matter:

1. The default. Before the visitor chooses, the banner sets every signal to "denied" for regions where consent is required, and this must happen before Google tags load.
2. The update. When the visitor chooses, the banner sends the new state. Tags that were waiting can now run, and the signals follow the choice from then on.

If the default is set after the tag, or never, the tag may start in the wrong state. This ordering mistake is the most common reason for a Consent Mode setup that "looks right" but collects data too early.

#Basic or advanced mode?

Google describes two ways of implementing it:

• Basic mode. Google tags are blocked entirely until the visitor consents. Nothing is sent to Google before the choice. This is the more conservative option and the easier to defend in Europe.
• Advanced mode. Tags load with the default "denied" state and send limited, cookie-less signals ("pings") before consent. Google uses these to model conversions it cannot observe. Regulators and lawyers do not all agree that this is acceptable without consent, so treat it as a decision for your own risk assessment, and mention it in your cookie policy if you use it.

#How to set it up

1. Choose a banner that supports it, or configure the signals yourself through Google Tag Manager's consent settings.
2. Declare the defaults as "denied" for every signal, for visitors in the EEA, the UK and any region where you want to ask first. Do this before any Google tag loads.
3. Map your categories to the signals: statistics to analytics_storage, marketing to ad_storage, ad_user_data and ad_personalization.
4. Update the state the moment the visitor chooses, and again when they change their mind from your cookie settings link.
5. Describe it in your cookie policy, including which mode you use and what Google receives.

#What Consent Mode does not do

• It does not collect consent. A banner does that.
• It does not control tools that are not from Google. Other trackers, such as a Meta pixel, a chat widget or a heatmap tool, need to be blocked by the banner itself until consent is given.
• It does not make an unlawful setup lawful. If your site loads Google tags before any choice, the choice is not respected, whatever the signals say.

#How to check that it works

1. Open your site in a private window and look at the network requests before touching the banner. Google requests should not set analytics or advertising cookies.
2. Reject all, and check that nothing changes.
3. Accept analytics only, and confirm that advertising cookies are not set.
4. In Google Tag Assistant or the tag's consent diagnostics, confirm the four signals change with each choice.

Repeat this when you add a tag or change the banner. A weekly scan in a real browser catches what a manual check misses.

#FAQ

#Is Consent Mode v2 mandatory?

Google requires it from advertisers who use audience features and conversion measurement for visitors in the EEA and the UK. The GDPR itself does not mention it; what the law requires is valid consent, which the banner must obtain.

#Does Consent Mode replace a cookie banner?

No. It needs a banner, or another consent mechanism, to tell it what the visitor chose.

#Which mode should I choose, basic or advanced?

Basic is the safer starting point in Europe because nothing is sent before consent. Advanced can recover some measurement but sends signals before the choice, so assess it with your own advisers.

#Do I need Consent Mode if I do not use Google Ads?

If you only use Google Analytics, the two original signals are the most relevant. Setting up v2 anyway keeps you ready if you advertise later.

#Does it work with Google Tag Manager?

Yes. The default state must be set before the container loads, and tags in the container should be configured to respect consent.

#Where can I read Google's own documentation?

Google publishes the consent API reference in its Tag Platform documentation, linked below, and updates it as the product changes.

#Sources

• Google Tag Platform: manage consent settings
• ePrivacy Directive 2002/58/EC, Article 5(3), EUR-Lex