This guide demonstrates how to implement Google CMv2 using our GTM tag template. CMv2 offers two modes: Basic and Advanced. Learn more about the differences between them here.
​
​Please be aware that our tag template implementation will implement the Advanced Mode of CMv2.
​
If you would like to only implement the basic mode, please see our CMv2 Implementation guide.

To implement Consent Mode v2 through Google Tag Manager, search for our tag template named Cookie Information + Consent Mode v2 in the Community Template Gallery and add it to your container.

In this step, you can either add a Cookie Information consent banner using the GTM template or directly to the website's source code.

Select the Add Cookie Information Consent Banner option to directly manage the consent banner code deployment through the template. Please note: If you choose this option, the cookie banner snippet should not be implemented in the source code of your website.

Selecting the Add Cookie Information Consent Banner option unlocks three different modes for managing language versions, including dynamic management of the consent banner's language versions.

It is crucial to select a language that has been configured within Cookie Information; otherwise, the banner will not be displayed.

If you implement our pop-up script (uc.js) in your source code, you will need to add a new attribute to it: data-gcm-enabled="false". After adding this new attribute to the script, it should look as follows:

By adding this attribute, uc.js will disable its logic for Google Consent Mode, as this will be managed by the CI GCM tag template within GTM.

Under Default settings, click Add Row. Ensure that all parameters are set to denied, then click Add in the top right-hand corner.

When the Redact Ads Data checkbox is ticked, and ad_storage is set to denied, ad click identifiers sent in network requests by Google Ads and Floodlight tags will be redacted. Additionally, network requests will be sent through a cookieless domain as an extra privacy measure. For more information about this setting, please refer to the Google Consent Mode v2 documentation.

When a user lands on your website after clicking an ad, information about the ad may be appended to your landing page URLs as a query parameter. To enhance conversion accuracy, this information is typically stored in first-party cookies on your domain. However, when the Pass through URL parameters checkbox is ticked, and either ad_storage or analytics_storage is set to denied, information that would normally be stored in cookies will not be stored locally on your domain. To preserve the quality of ad click measurement and ensure analytics accuracy when cookies cannot be utilized, you can choose to transmit information about ad clicks and analytics events through URL parameters across pages. Certain conditions must be met for URL passthrough to function effectively. For comprehensive instructions on configuring URL passthrough, please refer to the Google Consent Mode v2 documentation.

In scenarios where your banner loads asynchronously, there's a chance it might not execute before your Google tags. To address this, you can use the 'Wait for update' setting with a specified millisecond value to control the delay before data transmission occurs. For more information, please refer to the Google Consent Mode v2 documentation.

Click on Advanced Settings and set the tag firing priority to 999 to ensure it is the first one to fire.

Next, click on the Triggering panel and select Consent Initialization - All Pages as the trigger type.

To ensure the setup is correct, please refer to this article.

Please view the live demo recording of the Google Consent Mode v2 setup using the Cookie Information tag template below: