Summary

  • Google Consent Mode lets a site tell Google tags what the visitor chose for ads and analytics storage.
  • “Basic” mode keeps Google tags from loading before a choice. “Advanced” mode can still send cookieless pings that may include page context.
  • Consent Mode does not control Meta, TikTok or other non-Google tags. Those need separate blocking.
  • Use Google’s documentation as the technical source of truth12. This article is not an install guide.

Many clinic sites run Google Analytics 4 (GA4) and Google Ads tags through Google Tag Manager. Google Consent Mode is how those tags learn whether the visitor allowed advertising or analytics storage. It is useful — and easy to misunderstand.

Google’s consent mode overview describes consent types such as ad_storage, ad_user_data, ad_personalization and analytics_storage1. The site owner remains responsible for collecting consent and for making both Google and third-party tags respect the choice1.

Google also publishes implementation guides for consent mode2. Those pages are the right place for technical detail. Here we focus on what clinic decision-makers should understand.

Basic versus advanced

  • Basic — Google tags wait until the visitor interacts with your consent interface. No Google hit before that interaction1.
  • Advanced — tags may load in a denied state and send cookieless pings used for modelling. Google’s documentation notes that page URLs can still appear in those pings1.

For a clinic, advanced mode on a condition or treatment URL can still move health-contextual page addresses toward Google before anyone agrees. That is why Consent Mode is a tool, not a finish line — a point we also make in our banner guide.

GA4 without health detail

Google asks properties to avoid sending personally identifiable information to Analytics3. Clinics should also avoid embedding condition names in event names, user properties or page paths sent to ads platforms where a quieter measurement design would do. See our privacy-safe dataLayer guide.

Checklist

  • Know whether your site uses basic or advanced Consent Mode.
  • Confirm non-Google tags are blocked separately when consent is denied.
  • Review which page paths GA4 and Google Ads receive on service and booking URLs.
  • Read Google’s consent mode documentation before changing Tag Manager.
  • Treat Consent Mode as one control among notice, policy and tag minimisation.

See what your own website shares

The free Akesis scan checks your homepage for advertising and analytics tags, whether they fire before consent, and what they receive. It takes about a minute and needs no install.

Run a free scan

Sources

  1. Google for Developers, Consent mode overview. developers.google.com/tag-platform/security/concepts/consent-mode
  2. Google for Developers, Set up consent mode on websites. developers.google.com/tag-platform/security/guides/consent
  3. Google Analytics Help, Best practices to avoid sending Personally Identifiable Information (PII). support.google.com/analytics/answer/6366371

Sources were checked on 27 October 2026. Links to third-party sites are provided for reference; Akesis is not affiliated with the organisations listed.