Configure Google Consent Mode with Didomi

• functionality_storage: allows the storage of functional cookies used by a website or application (e.g. language settings)
• personalization_storage: allows storage related to content personalization (e.g. video recommendations)
• security_storage: this type of consent is always granted and allows security-related storage, such as authentication functionality, fraud prevention and other user protections

Setting the status of data storage permissions 

The Didomi CMP listens for consent status updates from Google vendors to update the status of GCM settings:

• If the Google Advertising Products vendor (SDK ID: google) receives consent globally (the vendor and all its purposes are enabled): ad_storage, ad_user_data and ad_personalization as well as functionality_storage and personalization_storage are set to granted

• If the Google Analytics Products vendor (SDK ID: googleana-4TXnJigR) receives consent globally (the vendor and all its purposes are activated): analytics_storage is granted

Difference between basic and advanced mode

Source: Consent Mode Deep Dive for Web & App: Power Durable Performance in 2024

✅ Once consent is granted, associated tags will function normally
🚫 When consent is denied with basic consent mode, all tags are blocked and no information is collected
🚫 & ✅ When consent is denied with advanced mode, tags do not drop cookies, but cookieless pings are sent for analytics_storage and ad_storage
🚫 & ✅ When consent is denied with advanced mode, the beacon will not send user data for advertising purposes
🚫 & ✅ When consent is denied with advanced mode, the tag will disable personalized advertising

To learn more, see the Google documentation.

2. Set Google Consent Mode (CoMo)

Overview:

Step 1 - Enable GCM (and set default status) 

👉 The default status is the status that is set when the page initially loads. You can have more details in the official Google documentation.

1) Using the Didomi console

1. Go to the Consent notices section and click on the Edit icon corresponding to your notice
2. Proceed to step 2. Customization, then to the Integrations section.
3. Click on the Advertising tab.
4. Enable the integration (check the box at the top right)
5. You can activate the integration and select either the Google Analytics products vendor, or Google Advertising Products, or both vendors

👉 If you had a custom vendor for Google Analytics, your old vendor will still be selected. And you will have to deselect it if it is no longer needed.
To avoid losing data, make sure you configure your GA tags correctly before deselecting the vendor.

• • For basic mode: you can leave the default settings with the box already checked at the top right and the appropriate vendor(s) also checked.
    Default statuses are not taken into account because your Google tags are blocked from loading pages. You can skip this step and go straight to step 2.

• • For advanced mode: check the item "Set the default status..." to be able to make a specific choice on each of the associated sub-options. Checked sub-options indicate that the status will be set to granted when the page initially loads.

• • • For example, if you enable "Enable ad_storage before user gives consent", on your website, the initial page load for ad_storage will be set to granted

2) Using the Didomi GTM template: 

Follow these instructions to configure GCM with the Didomi GTM template.

• For basic mode: default statuses are not taken into account, because your Google tags are blocked when loading pages. You can skip this step and go straight to step 2
• For advanced mode: set the default status to GCM granted for the desired permission(s)

 
3) Using a window.didomiConfig :

We recommend using option 1 or 2 in order to group the Didomi configuration in one place.
However, this setting can be useful for testing purposes.

<script type="text/javascript">

window.didomiConfig = {

  integrations: {

    vendors: {

      gcm: {

        enable: true,

        setDefaultStatus: true,

        defaultStatus: {

          analytics: false, //'analytics_storage' default status Basic mode

          ad: false, //'ad_storage' default status

          ad_user_data: false, //'ad_user_data' default status

          ad_personalization: false, //'ad_personalization' default status

        },

      }

     }

   }

};

</script>

Step 2 - Set up your tags 

Basic mode

Google tags (Ad Words, Analytics, Conversion Linker and Floodlight) must be blocked until the user gives positive consent. This means that the settings will be "denied" by default or will not be set.

To configure Basic mode with Didomi you have 2 options based on where your tags are set:

• In GTM: block your Google tags using our GTM integration described in this documentation.
  Note that to use basic mode, you must use the didomi-consent event.
• Using Didomi tags attributes as described here:
  Use the appropriate vendor to trigger your Google tags.
  Example for Google Analytics:
  <script type="didomi/javascript" data-vendor="c:googleana-4TXnJigR" src="https://www.googletagmanager.com/gtag/js?id=GA_MEASUREMENT_ID"></script> 

Advanced mode

Google tags (Ad Words, Analytics, Conversion Linker and Floodlight) should be loaded as soon as the SDK is ready.
The tags will then send data based on the default status.
In advanced mode, it is therefore important to define the default status that you want Didomi to expose.

To configure Advanced Mode with Didomi you have 2 options:

• With Google Tag Manager, use the didomi-ready event to ensure that Google tags are loaded once the Didomi SDK is ready and Consent mode is set (or a trigger group if necessary)
  You can refer to this documentation.
  

• Using Didomi <script> tags attributes documented here:
  With type="didomi/javascript" only
  Your tags will load as soon as the SDK is ready, without a specific link with a vendor

<script type="didomi/javascript" src="https://www.googletagmanager.com/gtag/js?id=GA_MEASUREMENT_ID"></script>

Optional configuration - Enable Consent mode's TCF integration

Consent mode commands can be set based on the user’s choices in the TCF string. To do so, enable the option "Enable IAB TCF integration with Google Consent Mode" in the Didomi Console:

3. If you upgraded from v1 to v2

Via the Didomi console

You don't need to take any specific action in this case.
The new consent mode permissions (ad_user_data and ad_personalization) are added with a default status = granted. You can change this setting if you want.

Via the GTM Didomi template

If you are already using Didomi's GTM template for consent mode v1, you will need to follow the following steps in order to use the latest version of the template:

1. Login to GTM
2. You'll see a warning, click on "View"
   
   
   
3. Select Didomi CMP
   
4. Click on "Accept Update":
   
   
   
5. New consent mode parameters will be automatically added and set to denied by default:
   
6. If you want to use advanced mode, you can modify the status of these new permissions.

Via a window.didomiConfig:

If you are using Didomi's script tag, make sure the default state of newly added parameters is set.

<script type="text/javascript">

window.didomiConfig = {

  integrations: {

    vendors: {

      gcm: {

        enable: true,
       
        dataLayerName: 'customDataLayer' // Custom data layer name, defaults to 'dataLayer'

        },

      }

     }

};

</script>

If you need further assistance or have noticed something unusual, please feel free to reach out to google-support@didomi.io.