Google Consent Mode: What It Is and How to Set It Up

When running ads, privacy regulations mean you have to respect user choices regarding data collection. In practice, what I see is that many advertisers struggle to balance privacy compliance with accurate tracking. This is where google consent mode comes in. It is a feature that allows you to communicate your users’ cookie or data privacy consent choices to Google tags, adjusting how your tags behave based on whether consent is granted or denied.

Consent mode doesn’t provide a consent banner or widget. Rather, consent mode interacts with your existing banner to obtain visitor consent. When you enable consent mode, Google measurement products ensure that a visitor’s consent mode state is preserved across the pages they visit. You can implement consent mode on your website or app in either of 2 ways: basic or advanced.

Before you start

To set this up, you need a few prerequisites in place before touching any code or tags.

• You need an active website or app that sends data to Google tags.
• You need a consent banner already integrated on your site to collect visitor preferences.
• You need access to your website’s code or tag management system to configure tag behaviors.

Step by step

Implementing consent mode depends on choosing between the basic and advanced setups. Here is how each option works in practice.

1. Decide on your implementation method: choose the basic version if you want to completely block Google tags from loading until a user interacts with your consent banner. Choose the advanced version if you want Google tags to load immediately when a user opens the website or app.
2. Configure the default states in the advanced setup: set your defaults to denied unless configured otherwise. The tags load the consent mode API, set defaults, and wait for user interaction to update consent states.
3. Transmit signals: in the basic setup, no data is transferred to Google prior to user interaction. When the user grants consent, Google tags load and execute the consent mode APIs to send consent states.
4. Handle pings and updates: ensure your setup sends consent state pings for Google Ads and Floodlight tags to communicate default and updated states for consent types such as ad_storage and analytics_storage.
5. Meet data thresholds: allow your tags to collect data for at least 7 full days so Google Ads and Google Analytics can gather enough information to report any modeled uplift.

How to test that it works

After setting up your implementation, you need to verify that consent signals are firing properly. Check your browser’s developer tools or network tab to inspect the pings sent on page load. In a basic setup, confirm that no Google tags fire or send data before you click accept or decline on your consent banner. In an advanced setup, confirm that initial pings send default denied states, and that full measurement data only transmits after a user grants consent.

Common problems

Even with careful setup, you might run into issues. Here is how to address the most frequent ones.

Tags firing too early

In a basic setup, if Google tags fire before user interaction, your implementation is incorrect. Ensure your tag blocking rules or consent banner triggers are positioned to block all tags until an explicit choice is made.

Missing uplift data

If you do not see modeled data after a week, your site may not meet the minimum data collection threshold required by Google. You will need to wait until you accumulate enough traffic and consent events.

Incorrect tag configuration

If you create tags that do not have built-in consent checks, they might ignore user choices. Use the Advanced and Consent Settings in your tag configuration to add manual checks.