Google Tag Manager and Automatic cookie blocking

Combine the use of Google Tag Manager with automated cookie blocking by Cookiebot to get the best of both worlds. Implementation is quick and easy and allows you to:

• Control tags and cookies based on the user's consent, using triggers and Consent Mode in Google Tag Manager AND
• Let Cookiebot automatically control all other cookies not set by Google Tag Manager, based on the consent given, typically cookies set by third party scripts that are embedded directly in your website.

To achieve this, make sure that the Cookiebot script is not executed by Google Tag Manager. So either remove the Cookiebot CMP tag, pause it, or remove the trigger assigned to it.

Furthermore, for optimal results:

1. Ensure that the Google Tag Manager script is first to load on your website.
2. Mark up your Google Tag Manager script tag with: data-cookieconsent="ignore"
   This will ensure that the Google Tag manager script can't unintentionally get blocked by the auto blocking feature.
3. Insert the Cookiebot script with automatic cookie blocking immediately after Google Tag Manager script.
4. If you choose to use Google Consent Mode, ensure this script loads before the Google Tag Manager script does.

Here's an example of how this could look:

If you have renamed the dataLayer, you need to add the data-layer-name attribute to the Cookiebot script tag, with the new dataLayer name as its value.
For example: data-layer-name="gtmDataLayer".

Google Consent Mode

For tags that support built-in consent checks, like Google Ads Conversion Tracking and Remarketing, Floodlight, Google Analytics and Conversion Linker, we recommend using Google Consent Mode, which can be activated by inserting the following snippet before the Google Tag Manager script in your header:

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

It is vital that this script loads before the Google Tag Manager script, otherwise the instructions to deny the use of cookies and to redact data will come too late!
Furthermore, if you have renamed the dataLayer, ensure that you replace window.dataLayer with the actual name of the dataLayer.
For example: window.gtmDataLayer = window.gtmDataLayer || [];

For all other cookie-setting tags in Google Tag Manager, implement Additional Consent Checks as described in our GTM deployment guide.

You can also make use of Consent triggers as described in Alternative methods for conditionally loading tags.

Disabling Consent Mode

It's important to note that regardless whether you implement the Consent Mode script, which sets the default permissions within Google Tag Manager, the Cookiebot script will always pass updated Consent Mode data when it has established a visitor's consent choices.

If you for any reason prefer not making use of Consent Mode, you have to option to prevent Cookiebot from sending Consent Mode signals to Google Tag Manager.

Please see Disabling Consent Mode for instructions.

You may also implement the use of Google Tag Manager with manual blocking and implementation of prior consent for any remaining  elements outside your tag manager. Use the script for manual cookie blocking and follow our guide here for setting up Google Tag Manager implementation