Google Consent Mode Tag Setup Guide (BETA)

Consent mode (beta) allows you to adjust how your Google tags behave based on the consent status of your users. You can indicate whether consent has been granted for Analytics and Ads cookies. Google’s tags will dynamically adapt, only utilizing measurement tools for the specified purposes when consent has been given by the user.

Tips

To allow the Google Consent Mode tag to dynamically adapt to users consent status, we recommend the following:

• Omit the Google Consent Mode tag from Consent Management so that it always fires.
• If you use Google Analytics, Ads, or Floodlight tags, omit those tags from Consent Management as well.

When configuring the Google Consent Mode tag, do the following:

• Set Automatically read from Tealium Consent Cookie to true.
• Map Google Ads and Google Analytics consent values to the appropriate tag variables.

Tag configuration

Navigate to the Tag Marketplace to add a new tag. Read the Tag Overview article for general instructions on how to add a tag.

When adding the tag, configure the following settings:

• Automatically read from Tealium Consent Cookie
  If set to true, Google consent will be set based on the Tealium Consent Manager. See the other configuration descriptions for the exact behavior.
• Ad Storage
  If the integration with Tealium Consent Manager is enabled and partial consent is given, this sets ad_storage_consent value to granted. When full consent is given, granted is set.
• Analytics Storage
  If the integration with Tealium Consent Manager is enabled and partial is given, this sets analytics_storage_consent value to granted. When full consent is given, granted will be set.
• Ads Data Redaction Mapping
  When ads_data_redaction is true and ad_storage is denied, ad click identifiers sent in network requests by Google Ads and Floodlight tags are redacted.
• URL Passthrough
  You can optionally elect to pass information through URL parameters across pages in order to improve measurement quality.
• Wait For Update
  If your consent tool loads asynchronously, it might not always run before your Google tags. To account for this, specify wait_for_update along with a millisecond value to control how long to wait before sending data.

Data mappings

Mapping is the process of sending data from a data layer variable to the corresponding destination variable of the vendor tag. For instructions on how to map a variable to a tag destination, see data mappings.

The available categories are:

Standard

Vendor documentation

• About Google Consent Mode
• Google Developers: Adjust tag behavior based on consent