Page Comparison

How Google Tag Manager (GTM) handles consent

Advanced vs Basic Google Consent Mode (GCM) - Overview

The following overview graphic will help you get a quick overview of the differences between Advanced and Basic GCM.

...

In the sections below, you’ll find more details on setting them up with the Usercentrics CMP.

Basic

...

Google Consent Mode

• Google tags are initially blocked until consent is granted.

  • Using Ucersentrics the Usercentrics CMP, tags within the Google Tag Manager (GTM) will need to be triggered

  • Image Removed

Advanced consent mode

• Google tags are loaded before the consent dialog appears

• Tags send cookieless pings when cookie consent declined

  • Using Ucersentrics CMP, tags within GTM won’t need to be triggered

  • Image Removed

Is Consent Mode v2 enabled?

We assume you've added the Consent Mode script before the Google Tag Manager script as instructed in our Adjust the existing Google Tag Manager code .

Checking the preview in Google Tag Manager

You can also inspect the preview to confirm that Consent is enabled, and if you're on version 2.

Start the preview and take the following steps:

1. Select "Consent"

2. Select the "Consent" tab

3. Ensure that the "On-page Defaults" are set and that they include the two new parameters; ad_personalization and ad_user_data.

Image Removed

Checking the 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, you don’t need to add the default values for the Consent Mode as they’re present in the UC temple.

...

Checking the dataLayer

Checking the contents of the dataLayer can be done by simply executing the command dataLayer. After consent has been given for all types of cookies:

...

• • only when consent for the correlating Data Processing Service (DPS) is given.

  • How we recommend setting up variables & triggers for this purpose in the GTM is documented.

    Image Added

  • Alternatively to using our recommended variable & trigger setup that can fire specific tags based on the consent status of specific Data Processing Services (DPS) in the Usercentrics CMP Configuration / SettingID, there are also other options of handling the triggering of tags, f.ex.

    • Triggering tags based on the consent state(s) of Google Consent Mode storage types (i.e. ad_storage) is possible for individual tags. The following video outlines this method for setting up Basic Google Consent Mode in more detail:

...

• Third party templates may be used to “translate” the consent_status event of the Usercentrics CMP into signals for the Google Consent Mode storage types inside the GTM.

• While these alternative approaches are possible to set up in connection with the Usercentrics CMP, they are not part of the generally recommended setup. They often require the assistance of a GTM expert.

Advanced Google Consent Mode

• Google tags of relevant Google services are loaded before consent is collected.

• They will not be adjusted like we recommend for other non-essential tags. Instead they will trigger “normally”, i.e. like so in the GTM:

  Image Added

• The Google tags have built-in consent checks for one or more of the following Google Consent Mode storage types:
  ad_storage
ad_user_data
ad_personalization
analytics_storage
  
  Example:

  Image Added

  
  The tags will adjust their behavior accordingly.

• Important: Tags corresponding to non-essential, non-Google Data Processing Services (DPS) should continue to be adjusted as generally documented. The Advanced Google Consent Mode implementation described above is specifically for Google tags of relevant Google services.

Is Google Consent Mode v2 enabled?

If you’re interested, continue with → checking your Google Consent Mode v2 implementation.