How to configure your Cookie Banner with Google Tag Manager?

Background

In order to follow this documentation, we assume you have:

A Google Tag Manager account.
Created a Google Tag Manager container on your website.
Added the Google Tag Manager script to your website.
Added your Privasee Cookie Banner script to your website. Learn how to do this here.

Google Consent Mode Disclaimer

<aside> ⚠️ Note that if you’re looking to add Google Analytics, Google Ads, Floodlight or Conversion Linker you need Google Consent mode. You can learn more about Google Consent Mode here and how to implement it here.

</aside>

Google Tag Manager Background Information

Google Tag Manager helps you configure when the Javascript tags on your website are activated.
Each tag needs to have at least one trigger.
Triggers listen for certain website events (e.g. the website is fully loaded). Once this event takes place the trigger determines if the tag is activated.
Triggers can be firing or exception triggers:
- Exception triggers determine when a tag is NOT fired and take precedence over other triggers.
Firing triggers determine when a tag is fired (we will use these).
Triggers can be use variables. A tag will be fired or blocked depending if a condition of a variable is met or not.
Privasee uses a special type of variable, a data layer variable, to communicate between your Google Tag Manager settings and your Cookie Banner.

1. Configuring Tools and Third Parties

We will use Google Analytics as an example. However, you must follow this process for each Tool and Third Party that is placing cookies on your website and configured using Google Tag Manager.

<aside> ⚠️ For tools which are placed directly as code snippets on your website and not added via Google Tag Manager, follow this guide instead.

</aside>