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.
| Question | Basic | Advanced |
|---|---|---|
| Does any signal reach Google before the visitor chooses? | No | Yes, cookieless pings |
| Modelling quality | General model | Advertiser-specific model possible |
| Fits a strict "nothing before consent" policy | Yes | Needs counsel's sign-off |
| Implementation effort | Lower: block tags until consent | Higher: defaults, updates, testing |
| Typical user | Provider with legal advice that rules out pre-consent pings | Provider 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.
- 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.
- Set defaults before any measurement. Google's documentation says to call
gtag('consent', 'default', ...)on every page before commands such asconfigorevent, 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. - Set
wait_for_updatefor asynchronous banners. This tells tags how long to wait, in milliseconds, for the consent update before sending data. Google's example uses 500. - Send the update when the visitor chooses. Call
gtag('consent', 'update', ...)when the user accepts, rejects or changes their mind, including revocation. - Persist the choice and reapply it on every following page.
- Map the four signals to your banner's categories:
analytics_storageto analytics,ad_storage,ad_user_dataandad_personalizationto advertising. - Configure tags with consent checks in Tag Manager, including non-Google tags, which do not follow Consent Mode automatically.
- 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.




