Implementing Google Consent Mode Using CookieYes

Last updated on December 14, 2024

CookieYes now supports Google’s Consent Mode, an API that integrates Google tag behaviour with the user’s consent tool. Consent Mode has consent types for ads, analytics, functional, personalization and security cookies when using the global site tag or Google Tag Manager. You can use them to control tag behaviour based on user consent.

The CookieYes integration enables you to leverage Consent Mode v2 to better manage consent across Google tags. This update allows CookieYes customers using Google ads to integrate seamlessly with the CookieYes CMP. Here is a guide to how to integrate CookieYes with the Consent Mode v2.

Before you proceed, sign up on CookieYes for free.

1. Google Consent Mode v1:
   • Migration to Consent Mode v2: Guide for Existing Users to Upgrade from Consent Mode v1 to v2.
2. Integration in WordPress Plugin:
   • Method 1: Using CookieYes Plugin Interface
   • Method 2: Using the custom consent modes script for integration without the GTM template.
3. Integration in Shopify:
   • Method 1: Using Google Tag Manager template for Shopify sites.
   • Method 2: Using the custom script for integration without the GTM template.
4. New user implementations:
   • Enable Consent Mode v2 in CookieYes: How to activate the feature on the CookieYes platform.
   • Consent Mode Integration: Integrating Google Consent Mode v2 with CookieYes
5. Setting Up Google Tag Manager with CookieYes for Beginners:
   • Guide for Beginners: Integrating CookieYes with Google Tag Manager

Google Consent Mode v2 is an enhanced version of Google Consent Mode, aiding website publishers and advertisers in obtaining explicit user consent for web tracking, aligning with privacy regulations like GDPR. This updated version introduces standardised banners and user controls, streamlining the consent-gathering process for setting cookies and utilising tracking technologies. By implementing Consent Mode v2, advertisers can receive consent from users that can be integrated with Google advertising services, enabling granular reporting on campaign performance and conversion tracking. Consent Mode v2 provides the capabilities to acquire user consent specifically for advertising and analytics cookies in a legally compliant way under privacy laws.

Google introduced Consent Mode v2 as an update to its existing Consent Mode platform to continue alignment with privacy regulations and provide users enhanced transparency and control. Two notable new parameters have been added:

ad_user_data

This parameter includes the user’s consent preference for sharing their data with Google’s ad services. The possible values are “granted” or “denied” based on user choice collected through the site’s cookie consent banner. If consent is denied, Google advertising tags will avoid collecting or sending identifiable user data.

ad_personalization

This parameter indicates if a user has opted-in to ad personalisation and remarketing. Like ad_user_data, it reflects user preferences captured through the consent UI. A value of “denied” will turn off personalised ad functionality such as remarketing or interest-based targeting.

The first and most important step in implementation is to enable the Google Consent Mode v2 feature on the CookieYes platform. By default, the Basic Consent Mode feature should be enabled, but if you have disabled it at any point, follow these steps to turn it back on:

1. Log in to your CookieYes web app account.
2. Navigate to CookieYes Dashboard > Advanced Settings.
3. In Advanced Settings, toggle the button (to the right) labelled “Support GCM“ to enable the Basic Consent Mode.
   
   
   
4. To set up Advanced Consent Mode in GCM, toggle the button (to the right) labelled “Allow Google tags to fire before consent”.
   
   
   

Enabling only the Support GCM option implements basic functionality, firing only allowed tags based on user consent. The Allow Google tags to fire before consent option, when activated, ensures Google tags fire even before the user consents to the banner. This uses cookieless pings and collects only essential data for behavioural and conversion modelling to fill the gaps in your data. 

If you use Consent Mode with CookieYes, every time the website users give their consent choice, CookieYes will signal Google to modify the tag behaviour based on the user’s choice. Therefore, the website will stop collecting or using any personally identifiable information and use aggregated information for its services. 

There are two methods to integrate Consent Mode v2 with CookieYes — with and without using the Google Tag Manager Template.

If you don’t have an account with CookieYes, sign up and try for free.

First, you need to set up Google Tag Manager for your website. You can refer to the help guide for detailed instructions. This implementation uses CookieYes CMP via the CookieYes CMP Template Gallery Tag inside GTM.

Now, follow these steps:

Step 1. First, you need to create a new tag. Click Tags in the left sidebar, and then New as shown.

Step 2. Click on Tag Configuration > Discover more tag types in the Community Template Gallery and search for CookieYes CMP. Alternatively, you can get the template from here and skip to step 3.

Step 3. Choose the CookieYes template and click Add to workspace >  Add to add the tag.

Step 4. Insert the CookieYes website key, set other fields to appropriate values, and save the tag after naming it.

To add Default Consent Setting:

1. Click Add Setting.
2. Select Enabled/Disabled from the drop down for each cookie category based on your requirements.
3. Set the Region by entering the region’s ISO-standardised (ISO 3166-2) codes for the specific regions you intend to Geo-target with your banner. If you prefer not to Geo-target your banner to specific regions around the globe, enter All in the Regions field. Refer to the ISO 3166-2 standard for the appropriate region codes.
4. Click Add.

Step 5. Select Consent Initialization – All Pages as the trigger for the tag.

Step 6. Click Save to complete the integration of CookieYes with the Google Consent Mode.

To integrate CookieYes with Consent Mode without the use of CookieYes GTM template:

Step 1. Copy the custom script and paste above the Google Tag Manager script and CookieYes script :

<script>
    window.dataLayer = window.dataLayer || [];
    function gtag() {
        dataLayer.push(arguments);
    }
    gtag("consent", "default", {
        ad_storage: "denied",
        ad_user_data: "denied", 
        ad_personalization: "denied",
        analytics_storage: "denied",
        functionality_storage: "denied",
        personalization_storage: "denied",
        security_storage: "granted",
        wait_for_update: 2000,
    });
    gtag("set", "ads_data_redaction", true);
    gtag("set", "url_passthrough", true);
</script>

 gtag("set", "ads_data_redaction",false);
 gtag("set", "url_passthrough",false);

Step 2. If your website already has Google Tag Manager installed, ensure that you position the GTM script directly below the Custom Consent Mode Script and above the CookieYes script.

If GTM is not installed on your website, follow the below steps:

1. Sign Up/ Create a Google Tag Manager Account and set up a container.
2. Navigate to the Google Tag Manager Dashboard and click on the Container ID in the top navigation Panel.
3. Copy and paste the GTM script between the custom script and the CookieYes script. Additionally, ensure to insert the <noscript> element immediately after opening the <body> tag.
   
   

Step 3. The order in which scripts are loaded is crucial for their proper functionality. Follow the appropriate order based on your consent mode:

For Advanced Consent Mode:

1. Custom Consent Mode script
2. gtag / GTM script
3. CookieYes script

For Basic Consent Mode:

1. Custom Consent Mode script
2. CookieYes script
3. gtag / GTM script

Loading the scripts in this specific order is necessary for their proper functionality.

To verify GCM integration on your website,

1. Navigate to Advanced Settings in the CookieYes Dashboard.
2. Click the Check Now button against Check GCM status. If the configuration is correct, you will see a success message stating, ‘No error detected’. If you encounter any error after running this check, refer to our GCM Troubleshooting Guide to resolve them and check again.

To further confirm the setup is correct, follow the steps in our Verification Documentation.

CookieYes CMP maps all seven Google consent types into 4 categories: