Introduction
Google Tag Manager allows you to configure Additional Consent Checks. This essentially allows you to configure the tag to require permission for a specific storage type to fire a tag.
This require the use of Google Consent mode though, which will be enabled automatically if you have deployed Cookiebot using the Cookiebot CMP tag from Google Tag Manager's template gallery. If you implement Cookiebot in any other way, you will need to add a supplementary script as described in Cookiebot and Google Consent Mode.
There are alternative methods to conditionally load tags though. This guide will describe alternative options and provides instructions in their use.
Cookiebot will send consent data regardless of whether Consent Mode is enabled or not. This ensures that you still can conditionally load tags that require consent, in the form of the following three Custom Events:
- Event name:
cookie_consent_preferences
- Event name:
cookie_consent_statistics
- Event name:
cookie_consent_marketing
The process of setting up a consent trigger requiring consent for statistical/analytics cookies is identical to setting up the cookie_consent_update
trigger as described in step 2.1 of the Google Tag Manager deployment guide. The result should look similar to this:
Using the Cookiebot Consent State variable
Click "Add to workspace" and confirm by clicking "Add".

You will now be able to use this variable in a condition to fire a tag.
Generally speaking you will need to switch "This trigger fires on" from "All..." to "Some..." and add the following condition:
Cookie Consent ➟ contains ➟ [category]
A trigger using the variable could look similar to this:

Comments
0 comments
Article is closed for comments.