...
The Usercentrics CMP template tag registers default consent settings, so the consent mode script doesn’t need to be used with that implementation method for the Usercentrics CMP, as long as all relevant Google tags are handled in the Google Tag Manager. (No default consent needed on the page.)
If you don’t implement Usercentrics CMP via the template tag in Google Tag Manager, you’ll need to add a script to your page to enable it.
Let’s have a look at that script for option 2:
| Code Block |
|---|
<script type="text/javascript">
// create dataLayer
window.dataLayer = window.dataLayer || [];
//Create the gtag API, so you don’t have to write dataLayer.push() and can use gtag() instead.
function gtag() {
dataLayer.push(arguments);
}
//Use the gtag method to pass default consent settings to Google Tag Manager.
gtag("consent", "default", {
ad_user_data: "denied",
ad_personalization: "denied",
ad_storage: "denied",
analytics_storage: "denied",
wait_for_update: 2000 // milliseconds to wait for update
});
// Enable ads data redaction by default [optional]
gtag("set", "ads_data_redaction", true);
</script>
//The last part is the Google Tag Manager script. If you want to use Consent Mode as alternative to prior blocking the type of the script tag is "text/javascript".
<script type="text/javascript">
(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
j=d.createElement(s),dl=l!='dataLayer'?'&l='+l:'';j.async=true;j.src=
'https://www.googletagmanager.com/gtm.js?id='+i+dl;f.parentNode.insertBefore(j,f);
})(window, document, 'script', 'dataLayer', 'GTM-XXXXX'); //replace GTM-XXXXXX with Google Tag Manager ID
</script> |
...
Follow the optional Step 2 of the Google Consent Mode technical documentation.
Alternative (requires deeper technical GTM expertise): For Google Consent Mode setups purely handled within the Google Tag Manager (GTM), it’s also possible to build your own or use third party Google Consent Mode GTM templates. The idea with that approach is to use the consent_status event’s information in the dataLayer to “translate” this into Google Consent Mode storage type consent states in the GTM.
Usercentrics does not recommend or actively support this alternative, but it may be feasible for some customers to explore such an option.
Deactivate Google Consent Mode in the Admin Interface of the CMP Configuration. This helps prevent mixed signaling for the consent states.
Step-by-Step Google Consent Mode implementation with the Usercentrics CMP
You’ll find more details above and on the other pages of this Google Consent Mode section, but here are the steps to take for implementing GCM with the Usercentrics CMP put into simple terms.
Set the default consent states for Google Consent Mode storage types in one of two ways:
Using our GTM template tag can do this for you in the Google Tag Manager. Ensure you enable Google Consent Mode in the tag.
Follow Step 1 of our Google Consent Mode tech doc in the context of a direct implementation in your website’s code.
Regardless of your choice (a or b) above, it’s then necessary to: Toggle on / off Google Consent Mode in the Admin Interface of your CMP Configuration / SettingID under Configuration → CMP Settings tab → Google Consent Mode, depending on:
Most common use case: If you’re using only Predefined DPS for the relevant Google services, toggle Google Consent Mode on in the Admin Interface to take advantage of our out-of-the-box signaling for GCM storage types.
Optional: If you’re using some Custom DPS for the relevant Google services, follow Step 2 of our GCM tech doc and toggle Google Consent Mode off in the Admin Interface. This helps prevent multiple consent state updates for the GCM storage types.
Adjust triggers of relevant Google tags based on your decision to use Basic or Advanced Google Consent Mode v2.