Checking your Google Consent Mode v2 implementation

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.

Some ways to check & test your GCM implementation:

1 Checking the preview in Google Tag Manager
2 Checking the Google Consent Mode settings
3 Checking the dataLayer
4 Script to check Google Consent Mode storage type consent states

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_personalization and ad_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 with Tag Assistant.

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.

When using a direct implementation (in your source code) of Google Consent Mode, you should see the default consent states of the GCM storage types in the dataLayer.

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.

With the consent default set in your code and a consent update from the Usercentrics CMP, the dataLayer will look similar to the following:

Script to check Google Consent Mode storage type consent states

If you’re using our GTM template to implement the Usercentrics CMP via a GTM tag, the default consent states of the GCM storage types won't be pushed to the dataLayer. They will be registered internally in the Google Tag Manager, so inspecting the dataLayer won't work to see them like in the example above.

However, you can execute the following script in the Console of your browser’s DevTools to get the Google Consent Mode settings:

(() => {
  l = s => s == undefined ? "" : s ? "granted" : "denied";
  c = s => s == "granted" ? "color: #0C0": "color: #C00";
  if (!window["google_tag_data"]) {
    console.warn("No Consent Mode data found");
    return;
  }
  var g = "ics" in google_tag_data ? google_tag_data.ics.entries : null, 
      i = "",
      t = "%c" + "Consent Mode settings:", 
      u = "";
  console.log(t, "font-size: 1rem");
  for (var a in g) {
    i = l(g[a]['default']);
    u = l(g[a]['update']);
    if (i == "" && u == "") continue;
    t = ("\t" + a + ":" +
      (i != "" ? "\n\t\tDefault: %c" + i : "%c")
      + "%c" +
      (u != "" ? "\n\t\tUpdate: %c" + u : "%c"));
    console.log(t, i != "" ? c(i) : "",
    "", u != "" ? c(u) : "", "");
  }
  if (i == "") console.log("No default Consent settings found");
})()

Your result should look similar to this, f.ex. after an Accept All on the CMP with relevant Google services for all the supported storage types added to the CMP Configuration: