Google Consent Mode allows Google tags to adjust their behavior based on a visitor’s consent choices from your cookie banner. Consent Mode does not replace a cookie banner. Instead, it works with your consent banner to communicate consent choices to Google services such as Google Analytics, Google Ads, Floodlight, and Google Tag Manager.
​

This guide helps you choose the correct Enzuzo setup for your website.

Enzuzo supports two main Google Consent Mode installation methods:

You should choose one installation method and follow that method completely.
​

Important: Do not mix the GTM and gtag installation methods unless your developer or implementation partner has intentionally designed a custom setup. Mixing methods can cause the Enzuzo banner, Consent Mode defaults, and Google tags to load in the wrong order.

Before configuring Consent Mode, make sure you have:

If you are not sure whether your website uses Google Tag Manager, check your website source code or ask your developer.
​

A Google Tag Manager script usually contains:

A script that contains the following is not Google Tag Manager by itself:

That script loads the Google tag directly and may or may not be managed through Google Tag Manager. Confusing gtm.js and gtag/js is a common implementation issue.

Use the table below to choose the correct setup.

Use the Google Tag Manager setup if:

In this setup, you must complete both parts of the GTM implementation:

The Enzuzo GTM configuration guide currently instructs customers to install the Enzuzo Community Template and set the Enzuzo Cookie Manager tag to Consent Initialized. Google also explains that the Consent Initialization trigger is designed for tags that set or update consent state and fires before other triggers.

Use the GTM method when Google Tag Manager is already installed on your website and you want GTM to control when the Enzuzo banner and other tags load.

Use the gtag / direct script setup if:

In this setup, the Consent Mode default command must be available before Google tags send measurement data. Google’s developer documentation says the gtag('consent', 'default', ...) command should be called before commands that send measurement data, such as config or event.

The Enzuzo gtag integration guide provides a direct script-based setup for customers who do not use the Enzuzo Google Tag Manager template.

Use the gtag method when your Google tag is installed directly on your website and you are not loading the Enzuzo banner through GTM.

Google Tag Gateway, or GTG, can affect how Google tags are loaded on your website.

If Google tags load before Enzuzo has made Consent Mode defaults available, you may see a warning that consent was set too late or that a tag read consent state before a default was set. Google’s troubleshooting documentation explains that default consent state should be set before any tags or other code uses or updates consent, and that CMP banners should load before Google tags send data.

GTG requires special attention because some automated or CDN-based setups can change how scripts are inserted or loaded. Google’s GTG documentation notes that when Consent Mode is used, automated script setup must be turned off, and that automated setups may insert scripts into the page HTML.

Google supports two Consent Mode implementations: basic Consent Mode and advanced Consent Mode.

With basic Consent Mode, Google tags are blocked from loading until the visitor interacts with the consent banner. Google says this setup sends no data to Google before the visitor interacts with the banner.

With advanced Consent Mode, Google tags load when the visitor opens the website, default consent states are applied, and tags adjust behavior based on the visitor’s consent choice. Google says that when consent is denied, Google tags may send cookieless pings, and only send full measurement data when the visitor grants consent.

Your Consent Mode setup should reflect your legal requirements, your Google product configuration, and your measurement needs.

For Google tags managed through GTM, Enzuzo generally recommends using Google tags with their built-in consent checks rather than treating Google tags like ordinary third-party scripts. Third-party scripts that do not have built-in consent checks should be configured to fire only after the appropriate Enzuzo consent update event.

After publishing your setup, verify that Consent Mode works correctly.

Check that:

You can use Google Tag Assistant and GTM Preview mode to help verify your implementation.

Google’s consent troubleshooting documentation identifies “default consent not set” and “default consent set too late” as common implementation issues.

If you use GTM, confirm that:

This usually means a Google tag loaded before Consent Mode defaults were available.

If you use GTM, confirm that the Enzuzo tag fires on Consent Initialization and that Google tags are not firing before the CMP has initialized.

If you use gtag, confirm that the Consent Mode default command is placed before Google measurement commands such as config or event.

If you use GTG, first verify whether the affected Google tag is enrolled in Google Tag Gateway, then follow the remediation steps in the GTG article.

This usually indicates an incorrect tag load order.

For GTM installations:

For direct gtag installations:

For support with Enzuzo’s Google Consent Mode integration, contact:

cmp-support@enzuzo.com
​

We can help troubleshoot Consent Mode, Google Tag Manager, gtag, IAB TCF, and Google Tag Gateway implementation issues.