All Collections
Consent Management Solution
Google Consent Mode and Termly CMP
Google Consent Mode and Termly CMP
Updated this week

Termly supports both basic and advanced Consent Mode V2

Google’s Consent Mode is used to communicate your users’ consent status to Google. Google services such as Tag Manager, Analytics, Floodlight and Ads adjust their behavior in response to flags set by Consent Mode, respecting users’ choices accordingly.

Consent Management Platforms like Termly can be configured to communicate your users' preferences to the Google tags on your page via Consent Mode. When consent is denied, among other adjustments, tags will not set or read cookies in your browser, will not collect identifying information and will use modelling to fill in the gaps in your data.

How to set up Consent Mode with Termly

There are two possible ways to enable consent mode with Termly's consent management platform (CMP):

  • Option 1: Enable Consent Mode under your regional Consent Settings in the Termly dashboard

  • Option 2: Enable Consent Mode using Termly's Google Tag Manager template

If you employ both methods, be sure to set the same default configurations across both platforms in order to avoid configuration conflicts.

Option 1: Enable Consent Mode in the Termly dashboard

Google Consent Mode can be enabled on a region-by-region basis from the Termly dashboard. To do this, navigate to your consent banner settings and enable 'Google Consent Mode' for any region under your 'Consent Settings'.

  • Advanced Consent Mode: When Consent Mode is enabled in your consent settings, gtags will be exempted from blocking by Auto Blocker. This means that gtags will always be allowed to run on page load.

  • Basic Consent Mode: If you prefer that gtags are are not exempted by Auto Blocker when Consent Mode is enabled, and therefore always blocked before consent is given, you can use manual blocking to assign them to the appropriate blocking category.

Configuring consent defaults

To make use of Consent Mode 'Advanced options' in the dashboard, you must be using the latest version of Termly's embed script.

When 'Google Consent Mode' is 'On', consent defaults and other advanced options can be configured next to the Consent Mode toggle by selecting 'Advanced options'.

Option 2: Enable Consent Mode with Termly's Google Tag Manager Template

Termly's official Consent Management Platform template, found in the Google Tag Manager community template gallery, is designed to translate user consent settings from Termly's CMP into Google Consent Mode preferences anywhere Termly is installed.

Step 1. Add the Consent Mode template to your workspace

To install Termly’s Consent Mode template:

  1. Click on Templates in the left hand menu of your GTM workspace

  2. Click Search Gallery

  3. Search for “Termly”

  4. Select “Termly Consent Management Platform”

  5. Click Add to Workspace

Step 2. Create a new event trigger "userPrefUpdate"

Termly fires this event every time user preferences change in the Termly CMP. The template listens for this event and updates the consent state according to user preferences.

  1. Go to your GTM workspace and create a new trigger

  2. Click Choose a trigger type to begin setup, then click Custom Event.

  3. Under Event name type userPrefUpdate

  4. Trigger should be set to fire on All Custom Events

Step 3. Add Termly's template tag

  1. Go to Tags

  2. Create a new tag and select Termly Consent Management Platform in Tag Configuration

  3. Click Triggering, then click New / +

  4. Add Consent Initialization - All Pages

  5. Add userPrefUpdate

Now you can make use of GTM's consent configuration options to manage how and when tags are triggered based on user's consent preferences.

  • Advanced Consent Mode: To implement advanced consent mode through GTM, ensure that your gtags (GA4, Ads, etc.) do not have any Additional Consent Checks. In this way, they will always be fired when a user lands on the page, and will use the consent state to respond to the user's consent preferences.

  • Basic Consent Mode: If you prefer that gtags are are not fired before consent is given, you can configure Additional Consent Checks to allow them to fire when the appropriate blocking category is consented to.

Did this answer your question?