Consent Mode for Indian businesses: what applies, what doesn't, how to set it up
Chandan KumarFounder · Performance Marketing SpecialistListen to this article
The short answer
Consent Mode v2 is Google's requirement for advertisers serving users in the EEA and UK — it is not an Indian law, and a business with only Indian traffic is not obliged by Google to implement it. But India's DPDP framework does require notice, consent and the ability to withdraw, which means consent-aware measurement is coming regardless, and Consent Mode is the cleanest way to wire it into GA4 and Google Ads. Two modes matter: basic (tags don't fire until consent) and advanced (tags fire with cookieless pings, allowing modelled conversions). Advanced preserves far more measurement, and is the right default for most businesses — provided your banner genuinely gathers consent rather than assuming it.
On this page
I get asked about Consent Mode in two opposite ways. Indian businesses with no European traffic are told they must implement it urgently, which is not true. Indian businesses selling to the UK or Europe often have not heard of it and are quietly losing conversion data or risking their Google Ads setup. Both need the same thing: a clear picture of what applies to whom, and an implementation that survives DPDP. So let me separate the compliance question from the measurement question, because conflating them is why this topic is such a mess.
Who Consent Mode actually applies to
Google requires Consent Mode v2 for advertisers whose traffic includes users in the European Economic Area and the UK, because of European law. If you serve ads to, or measure, users in those regions and do not pass consent signals, you lose remarketing audiences and conversion measurement for that traffic.
If your customers are entirely in India, Google is not requiring it of you. That is the honest answer, and anyone telling you otherwise is selling something. What India does require, through the DPDP framework, is notice and consent for collecting personal data — a separate obligation that Consent Mode helps you honour technically but does not itself satisfy.
| Your traffic | Consent Mode v2 required by Google? | DPDP obligations? |
|---|---|---|
| India only | No | Yes — notice, consent, withdrawal |
| India + EEA/UK | Yes, for the EEA/UK portion | Yes, plus GDPR for EU users |
| Exporting services to EU/UK clients | Yes | Yes |
| No advertising, analytics only | Not by Google, but consent still needed for the data | Yes |
Two different questions
'Do I need Consent Mode?' is a Google policy question, answered by where your users are. 'Do I need consent?' is a legal question, answered by DPDP — and for Indian businesses the answer is yes regardless of Consent Mode.
Basic versus advanced, and why it matters
In basic mode, Google tags do not load at all until the user consents. Clean and simple, and you lose all data from anyone who declines or ignores the banner — which in practice is a large share of visitors.
In advanced mode, tags load immediately but send cookieless pings when consent is absent: no identifiers, no cookies, just enough signal for Google to model the conversions it cannot observe. You keep far more usable measurement while still respecting the choice. For most businesses advanced is the right default, and the difference in reported conversions between the two is frequently large enough to change budget decisions.
| Basic | Advanced | |
|---|---|---|
| Tag behaviour before consent | Does not load | Loads, sends cookieless pings |
| Data from non-consenting users | None | Anonymous signals, modelled conversions |
| Measurement retained | Lower | Substantially higher |
| Implementation complexity | Simpler | Moderate |
| Best for | Very cautious posture | Most businesses |
How to implement it without breaking your tracking
The order matters. Set default consent states before any Google tag loads — denied for advertising and analytics storage until the user chooses. Then update the consent state when they interact with the banner, and make sure that update happens once, reliably, and persists across pages.
Use a consent management platform that supports Google's consent signals natively rather than hand-rolling it, unless you have a good reason. Then test properly: open the site in a fresh session, decline, and confirm in tag debugging that pings are cookieless and no identifiers are set; accept, and confirm full tags fire. Most broken implementations I audit fail because nobody tested the decline path.
Implementation sequence
- 1Set defaults first — `denied` for ad_storage, ad_user_data, ad_personalization and analytics_storage, before any Google tag.
- 2Load your consent banner and wire its choices to a consent update.
- 3Update once, reliably, and persist the choice across pages and sessions.
- 4Enable advanced mode unless you have a specific reason for basic.
- 5Test both paths — accept and decline — in debug mode, in a clean session.
- 6Re-test after any tag manager change. This breaks silently and often.
What DPDP adds that Consent Mode does not cover
Consent Mode manages what Google's tags do. It does not write your notice, store your consent records, or propagate a withdrawal to your CRM, WhatsApp tool and email platform. Those are the DPDP obligations, and they live outside the tag manager.
So a compliant setup has two halves: the tag layer honouring consent signals, and the business layer recording who consented to what and when, with a withdrawal route that actually suppresses across every tool. Businesses that implement only the first half have tidy analytics and an unresolved compliance gap.
| Requirement | Consent Mode | Your systems |
|---|---|---|
| Stop Google tags before consent | Yes | — |
| Plain-language notice at collection | No | Yes |
| Auditable consent record | No | Yes |
| Withdrawal propagating to CRM, WhatsApp, email | No | Yes |
| Handling access and correction requests | No | Yes |
The banner is a conversion element, not a legal sticker
Most Indian sites either have no banner or have one that covers half the screen on mobile and blocks the phone number. Both are bad, and the second is worse — you are losing enquiries to a compliance widget.
Design it properly: short plain-language notice, genuine accept and decline options of equal visual weight, no dark patterns, never blocking key content on mobile, and a link to the full policy. Dark-pattern banners are increasingly likely to be treated as invalid consent, which means you carry the friction and get none of the protection.
Test on a real phone
Load your site on a mid-range Android handset on 4G. If the banner covers the call button, or takes two seconds to appear and shifts the layout, it is costing you money — fix that before worrying about modelled conversions.
What to expect in your reports
After a correct advanced-mode implementation, expect reported conversions to change — often down initially, then partially recovered through modelling. That is a truer picture, not a loss, and it is important to brief whoever reads the reports before you make the change rather than after.
Set the baseline deliberately: record two weeks of pre-change numbers, note the switch date in your reporting, and compare like-for-like afterwards. Teams that skip this step spend the following quarter arguing about whether performance dropped when actually only the measurement changed.
Brief before, not after
Conversion counts change when consent-aware tracking goes live. Document the switch date and the pre-change baseline, or you will spend a quarter arguing about a measurement artefact.
Key takeaways
- Consent Mode v2 is Google's requirement for EEA and UK traffic, not an Indian legal obligation — but DPDP means Indian businesses need consent-aware measurement anyway.
- Use advanced mode unless you have a specific reason not to: it preserves far more usable measurement through cookieless pings and modelled conversions.
- Consent Mode only governs Google tags — notice, consent records and withdrawal propagating across CRM, WhatsApp and email are separate obligations you must build.
Frequently asked questions
Does Google Consent Mode v2 apply to Indian businesses?
Only if your traffic includes users in the EEA or UK — that is where Google's requirement comes from. A business with purely Indian traffic is not obliged by Google to implement it. India's DPDP framework separately requires notice, consent and withdrawal for personal data, so consent-aware measurement is still necessary; Consent Mode is simply the cleanest way to wire that into Google's tags.
What is the difference between basic and advanced Consent Mode?
In basic mode, Google tags do not load at all until a user consents, so you lose all data from anyone who declines or ignores the banner. In advanced mode, tags load and send cookieless pings without identifiers when consent is absent, letting Google model unobserved conversions. Advanced retains substantially more usable measurement and is the right default for most businesses.
Do I need a cookie banner in India?
You need notice and consent for collecting personal data under the DPDP framework, and for most websites a banner is the practical way to obtain and record it for analytics and advertising cookies. Design it as a genuine choice — plain language, accept and decline of equal weight, no dark patterns — and make sure it does not cover your call button on mobile.
Will my conversions drop after implementing Consent Mode?
Reported conversions usually fall initially and then partially recover as modelling kicks in. That is a change in measurement accuracy rather than in performance. Record a two-week baseline before the switch, note the change date in your reporting, and brief whoever reads the reports beforehand — otherwise the next quarter is spent debating a measurement artefact.
Is Consent Mode enough for DPDP compliance?
No. It controls what Google's tags do before and after consent, and nothing else. DPDP also requires a plain-language notice at the point of collection, an auditable record of who consented to what and when, and a withdrawal route that suppresses that contact across every system — CRM, WhatsApp, email and ad audiences. Those live in your business systems, not in your tag manager.
Tools & next steps
Put this into practice, go deeper, or see how we'd do it for you.
Written by
Mr. Chandan Kumar
Founder & Performance Marketing Director, Global Info Edge
Founder of Global Info Edge and a performance-marketing specialist with 18+ years — Google & Meta ads, conversion funnels and measurable growth.
View full profile