A Rough Guide to Google Consent Mode

TL:DR

Google Consent Mode allows your website to communicate a user’s consent choices to Google tags such as Google Analytics and Google Ads. When used with Google Tag Manager, those consent choices can also be used to control when other analytics and marketing tags are allowed to fire.

It isn’t your cookie banner or Consent Management Platform (CMP). Your CMP collects the user’s choice; Consent Mode tells Google’s tags what that choice means and how they should behave.

A correct implementation therefore needs more than simply switching Consent Mode on. You need to make sure:

• the correct consent states are set before Google tags run;
• those states update when somebody accepts or rejects consent;
• GA4 and Google Ads respond correctly;
• regional consent requirements are handled where necessary;
• the setup is tested for both accepted and rejected consent.

Why Google Consent Mode matters

As a Google Analytics 4 consultant, Consent Mode is something I’m increasingly asked about.

This guide covers how it works, Basic vs Advanced Consent Mode, the four main consent signals, implementation and, importantly, how to check whether it’s actually working.

What Is Google Consent Mode?

Google Consent Mode is a mechanism for communicating a visitor’s consent choices to Google tags on your website.

The important distinction is:

Consent Mode isn’t your cookie banner, and it isn’t your consent management platform.

Your CMP or cookie banner asks the visitor for consent and records their choice. Consent Mode communicates the relevant consent state to Google’s tags so they can adjust their behaviour accordingly.

A simplified version looks like this:

Visitor → Cookie banner/CMP → Consent choice → Google Consent Mode → Google tags → GA4 / Google Ads

It’s entirely possible to have a cookie banner installed without Consent Mode being configured correctly.

Likewise, simply installing a CMP that supports Consent Mode doesn’t mean the implementation is working as intended.

Do I Need Google Consent Mode?

If your website uses products such as Google Analytics 4, Google Ads or other Google tags and those tags need to respond to users’ consent choices, Consent Mode is likely to be relevant.

This becomes particularly important where you’re collecting consent from visitors in regions with privacy and consent requirements, or where you use Google advertising features with their own consent requirements.

Consent Mode itself shouldn’t, however, be confused with legal compliance.

It’s a technical mechanism for communicating consent choices to Google. Whether your website needs consent, who you need to ask and what constitutes valid consent are broader privacy and legal questions.

In practical terms, I normally start by asking:

• Which Google products are installed?
• Where are the site’s visitors located?
• Is there already a CMP or cookie banner?
• Which tags fire before somebody makes a choice?
• What happens when consent is accepted?
• What happens when consent is rejected?
• Is Google Ads being used?
• Does the business rely on remarketing or advertising measurement?

The answers determine what the Consent Mode implementation needs to do.

Google Consent Mode v2 and the Four Consent Signals

Google Consent Mode uses consent signals to tell Google tags what a user has or hasn’t consented to.

There are four particularly important signals.

analytics_storage

Controls whether storage related to analytics, such as Google Analytics cookies, is permitted.

For most websites using GA4, this is one of the fundamental consent states to understand.

ad_storage

Controls whether storage related to advertising is permitted.

This is particularly relevant where Google Ads tags and advertising measurement are being used.

ad_user_data

Controls whether user data can be sent to Google for advertising purposes.

ad_personalization

Controls whether personal data can be used for personalised advertising, including functionality such as remarketing.

You don’t necessarily need to memorise the parameter names.

What matters is that a visitor’s choice is translated into the correct consent states and Google’s tags behave appropriately for those states.

That’s where many implementation problems occur.

Basic vs Advanced Google Consent Mode

Consent Mode is generally implemented using one of two approaches: Basic or Advanced Consent Mode.

The main difference is what happens before the user grants consent.

	Basic Consent Mode	Advanced Consent Mode
Before the user interacts with the banner	Google tags are blocked	Google tags can load with consent denied
If consent is denied	Google tags remain blocked	Cookieless signals may be sent
If consent is granted	Google tags can run normally	Consent states update and tags operate accordingly
Measurement/modelling	More limited	Additional signals may be available for modelling

With Basic Consent Mode, Google tags are prevented from loading until the visitor interacts with the consent banner and grants the relevant consent.

With Advanced Consent Mode, Google tags can load before consent but operate with the relevant consent states set to denied. Limited, cookieless signals can be sent without setting or reading advertising or analytics cookies that require consent.

If the visitor subsequently grants consent, the consent states are updated.

Advanced Consent Mode isn’t simply a way of getting “better tracking”. It’s a different implementation approach and needs to be considered alongside your privacy requirements, CMP configuration and measurement needs.

Do I Need a CMP for Google Consent Mode?

A Consent Management Platform (CMP) is responsible for presenting consent choices to users and managing those choices.

Google Consent Mode communicates the appropriate consent state to Google tags.

They work together, but they’re not the same thing.

Many CMPs offer built-in integrations with Google Consent Mode, which can make implementation considerably easier, particularly when the CMP also integrates with Google Tag Manager.

When choosing a CMP, I’d consider:

• Does it integrate cleanly with your CMS or website platform?
• Does it support the regions in which you operate?
• Can consent behaviour be configured geographically?
• How does it integrate with Google Tag Manager?
• Can consent categories be mapped correctly to Google’s consent states?
• Does it keep appropriate consent records?
• How easy is it to test and debug?
• Can it also manage non-Google marketing and analytics technologies?

Platforms such as Cookiebot, CookieYes, OneTrust and Usercentrics can all form part of a Consent Mode implementation.

The important question isn’t simply which CMP supports Consent Mode?

It’s which CMP suits the website and can be configured so its tags behave correctly?

How Do You Implement Google Consent Mode?

There isn’t one universal implementation. The correct setup depends on the website, CMP, tag-management setup and Google products being used.

The process generally looks like this.

1. Audit the Tags Already Running

Before changing consent behaviour, establish what’s actually being loaded.

That includes GA4, Google Ads, Floodlight and any other advertising, analytics or marketing tags.

It’s also an opportunity to identify tags that shouldn’t still be on the website at all.

2. Configure the Consent Mechanism

Your cookie banner or CMP needs to collect the appropriate choices from visitors and make those choices available to the rest of the website.

The configuration may differ according to visitor location and the site’s privacy requirements.

3. Set the Default Consent States

Before the user makes a choice, Google’s tags need the appropriate default consent states.

These need to be set early enough in the page lifecycle.

If tags have already fired before the default consent state is established, the implementation isn’t doing what it’s supposed to do.

4. Update Consent When the Visitor Makes a Choice

When somebody accepts or rejects categories through the CMP, the corresponding Consent Mode states need to update.

For example, granting analytics consent may update analytics_storage, while advertising choices may affect ad_storage, ad_user_data and ad_personalization.

5. Make Sure Your Tags Respect Those States

If you’re using Google Tag Manager, you need to understand both Google’s built-in consent behaviour and any additional consent requirements applied to individual tags.

Google tags such as GA4 and Google Ads have built-in support for Consent Mode, but consent controls in GTM aren’t limited to Google tags.

You can also apply additional consent requirements to third-party tags such as Meta, LinkedIn, TikTok or Hotjar, so they only fire when the appropriate consent has been granted.

This means the consent choices collected by your CMP can influence tracking across the wider website, rather than only controlling Google Analytics and Google Ads.

This is an area where I regularly see setups become more complicated than they need to be, particularly when Google’s built-in consent checks and GTM’s additional consent requirements are confused.

6. Test It

Don’t assume the implementation works because the cookie banner appears or the CMP dashboard says Consent Mode is enabled.

Test the actual behaviour.

How To Test Whether Google Consent Mode Is Working

For me, this is one of the most important parts of the implementation.

A Consent Mode setup isn’t finished when the banner goes live. It’s finished when you’ve verified what happens in each consent state.

Google’s Tag Assistant is useful here, alongside browser developer tools and Google Tag Manager preview and debugging.

At minimum, I test the following scenarios.

Before the Visitor Makes a Choice

What are the default consent states?

Are they set before the relevant Google tags run?

Does the behaviour match the Basic or Advanced implementation you’ve chosen?

When the Visitor Rejects Consent

Do the consent states update correctly?

Are tags behaving as expected?

Are cookies or other storage mechanisms being used when they shouldn’t be?

When the Visitor Accepts Consent

Do the appropriate consent states change to granted?

Do GA4 and advertising tags subsequently behave as expected?

When an Existing Visitor Changes Their Mind

This is easy to overlook.

If somebody initially accepts and later changes their preferences, does the site update the consent state correctly?

Likewise, can somebody who previously rejected consent return to their settings and grant it?

Consent testing shouldn’t stop at clicking Accept All.

Common Google Consent Mode Problems

A visible cookie banner tells you very little about whether the underlying Consent Mode implementation is correct.

These are some of the problems I regularly look for.

The Consent Default Is Set Too Late

If Google tags run before the initial consent state has been established, tag behaviour may not reflect the user’s expected consent state.

The CMP Is Installed but Consent Mode Isn’t Configured

A banner can collect consent without those choices being communicated correctly to Google.

The front end looks finished. The implementation isn’t.

Consent Doesn’t Update Correctly

The user clicks Accept or Reject, but the corresponding consent states don’t change as expected.

Tags Have Been Unnecessarily Blocked

This can happen when Consent Mode and Google Tag Manager consent controls are layered together without understanding Google’s built-in consent behaviour.

The result can be tags that don’t run even when the appropriate consent has been granted.

Regional Behaviour Isn’t What You Expected

If your consent implementation varies by geography, test the actual behaviour rather than assuming the CMP is applying the correct configuration everywhere.

Nobody Tested Reject

This is surprisingly common.

Someone implements a cookie banner, clicks Accept All, sees GA4 firing and assumes everything is working.

The more revealing test is often what happens when you click Reject.

What Does Consent Mode Mean for Your Analytics Data?

Consent creates an unavoidable measurement trade-off.

If some users don’t consent to analytics or advertising storage, you’ll have less directly observable data about those visitors.

Consent Mode allows Google products to adjust their behaviour based on those choices and, depending on the implementation and eligibility, use available signals for modelling.

That doesn’t mean Consent Mode magically restores all the data you would otherwise have collected.

And it isn’t a substitute for a good analytics implementation.

Consent Mode should be one part of the wider measurement setup: clear tracking requirements, a sensible GA4 implementation, well-managed tags, appropriate consent controls and proper testing.

Is Your Website Ready for Google Consent Mode?

If you’re already using a CMP, don’t start by asking whether it has a Google Consent Mode switch.

Start by looking at what your website actually does.

Which tags load before consent?

What consent defaults are being sent?

What changes when somebody accepts?

What happens when they reject?

Are GA4 and Google Ads receiving the signals you expect?

Can a visitor change their preferences later?

And has anybody actually tested all of this?

Those questions tell you considerably more about the quality of your Consent Mode implementation than the presence of a cookie banner.

If you’re unsure how your current setup behaves, I can audit your analytics and ad tracking implementation, including GA4, Google Tag Manager, cookie consent and Google Consent Mode, and identify where tracking or consent behaviour isn’t working as intended.

---