Is Google Consent Mode mandatory?

Google has made Consent Mode, or an equivalent way of passing consent signals, a requirement for using certain advertising and measurement features with users in some regions, notably the European Economic Area. Requirements change, so check Google's current policies. Separately, your local laws may require consent regardless of Google's rules.

What is the difference between Consent Mode v1 and v2?

The update commonly called v2 added two signals, ad_user_data and ad_personalization, to the original storage-related signals. They govern whether user data can be sent to Google for advertising and used for personalised advertising. Implementations built before the update may need changes to pass these signals.

Does Consent Mode work with Meta or LinkedIn pixels?

No. Consent Mode is a Google framework that controls Google tags. Other vendors' pixels need to be governed through your consent management platform and tag manager, so that they fire only when the relevant consent is given. Check each vendor's documentation for its own consent mechanisms.

Will Consent Mode reduce my reported conversions?

Respecting refusals means fewer observed conversions than tracking everyone would show. Modelling can estimate some of the gap, especially in advanced setups with enough volume. Compare reported conversions with your CRM or order system to understand the difference, and track consent rate alongside performance.

Do I need Consent Mode for a website in India?

India's DPDP Act makes consent central to processing personal data, and Google's own requirements may apply depending on features and audiences. Whether specific analytics or advertising tracking needs consent under Indian law is a question for legal advice, but a consent-aware setup is a sound and increasingly expected practice.

Google Consent Mode Explained: Basic, Advanced and v2

Consent Mode is often misunderstood as a consent banner. It is not. Your consent management platform (CMP), the banner and preference centre, asks visitors for permission. Consent Mode is the messenger that carries their answer to Google's tags, which then change how they behave: whether they set cookies, what they send and how the data is used.

It is equally not a compliance guarantee. Whether your approach to consent is lawful depends on the laws where your visitors are, what you tell them and how you honour their choices. Consent Mode is one technical component of that system. Google's requirements around it, especially for users in Europe, have tightened over time, so check Google's current documentation and take legal advice for your markets.

The banner asks the question. Consent Mode makes sure the tags hear the answer.

Consent Mode works with a small set of named consent types, each of which can be granted or denied. The most widely used are listed below; Google's documentation has the full and current list.

Signal	Governs	If denied
analytics_storage	Cookies and storage used for analytics	Analytics tags avoid setting analytics cookies
ad_storage	Cookies and storage used for advertising	Ad tags avoid setting advertising cookies
ad_user_data	Whether user data may be sent to Google for advertising	Data is not used for advertising purposes in the same way
ad_personalization	Whether data may be used for personalised advertising such as remarketing	Personalised ads and remarketing are restricted

The latter two were added in an update widely referred to as Consent Mode v2. If your implementation predates it, check whether it passes all current signals; older setups may be incomplete.

Basic and advanced implementations

There are two broad ways to implement Consent Mode, and the difference matters both for privacy and for measurement.

Fig. 01 · Comparison

Tap to explore

Basic versus advanced Consent Mode

BasicAdvanced

Before a choice is madeGoogle tags do not loadTags load with consent defaulting to denied

If the visitor declinesNo data sent to GoogleCookieless pings without identifiers may be sent

Conversion modellingMore limited, based on general modelsCan use the cookieless signals to model more specifically

Privacy postureMore conservativeDepends on whether cookieless pings are acceptable in your jurisdiction

Summary of the principles. Exact behaviour is defined in Google's current documentation.

Advanced mode tends to give better modelled measurement; basic mode is more conservative. Which is appropriate is partly a legal question, because some regulators and lawyers take the view that even cookieless pings require consent in certain jurisdictions. This is exactly the kind of decision that should involve your legal or privacy adviser rather than being made by whoever configures the tags.

What modelling does, and its limits

When visitors decline consent, their conversions are not observed in the usual way. Google can use modelling to estimate some of the conversions and behaviour that were lost, based on patterns among consenting visitors and, in advanced mode, signals from cookieless pings. Modelled data then appears blended into reports.

Modelling is useful but should be understood for what it is: an estimate. It typically requires minimum volumes before it activates, it cannot reconstruct individual journeys, and it is not visible line by line. For financial reporting, rely on your own order and CRM data. For trend and channel analysis, modelled data is generally better than ignoring the gap entirely.

Fig. 02 · Process

Tap to explore

How a consent choice reaches the tags

Each link must work. Most failures happen at the default state or the update step.

Note any change to your consent setup in your reporting log, because it can shift trends overnight.

Implementing it properly

Most CMPs certified by Google offer built-in Consent Mode integration, and Google Tag Manager has consent settings that make tags aware of the required signals. The technical work is not large. The care lies in the order of events and in testing.

Checklist

0/8

Consent Mode implementation checklist

Note the point about non-Google tags. Consent Mode is a Google framework. Meta, LinkedIn, heatmap tools and others need to be governed by your CMP and tag manager separately. A site with perfect Consent Mode and uncontrolled third-party pixels is not respecting consent.

Banner design is where most setups fail

Teams spend hours on tag configuration and minutes on the banner, yet the banner decides whether consent is meaningful at all. Pre-ticked boxes, an accept button in bright colour beside a refuse link hidden in grey text, or a refusal buried two screens deep may increase consent rates in the short term. They also invite regulatory scrutiny and teach visitors that the brand plays games.

A good banner says plainly what is collected and why, offers accept and refuse with equal prominence, lets people choose by purpose and makes changing one's mind easy. Write it in the language your visitors use, including regional languages where your audience expects them. Then measure consent rate by device and page type: a sharp difference often reveals a banner that is broken or badly displayed on mobile.

Consent Mode is most discussed in a European context, but its logic applies wherever consent is required or expected. In India, the Digital Personal Data Protection Act places consent at the centre of processing personal data, with requirements for clear notice and easy withdrawal. How its rules apply to analytics and advertising cookies is a matter for legal advice, but a consent-aware tag setup puts a business in a far better position than one that fires everything regardless.

There is also a commercial argument. Visitors increasingly notice how sites treat their data. A clear, honest banner and tags that genuinely respect a refusal are part of brand trust, not just compliance.

Living with less observed data

Whatever setup you choose, some visitors will decline and your observed data will be incomplete. Accept that, and design measurement accordingly. Track consent rates as a metric in their own right, so you can tell a fall in conversions from a fall in consent. Lean on first-party outcomes from your CRM and order system. Use incrementality testing and modelling for channel decisions rather than chasing complete user-level data.

Myth vs reality

Consent Mode myths

Key takeaways

01Consent Mode carries consent choices from your banner to Google tags; it does not collect consent itself.
02Current setups should pass all required signals, including ad_user_data and ad_personalization.
03Basic mode blocks tags until consent; advanced mode sends cookieless pings, which needs a legal view.
04Modelled conversions are useful estimates, not a substitute for your own revenue data.
05Non-Google tags need their own consent controls, and consent rate should be tracked as a metric.

Frequently asked

Is Google Consent Mode mandatory?: Google has made Consent Mode, or an equivalent way of passing consent signals, a requirement for using certain advertising and measurement features with users in some regions, notably the European Economic Area. Requirements change, so check Google's current policies. Separately, your local laws may require consent regardless of Google's rules.
What is the difference between Consent Mode v1 and v2?: The update commonly called v2 added two signals, ad_user_data and ad_personalization, to the original storage-related signals. They govern whether user data can be sent to Google for advertising and used for personalised advertising. Implementations built before the update may need changes to pass these signals.
Does Consent Mode work with Meta or LinkedIn pixels?: No. Consent Mode is a Google framework that controls Google tags. Other vendors' pixels need to be governed through your consent management platform and tag manager, so that they fire only when the relevant consent is given. Check each vendor's documentation for its own consent mechanisms.
Will Consent Mode reduce my reported conversions?: Respecting refusals means fewer observed conversions than tracking everyone would show. Modelling can estimate some of the gap, especially in advanced setups with enough volume. Compare reported conversions with your CRM or order system to understand the difference, and track consent rate alongside performance.
Do I need Consent Mode for a website in India?: India's DPDP Act makes consent central to processing personal data, and Google's own requirements may apply depending on features and audiences. Whether specific analytics or advertising tracking needs consent under Indian law is a question for legal advice, but a consent-aware setup is a sound and increasingly expected practice.

Published by Fabulous.Media, a network of specialist marketing agencies. Updated 9 October 2026. Platform features change often; check current official documentation before acting on platform-specific detail.