Google Consent Mode v2
Google Consent Mode v2 ensures that Google vendors associated with a consent notice comply with an end-user's consent choices (called consent types) defined by Google. When a website visitor or app user indicates their consent choices, a consent check will adjust Google tag behaviors, and the end-user's consent choices are preserved across their interaction with the website.
Click here to read the Didomi blog post about Google Consent Mode v2.
Glossary
In the context of working with Google Consent Mode v2, your organization should be familiar with the following terminology used by Google:
Consent type
Indicates the type of storage. Click here to view the different consent types available for Google Consent Mode v2.
Consent state
End-users choice for a particular consent type. The consent state for each consent type can be granted or denied.
Consent check
Action that causes vendor tags to modify behavior based on the consent state for each consent type
Google consent types
The following consent types that can be set include:
ad_storage
Enables storage, such as cookies (web) or device identifiers (apps), related to advertising.
ad_user_data
Sets consent for sending user data to Google for online advertising purposes.
ad_personalization
Sets consent for personalized advertising.
functionality_storage
Enables storage that supports the functionality of the website or app, for example, language settings
personalization_storage
Enables storage related to personalization, for example, video recommendations
analytics_storage
Enables storage, such as cookies (web) or device identifiers (apps), related to analytics, for example, visit duration.
Basic vs Advanced consent mode
Google Consent Mode v2 supports two different modes that your organization can use to guide implementation (basic or advanced). The major difference between these two modes is how end-user consent impacts when and if your Google tags are loaded and the data transmitted to Google.
Tag loading
Blocked until end-user interaction with the consent notice
Loads with consent type defaults set to denied , unless configured otherwise
Data transmission
No data is sent before an end-user consents - not even the default consent status
When consent is denied, consent state and cookieless pings are sent
When consent is granted, cookies are written and all measurement data is sent.
Tag behavior after end-user interaction
Loads and executes consent mode APIs only when an end-user grants consent
Adjusts tag behavior based on end-user consent choice
Conversion and key event modeling
General model (less detailed modeling)
Advertiser-specific model (more detailed modeling)
Last updated