We assume you've added the Google Consent Mode script before the Google Tag Manager script as instructed in our tech doc or you’re using the Usercentrics CMP GTM template.
We also assume you’ve activated Google Consent Mode in the Admin Interface of your CMP Configuration or completed Step 2 of the tech doc and deactivated Google Consent Mode in the Admin Interface.
Checking the preview in Google Tag Manager
You can inspect the preview to confirm that Google Consent Mode v2 is enabled.
Start the preview and take the following steps:
Select "Consent"
Select the "Consent" tab
Ensure that the "On-page Defaults" are set and that they include the two new parameters;
ad_personalizationandad_user_data.
...
For a more thorough check that also includes checking the GCM storage type consent state updates, please refer to Google’s own detailed documentation on verifying your GCM implementation.
Checking the Google Consent Mode settings
When a page loads prior consent, the Consent Mode settings should be correctly registered in Google Tag Manager.
If you've implemented Usercentrics using the Usercentrics CMP template for GTM, you don’t need to add the default values for the Consent Mode storage types as they’re present in the UC template. Exception: If you’re using Google tags outside the GTM as well.
If you aren’t using our GTM template and/or using some Google tags directly in your code, please make the required adjustment in your site’s source code as documented.
...
Checking the dataLayer
Checking the contents of the dataLayer can be done by simply executing the command dataLayer in the Console of your browser’s DevTools. After consent has been given for all GCM storage types based on the consent_status of the relevant Google DPS in your CMP Configuration, you should see a consent update similar to the one below:
...