Integrate Google Consent Mode with LaunchPad
Universal Privacy Manager supports Google Consent Mode which allows you to adjust how your Google tags behave based on the consent status of your users. Privacy Manager will 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. If a user consents, conversion measurement reporting continues normally. If a user does not consent, the relevant Google tags will adjust accordingly and not use ads cookies, instead measuring conversions at a more aggregate level.
Google Consent Mode supports the following Google products:
Google Analytics
Google Ads (Google Ads Conversion Tracking and Remarketing)
Google Tag Manager
Gtag
Floodlight
Conversion Linker
Note
This list was current at the time of publication and is subject to change.
Google Consent Mode requires gtag.js or Google Tag Manager to run. If you use an older tag like ga.js, analytics.js, or conversion.js, you’ll have to update to gtag.js or Google Tag Manager first.
For more details on Google Consent Mode, see Google’s help documentation.
Using Google Consent Mode
Getting There
From Console, navigate to the LaunchPad configuration that you wish to use with Google Consent Mode and select the "Integrations" tab. Click and then select “Google Consent Mode”.
Consent Mode Behavior
It is possible to link the Consent Mode behaviors to the consent state of specific vendors. Privacy Manager will set the appropriate Google Consent Mode state depending on the consent state of the linked vendor. Make sure that before configuring Google Consent Mode, you have added the appropriate vendors to your vendors configuration.
Vendors that are typically used are:
Behaviour | Vendor ID | Vendor Name |
|---|---|---|
Ad Storage | 755 | Google Advertising Products |
Analytics | 10211 | Google Analytics |
When the vendors have been added in the Privacy Manager "Parties" configuration, you will be able to use them for Google Consent Mode.
Setting Additional Data Controls
Pass ad click information through URLs
To help improve data associated with ad clicks when ad_storage is denied, you can optionally tell your tags to pass the ad click information from the landing page through to subsequent pages in the user's navigation on your site.
Redact ads data
Can be used to stop ad click identifiers from being passed in the Google tag requests.
Setting ads_data_redaction will have no effect when consent for ad_storage is set to 'granted'.
Please note that without this additional setting, some cookies may be read and written, limited to Spam & Fraud use cases.
More information on additional data controls can be found in this Google help article.
Implementing Consent Mode
Consent Mode for web pages must be implemented in a way that ensures the user consent state is defined before the tags load. This way, Google tags will adjust their behavior according to the user's consent choice. Ensure that your implementation loads Google tags in all cases, not only if the user consents or Google will not receive the necessary pings for accurate measurement.
By default, Google Consent Mode settings are embedded in the Privacy Manager wrapper. In case the Privacy Manager wrapper is not loaded before any Google tags, for instance when it is loaded from a tag manager, then the gtag.js API should be defined separately. Select "Do not define the gtag API in the Privacy Manager wrapper" to get the code snippet and disable the loading of gtag API from the Privacy Manager wrapper.
Configuring Loading Method
Privacy Manager is loaded asynchronously and it is not guaranteed to load before your Google tags. The gtag('consent', 'default') command loads a static set of default consent type settings on each page load to fall back on.
Region Specific Behaviours
The default state for the Consent Mode behaviors for all regions is configurable to be either "denied" or “Granted”. The default state can be overridden for one or multiple countries using the Country setting. When Privacy Manager initializes, it will update the state. This setting allows you to configure how long the tags should wait for the consent state. The default value is 500 milliseconds.
Check out Google’s Consent Mode Developer Documentation for more information on how to configure Consent Mode.