Skip to main content
NewNMC’s advertising guidelines for doctors are in force from 6 Oct 2026. See what to change, and get a free compliance auditNew NMC advertising rules for doctors: what to change
Analytics

Consent Mode v2 for Indian Hospitals: When It Applies and How to Implement It

Consent Mode v2 is a Google requirement for EEA, UK and Swiss traffic, not an Indian legal rule. Here is when a hospital needs it, basic versus advanced mode, and a clean implementation order.

Consent Mode v2 for Indian Hospitals: When It Applies and How to Implement It

Consent Mode v2 is mentioned in agency decks as if every Indian website must have it. It is more specific than that. It is a Google mechanism, introduced to support Google's consent policy for users in Europe, and what it does is pass a visitor's consent choices to Google's tags so that the tags behave accordingly. Whether an Indian hospital needs it depends on who its advertising reaches and on what the hospital decides to do with consent more generally.

This article is for hospital marketing leads, doctors who run their own practice websites, and the developers who support them. It separates what is required from what is optional, explains basic and advanced mode in plain terms, and gives an implementation order. It is not legal advice. Your counsel owns the interpretation of the Digital Personal Data Protection Act.

What Consent Mode v2 is

Consent Mode lets your site tell Google tags what the visitor has agreed to. In its November 2023 update, two parameters were added to the existing ad_storage and analytics_storage, as set out in Google's consent documentation:

  • ad_user_data: consent for sending advertising-related user data to Google.
  • ad_personalization: consent for personalised advertising.

Google's Analytics help explains the effect. When ad_user_data is denied, using personal data for online advertising is disabled, including conversion measurement uses such as enhanced conversions. When ad_personalization is denied, remarketing receives no data and personalised advertising is disabled. Personalised advertising needs both granted.

Two other things belong in the definition. Consent Mode does not store the choice: you must persist it yourself and reapply it on later pages. And it is not a consent banner. You still need a banner or preference centre that collects the choice, and a record of it.

Where it applies

Required by Google: EEA, UK and Switzerland traffic. Google's EU user consent policy covers end users in the European Economic Area, the UK and Switzerland. It requires you to obtain legally valid consent for cookies and for collecting, sharing and using personal data to personalise ads, to keep records of consent, and to tell users how to revoke it.

For an Indian hospital, that matters if you run Google Ads or measure conversions from visitors in those regions. A hospital that advertises its medical tourism programme to patients in the UK, for example, has users in scope. A hospital whose ads target only Indian cities does not fall under that policy for those users, although some visitors may still arrive from Europe.

Not required by Google for India-only traffic. Nothing in the policy imposes Consent Mode on visitors in India.

The Indian legal position is separate. The DPDP Act, 2023 is built on notice and consent for processing personal data, and the Rules were notified in November 2025 with an eighteen-month period for phased compliance. Consent Mode is a technical way to make Google tags respect a choice; it does not by itself satisfy a notice requirement, record consent in the form the law expects, or cover tags from other vendors. If your counsel decides you need consent for analytics and advertising tags in India, Consent Mode is one of the tools to implement that decision, and it is worth building to the same standard as for the EEA. Our article on the DPDP Act for healthcare marketing sets out the Act in a marketing context.

GCC. The UAE and Saudi Arabia have their own personal data laws, and health data is typically handled under stricter sector rules. Google's policy is not the governing text there. Check the local rules with counsel, and treat Consent Mode as optional technical support rather than proof of compliance.

Basic versus advanced mode

Google's Ads help on consent mode draws the line this way.

Basic mode. Google tags stay blocked until the visitor interacts with the consent banner. If the visitor declines, no data goes to Google at all, not even the consent status. Conversion modelling then relies on a general model.

Advanced mode. Tags load when the site loads. While consent is denied, they send cookieless pings. Once consent is granted, they send full measurement data. This permits an advertiser-specific model, which is more detailed.

The decision is partly technical and partly a risk decision.

QuestionBasicAdvanced
Does any signal reach Google before the visitor chooses?NoYes, cookieless pings
Modelling qualityGeneral modelAdvertiser-specific model possible
Fits a strict "nothing before consent" policyYesNeeds counsel's sign-off
Implementation effortLower: block tags until consentHigher: defaults, updates, testing
Typical userProvider with legal advice that rules out pre-consent pingsProvider with enough traffic to benefit from modelling and approval to send pings

For a hospital with a cautious privacy stance, basic mode is the defensible starting point. If the hospital later has enough traffic for modelling to matter and counsel is comfortable with cookieless pings, move to advanced.

Implementation order

The order of operations matters more than which CMP you choose.

  1. Pick a consent platform that supports Consent Mode and records consent decisions with a timestamp and the version of the notice shown. Check its integration with Tag Manager.
  2. Set defaults before any measurement. Google's documentation says to call gtag('consent', 'default', ...) on every page before commands such as config or event, and to scope defaults to specific regions where possible. For example, denied for EEA, UK and Switzerland, and a default that matches your Indian policy elsewhere.
  3. Set wait_for_update for asynchronous banners. This tells tags how long to wait, in milliseconds, for the consent update before sending data. Google's example uses 500.
  4. Send the update when the visitor chooses. Call gtag('consent', 'update', ...) when the user accepts, rejects or changes their mind, including revocation.
  5. Persist the choice and reapply it on every following page.
  6. Map the four signals to your banner's categories: analytics_storage to analytics, ad_storage, ad_user_data and ad_personalization to advertising.
  7. Configure tags with consent checks in Tag Manager, including non-Google tags, which do not follow Consent Mode automatically.
  8. Test in preview and in the browser network panel. With everything denied, no cookies from the denied categories should be set. With everything granted, tags should send full data.

Want this applied to your practice? Get a free analytics audit.

Book my free audit

Healthcare-specific points

  • Sensitive pages. Consent Mode controls tag behaviour, not what the page content reveals. Pages about sensitive services still shouldn't carry advertising tags. Google's personalised advertising policy treats health as a sensitive interest category, and consent does not change that.
  • Patient portal and telemedicine. Keep these out of the marketing tag set altogether.
  • Banner wording. Say what each category does in plain language, in English and in the languages your patients use. Equal prominence for accept and reject avoids a banner that looks designed to extract a yes.
  • Records. Keep consent logs for the period your policy sets, with a way to find an individual's record if asked.
  • Server-side tagging. If you run a server container, pass the consent state to it and respect it there, as covered in server-side tracking and consent mode for healthcare.

Common mistakes

  • Treating Consent Mode as a banner. It is a signalling layer.
  • Setting defaults after the Google tag has already fired.
  • Updating consent for Google tags but leaving other vendors' tags firing.
  • Setting granted as the default everywhere to keep numbers up.
  • Forgetting that conversion numbers will drop once consent is respected; set the expectation with leadership before launch.

A short worked example

A hypothetical 150-bed hospital in Hyderabad runs Google Ads for its international patient programme. Most clicks come from the Gulf and East Africa, but a small number come from patients and relatives living in the UK.

The team starts with a region-scoped default. For UK, EEA and Switzerland visitors, all four signals default to denied until the banner reports a choice. For India and the Gulf, counsel advises the same banner and the same defaults, since the hospital prefers one behaviour and one record format everywhere, with the legal basis reviewed per market. The team chooses basic mode, so Google tags do not load before a choice.

On the first page of a session the banner appears. The visitor accepts analytics and rejects advertising. The consent platform sends an update setting analytics_storage to granted and the other three to denied. GA4 then measures the visit normally, while Google Ads tags do not receive advertising data. The platform stores the choice, so the next page reapplies it before any tag fires.

In reports, the team sees fewer Google Ads conversions than before. They compare against enquiries logged in the CRM, find the gap is explained by rejected advertising consent, and agree the CRM count is the figure used for budget decisions. That conversation is better held before launch than after.

The point of the example is the order, not the numbers: defaults first, update on choice, persistence, then tag behaviour and reporting expectations.

Where to start

  1. List your ad markets. If EEA, UK or Swiss users are in scope, Consent Mode is a requirement for those users; otherwise it is a decision.
  2. Get counsel's view on notice and consent for India and any GCC markets.
  3. Choose basic mode unless counsel and traffic volume support advanced.
  4. Implement defaults, updates and persistence in that order, then test.
  5. Brief leadership on the measurement impact.

For hands-on help, see our analytics and tracking service, the compliance overview and the GA4 glossary entry.

Filed underconsent mode v2 IndiaGoogle consent mode v2 hospitalconsent mode basic vs advancedad_user_data ad_personalizationconsent mode DPDPcookie consent healthcare website

About the author

Co-Founder & CTO · Gurugram, India

Arush builds the systems the rest of the company runs on — the patient-acquisition pipelines, the AI chatbots, the analytics that tie a single click to a booked appointment. If a campaign reports a number, it's because something his team built is tracking it.

Free guide · 15 pages

The Patient Acquisition Blueprint

A 90-day plan from first search to booked appointment.

The Pioneers Brief — one essay, three benchmarks, one teardown, every Thursday. Subscribe free →

Free analytics audit

Your next chapter starts with a conversation.

Three quick questions. We come prepared with a plan for your specialty and city.

  • A 30-minute call with a healthcare specialist
  • Your top three growth opportunities, in writing
  • Honest advice — even if that means not hiring us
  • No obligation and no hard sell
You’ll speak with a senior strategist
Consultations are hosted by Arush Thapar’s team.
Step 1 of 3Takes 30 seconds

What do you want to improve first?

Details stay privateNo obligationReply within 1 working day

Client portfolio · Healthcare websites

Work relevant to consent mode v2 for indian hospitals when it applies and how to.

Explore client work →