What is Google Consent Mode?
How does Consent Mode work?
A consent management platform (CMP) is the tool that shows the banner and records the choice. It tells Google's tags what the visitor allowed. The tags then act on that signal.
There are two ways to run it. In basic consent mode, tags are blocked until the visitor consents. In advanced consent mode, tags load and, while consent is denied, send cookieless pings: signals without cookies1. Version 2 is not a third mode. It is two extra parameters on top of the existing ones2.
Google's Analytics Help describes behavioural modelling for consent mode, which estimates the behaviour of users who decline analytics cookies, and ties it to the advanced implementation3. Under basic, a refused banner means the tags send nothing at all, not even the consent status1. Eligibility and the rest of the detail are in consent mode conversion modelling.
Why does it matter for EEA traffic?
Google's EU user consent policy asks advertisers to collect consent from EEA users for measurement, ad personalisation and remarketing, and to share consent signals with Google4. So a shop with European traffic needs the consent signal to reach Google tags correctly. A banner that looks right but sends the wrong signal is a tracking fault, and it is easy to miss.
This page is not legal advice. What your banner must say and what you may collect: your counsel decides.
For ZFD: We check that consent signals actually reach Google. It is one of the checks in an ecommerce tracking audit.
What Consent Mode does not do
- It does not replace the cookie banner or the CMP.
- It does not decide whether you need consent.
- It does not turn a "no" into a "yes". It changes what the tags send after the answer.
Easily confused with
Consent Mode vs Cookie banner or CMP
The tool that asks the visitor. Consent Mode carries the answer to Google.
Consent Mode vs Server-side tracking
Collecting data on a server you control instead of in the browser. It is a different layer. Which data you may collect still depends on consent.
Consent Mode vs Enhanced conversions
Sending hashed first-party customer data to Google to improve matching. It is a data feature, not a consent signal.
Consent Mode vs First-party data
Data you collect directly from your own customers. Consent decides how you can use it.
For the basic and advanced trade-offs, read consent mode basic vs advanced.
FAQ

Does Consent Mode replace my cookie banner?
No. It relies on the banner. The banner collects the choice and Consent Mode passes it on to Google's tags.
What is the difference between basic and advanced consent mode?
Basic blocks tags until consent. Advanced lets tags load and send cookieless pings while consent is denied1.
Is Consent Mode legal advice?
No. It is a technical mechanism. Your counsel decides what is required.
Sources
- About consent mode (Tag Manager Help)Primary source
- Consent mode update for EEA (Tag Manager Help)Primary source
- [GA4] Behavioral modeling for consent mode (Analytics Help)Primary source
- EU user consent policy (Google Ads Help)Primary source
Let’s find what’s actually working.
Next step. Want it set up and checked against your real orders? See our analytics and tracking service.