Cookie banner

Google Consent Mode v2

The cookie banner sets Google Consent Mode v2 to denied by default and updates it with the visitor's choice. Learn the signal mapping and the options for Google tags.

Updated 3 November 20261 min read

Google Consent Mode lets Google tags adapt to the visitor's consent. Privacyboard implements version 2: all signals start as denied and update when the visitor chooses.

#Signal mapping

Visitor choiceSignals set to granted
Preferencesfunctionality_storage, personalization_storage
Statisticsanalytics_storage
Marketingad_storage, ad_user_data, ad_personalization

security_storage is always granted. After each choice the banner also pushes an event to the data layer with the state of each category, which you can use in Tag Manager.

#Google tags: two ways to handle them

In the banner settings, Google tags has two modes:

  • Block until consent (strictest). Google tags such as Google Analytics, Google Ads and Tag Manager are held back entirely until the visitor accepts the matching category. This is the default.
  • Consent Mode. Google tags may load before consent but behave according to the denied or granted signals. In Tag Manager, also set the tags to wait for consent.

Choose the first if you want no request to Google before consent. Choose the second if you rely on Consent Mode modelling, and review the rules of your data protection authority.

#Tag Manager

Tags that a Tag Manager container loads cannot be seen by the page scan. Keep Google tags on Block, or use Consent Mode and set the tags in Tag Manager to require consent. Install the banner with the Consent Initialization – All Pages trigger. See Install the banner.

#FAQ

Google requires it for personalised advertising and some measurement features for users in the EEA. For analytics only, you can keep Google tags on Block.

It sets the consent state in the page. Google tags read it, according to their own configuration.

Privacyboard is a guidance tool, not legal advice. This page describes what the product does today. Found something unclear or out of date? Write to antoine@unmake.io.