Google Consent Mode 2.0 (GDPR Standard - web)

Google Consent Mode 2.0 ensures that Google vendors on your property comply with an end-user's consent choices for purposes (called consent checks) defined by Google. When a website visitor or app user indicates their consent choices, tags with consent checks adjust their behavior, and user consent choices are preserved across their interaction with the website.

In this article, we will cover how to configure the integration between Sourcepoint and Google Consent Mode 2.0 for a web property who is running a GDPR Standard campaign.  

• Consent check overview
• gtag.js vs Google Tag Manager
• Implement Google Consent Mode 2.0 on web
• Debug default consent mode timing  
• Test integration

Consent check overview

Consent check(s) indicates the kind of storage a Google vendor uses.  An end-user can deny or grant the collection of this data. The consent check varies across each Google vendor and can be viewed by selecting a vendor from the GTM platform and expanding the Advanced Settings > Consent Settings tab.

Please refer to the table below for the different consent checks available in Google Consent Mode 2.0:

gtag.js vs Google Tag Manager

Before configuring the implementation, your organization will need to decide whether to implement using gtag.js or Google Tag Manager.

Implement Google Consent Mode 2.0 on web

Sourcepoint supports two different ways to implement Google Consent Mode 2.0 on your property running a GDPR TCF campaign. Click the tabs below to review which implementation method is suitable for your organization:

<script>
window.dataLayer = window.dataLayer || [];
function gtag(){dataLayer.push(arguments);}

//default behavior
  gtag('consent', 'default', {
    'ad_storage': 'granted',
    'ad_user_data': 'granted',
    'ad_personalization': 'granted',
    'analytics_storage': 'granted',
    'wait_for_update': 500
  });
  
//behavior specific for end-users in the EEA + UK  
  gtag('consent', 'default', {
    'ad_storage': 'denied',
    'ad_user_data': 'denied',
    'ad_personalization': 'denied',
    'analytics_storage': 'denied',
    'region': ['GB', 'BE', 'BG', 'CZ', 'DK', 'CY', 'LV', 'LT', 'LU', 'ES', 'FR', 'HR', 'IT', 'PL', 'PT', 'RO', 'SI', 'HU', 'MT', 'NL', 'AT', 'IS', 'LI', 'NO', 'SK', 'FI', 'SE', 'DE', 'EE', 'IE', 'EL'],
    'wait_for_update': 500
  });
</script> 

Debug default consent mode timing

Your organization can add the following code snippet to Sourcepoint's onConsentReady event callback to check whether the default consent code is set before any other Google product is configured.

If any other Google product is configured before Google Consent Mode code is set then you will receive the following alert in your browser console: GCM not being configured soon enough.

onConsentReady: function (consentUUID, euconsent) {
    console.log('[event] onConsentReady', arguments); 
    //Loop through all the dataLayer objects
      for(var obj in dataLayer){
        //initialize vars
        gcm_conset_pos = -1;
        gcm_config_pos = -1;
                        
        //mark when GCM is first set
        if(dataLayer[obj][0]==='consent'){                   
          console.log('GCM configured at position ' + obj + ' in the data layer');
          if(dataLayer[obj][1]==='default'||dataLayer[obj][1]==='update'){
            var gcm_conset_pos = obj;    
          }
        }
                        
        //mark when the first Google product is configured
        if(dataLayer[obj][0]==='config'){
          console.log(dataLayer[obj][1] + ' configured')
          var gcm_config_pos = obj;
          console.log("breaking: ", (gcm_conset_pos - gcm_config_pos));
          break;
        }
      }
                    
      //check if GCM is happening before any config is happening
      if((gcm_conset_pos - gcm_config_pos)0){
        console.log("GCM not being configured soon enough")
      }
      else{
        console.log("GCM timing is okay")
      }
}

Test integration

Regardless of how your organization has implemented Google Consent Mode 2.0 (either via Google Tag Manager or gtag.js), you can test the setting of Google's consent checks via Google Tag Assistant. 

Click Add Domain.

Use the provided modal to input your property's URL that is currently integrated with Sourcepoint's CMP and Google Consent Mode 2.0.

From an event, navigate to the output for your container/tag and select the Consent tab. From the subsequent table, you can discern the status of the Google consent checks and compare them to consented/rejected purposes in your privacy manager.