GoogleFrameworkGoogle Consent Mode v2

Google Consent Mode v2

Connect visitor consent choices with Google Analytics, Google Ads and other Google tags — and keep the consent state updated automatically.

Built-in CookieHub support · GTM and gtag.js compatible
Consent stateregion: eumode: basicstate: updatedVisitor choiceanalytics acceptedCookieHubcategory → parameterGoogle consent stategtag consent updateanalytics_storagegrantedad_storagedeniedad_user_datadeniedad_personalizationdenied
Type
Consent signalling framework
Works with
Google Ads, Analytics and Google tags
Modes
Basic and Advanced
Consent parameters
7
CookieHub support
Built in
Overview

What Google Consent Mode v2 actually does.

Consent Mode tells Google tags what a visitor has agreed to. Supported tags read that state and adjust their own behaviour: whether they may use cookies, send ad data, or use it for personalisation.

It does not collect consent itself. A consent management platform presents the choice and stores the decision; Consent Mode sends the resulting state — as a default when the page loads, and as an update once the visitor has chosen.

CookieHub collects and manages the visitor’s choice. Consent Mode carries that choice to Google tags.

Page lifecyclegtag.js / GTM
  1. 01Page loadstag queued
  2. 02Default consent state appliedconsent default
  3. 03Visitor makes a choicebanner
  4. 04CookieHub updates the Google consent stateconsent update
  5. 05Supported Google tags respond to the statetag behaviour
Signal flow

From visitor choice to Google consent state.

Pick a visitor state to see the consent parameters CookieHub sends to Google.

Visitor state
Visitor choiceNo choice yet

The visitor has arrived and the banner is showing. Nothing has been agreed to.

CookieHubApplies configured defaultsevent: consent defaultregion: eustored: no
Google consent statedefaultanalytics_storagedeniedad_storagedeniedad_user_datadeniedad_personalizationdenied
Visitor choiceAccepted

The visitor accepted the categories connected to Google analytics and advertising.

CookieHubUpdates the consent stateevent: consent updatecategories: 4 of 4stored: yes
Google consent stateupdatedanalytics_storagegrantedad_storagegrantedad_user_datagrantedad_personalizationgranted
Visitor choiceDeclined

The visitor declined the non-essential categories, or withdrew a previous choice.

CookieHubUpdates the consent stateevent: consent updatecategories: 0 of 4stored: yes
Google consent stateupdatedanalytics_storagedeniedad_storagedeniedad_user_datadeniedad_personalizationdenied

Illustrative signal behaviour for one configuration. The parameters CookieHub sends depend on your categories, your region settings and the choice the visitor actually makes — this is not a universal configuration.

Consent signals

The parameters Google listens for.

Seven consent parameters, each mapped from a CookieHub category or set as a fixed state.

ParameterPurposeCookieHub category / sourceExample state
ad_storageStorage used for advertising, including advertising cookies.Marketingdenied
analytics_storageStorage used for analytics, such as visit and session measurement.Analyticsgranted
ad_user_dataSending user data to Google for advertising purposes.Marketingdenied
ad_personalizationUsing the data for personalised advertising.Marketingdenied
functionality_storageStorage that supports website functionality, such as language.Preferencesgranted
personalization_storageStorage used to personalise the website, such as recommendations.Preferencesgranted
security_storageStorage related to security, authentication and fraud prevention.Necessarygranted
CookieHub sets each parameter automatically from the visitor’s category choices, using a fixed mapping (IAB TCF purposes in TCF regions). The example states show one common European setup where analytics and preferences were accepted and advertising was not.
Implementation modes

Basic or Advanced Consent Mode?

Both modes use the same Consent Mode parameters. The key difference is what Google tags can do before a visitor makes a choice.

Before choiceAfter choiceBasic modemode: basic
  1. Page loadtag queued
  2. Consent-dependent tags waitheld
Visitor chooses
  1. Allowed tags activategranted
Advanced modemode: advanced
  1. Page loadtag loaded
  2. Denied defaults applieddenied
  3. Cookieless signals may be sentcookieless
Visitor chooses
  1. Consent state updatesconsent update
Basic mode

Strict pre-consent blocking

Consent-dependent Google tags wait until the required visitor choice is available.

Advanced mode

Measurement continuity where permitted

Supported Google tags can run with denied defaults and adjust behaviour when the visitor’s choice changes.

CookieHub + Google

Consent signals without manual state management.

CookieHub applies the defaults, updates the state and maps your categories to Google’s parameters.

See how consent management works
01Configure once
  • Region-aware behaviour

    region rules

    Apply the appropriate configured consent model by visitor location.

  • Parameter mapping

    category → parameter

    CookieHub maps its categories to Google consent parameters automatically.

  • Default states

    consent default

    Apply configured consent defaults when the page loads.

02CookieHub manages the state
Default stateappliedVisitor choicereceivedUpdated statesent
  • Real-time updates

    consent update

    Update consent state when the visitor changes their choice.

  • Consent records

    stored decision

    Maintain consent records of visitor decisions in CookieHub when the feature is enabled.

03Google receives the right signals
Google consent stateexampleanalytics_storagegrantedad_storagedeniedad_user_datadeniedad_personalizationdenied
  • GTM / gtag support

    gtm · gtag.js

    Work with Google Tag Manager or supported direct Google tag implementations.

The Google consent state shown is an example of one configuration, not a universal set of values.
Implementation

Connecting Consent Mode.

Three phases, from adding CookieHub to confirming the signals Google receives.

  1. 01

    Connect

    Connect CookieHub to the Google tag environment already used by the site.

    1. 01Add CookieHub to the website.
    2. 02Connect Google Tag Manager or the supported Google tag implementation.
  2. 02

    Configure

    Choose the Consent Mode behaviour and review how CookieHub choices map to Google signals.

    1. 03Configure the consent model for the relevant visitor regions.
    2. 04Choose Basic or Advanced Consent Mode where appropriate.
    3. 05Confirm category-to-parameter mapping.
    4. 06Publish the consent configuration.
  3. 03

    Verify

    Confirm that the correct consent state reaches Google.

    1. 07Run the Consent Mode Checker.
    2. 08Verify default and updated states.
    verifiedRecheck when tags or consent settings change.
Verify your setup

Is Consent Mode working on your site?

Check whether Google Consent Mode signals are present and behaving as expected.

No account needed
Consent Mode v2 detectedexample.com
  • analytics_storagegranted
  • ad_storagedenied
  • ad_user_datadenied
  • ad_personalizationdenied
  • Default statedetected
  • Consent updatedetected
View full reportillustrative result
Google Tag Manager

Connect Consent Mode through GTM.

Where GTM already manages your tags, CookieHub supplies the consent state the container reads.

  • CookieHub loads the consent configuration.
  • Consent defaults are available before consent-dependent tags run.
  • Consent updates follow visitor choices.
  • Existing GTM environments can remain the central tag-management layer.
Container viewconceptualGTM containergtm-xxxxxxCookieHub consent statedefault · update
  • Google Analyticsanalytics_storage
  • Google Adsad_storage
  • Conversion Linkerad_user_data
Compatibility

Works across Google’s consent-aware stack.

The Google products and tags that read the consent state CookieHub sends.

  • Google Analyticsanalytics_storage
  • Google Adsad_storage
  • Google Tag Managerconsent template
  • Floodlightad_user_data
  • Conversion Linkerad_storage

Built to work with Google’s consent ecosystem.

CookieHub is a Google certified CMP partner and an IAB Europe registered CMP. Certified CMP requirements apply in specific Google publisher and advertising contexts rather than to every Consent Mode implementation — check which requirements apply to your own use of Google products.

Google Certified CMP PartnerIAB Europe TCF registered CMP
FAQ

Google Consent Mode v2 questions.

It is Google’s way of receiving a visitor’s consent state. The website sends consent parameters, and supported Google tags adjust their behaviour based on them. Version 2 added ad_user_data and ad_personalization to the original parameters.

No. A consent management platform such as CookieHub presents the choice to the visitor and stores the decision. Consent Mode communicates the resulting state to Google-supported tags.

In Basic mode, consent-dependent Google tags are held back until the visitor’s choice is available. In Advanced mode, supported tags load with denied defaults, may send cookieless signals, and then adjust when the consent state updates.

ad_user_data covers sending user data to Google for advertising purposes. ad_personalization covers using that data for personalised advertising. Both were introduced with Consent Mode v2 and are typically mapped from a marketing category.

No. GTM is a common path because it centralises tag management, but Consent Mode also works with supported direct Google tag (gtag.js) implementations.

CookieHub applies your configured consent defaults, sends consent updates when the visitor chooses, and maps CookieHub categories to Google’s consent parameters automatically. You choose the consent model and the mode; the category-to-parameter mapping is set by CookieHub.

Run the CookieHub Consent Mode Checker against a page, then confirm in Google’s Tag Assistant that a default state is set before consent and that an update follows the visitor’s choice.

No. Consent Mode carries a consent state; it does not ask for consent. A banner or equivalent consent interface is still what collects the visitor’s choice.

Version 2 added two parameters, ad_user_data and ad_personalization, next to the original analytics_storage and ad_storage. In the first generation Consent Mode was optional and mainly enabled conversion modelling; since March 2024 Google requires the v2 signals from advertisers who measure or personalise ads for visitors in the European Economic Area, and recommends sending them through a Google-certified CMP.

It depends on the Google products, advertising features and measurement uses on your site, and on Google’s applicable policies. For visitors in the European Economic Area, the UK or Switzerland, Google has required Consent Mode v2 signals since March 2024 to keep features such as conversion measurement, remarketing and personalised ads working. Not every Google Analytics installation is affected in the same way. Elsewhere it is generally optional, but it still lets Google tags respect each visitor’s choice consistently.

Any business running Google Ads or Google Analytics, and the agencies working for them: advertisers who need accurate conversion data, publishers who monetise with Google products, marketing teams that rely on remarketing and audiences, and web agencies that implement consent banners for clients.

It depends on the mode. In Basic mode, Google tags wait for consent, so nothing is sent for visitors who decline. In Advanced mode, supported Google tags load with consent denied and send cookieless pings, which Google can use for conversion modelling when its eligibility requirements are met. That can keep reports closer to reality and give Smart Bidding more complete data, but the effect is not guaranteed and depends on your setup and traffic.

No. Consent Mode is Google’s way of receiving the consent state; it does not collect consent and does not satisfy GDPR, the ePrivacy Directive or Google’s EU user consent policy on its own. A compliant setup still needs a consent banner that blocks consent-dependent cookies until the visitor has chosen, which is what CookieHub provides, with Consent Mode carrying the result to Google.

A Google-certified CMP has been reviewed by Google for its Consent Mode integration and is listed among Google’s CMP partners. Publishers monetising with AdSense, Ad Manager or AdMob in the EEA, the UK and Switzerland must use a certified CMP, and Google recommends one for advertisers too, so the Consent Mode v2 signals are set up the way Google’s tags expect.

Yes. CookieHub is a Google-certified CMP partner and supports Consent Mode v2 in both Basic and Advanced mode, with the four consent parameters mapped from your cookie categories.

Legal note

Disclaimer

This page describes how consent signals are passed to Google tags. It is technical guidance, not legal advice, and it does not describe every possible configuration — which consent model applies to your visitors depends on the regulations relevant to your site.

Google Consent Mode v2

Send the right consent signals to Google.

Connect CookieHub to your Google tags, configure Consent Mode and verify that the right signals are being sent.

  • 14-day trial
  • No card required