Consent mode and analytics
Google's Consent Mode lets tags read consent-state signals (such as analytics_storage and ad_storage) and adapt: when consent is denied, tags can send cookieless pings or send nothing, and gaps may be statistically modelled. It is a tag-behaviour mechanism, not a consent banner, and it does not by itself make collection lawful. This is an educational overview, not legal advice.
What this means
Consent mode is a Google feature where tags receive consent-state parameters — for example analytics_storage and ad_storage set to granted or denied — and change behaviour accordingly. With consent granted, tags work normally; with consent denied, tags can fall back to cookieless pings or suppress storage entirely.
What it does and does not do
Consent mode is plumbing between your consent banner and Google's tags; it is not the banner and not a lawful basis. When consent is denied, Google documents that some metrics may be modelled to fill gaps, which means reported figures can include estimated rather than directly observed values. You still need a compliant consent mechanism and a lawful basis for whatever you collect.
- Reads consent-state signals like analytics_storage / ad_storage
- Denied consent: cookieless pings or no collection
- Gaps may be statistically modelled, not observed
How it appears in analytics and logs
Consent mode means tag behaviour changes with consent state — denied consent yields cookieless or withheld hits, and reported gaps may be modelled rather than directly observed.
Diagnostic use case
Use consent mode to make Google tags respect consent state, while remembering you still need a compliant consent mechanism and lawful basis behind it.
What WebmasterID can help detect
Because WebmasterID is cookieless and first-party, it sidesteps much of the tag/consent-state complexity that consent mode exists to manage.
Common mistakes
- Treating consent mode as a substitute for a consent banner.
- Assuming consent mode alone makes collection lawful.
- Reading modelled figures as directly measured values.
Privacy and accuracy notes
Consent mode is a control layer, not compliance by itself. WebmasterID avoids the problem differently: it is cookieless, so it does not depend on consent-state plumbing to behave privately.
Related pages
- Consent banners and analytics
A consent banner (or CMP) is the interface that asks visitors to accept or refuse non-essential storage and processing. For consent to be valid under EU rules it must be freely given, specific, informed, and unambiguous — which rules out pre-ticked boxes and 'accept-only' dark patterns. Reducing what needs consent in the first place is the cleaner path. This is educational, not legal advice.
- Cookieless analytics: how it works and its limits
Cookieless analytics records visits and events without setting cookies or persistent cross-site identifiers. It relies on first-party, server-side signals and aggregate counting. The trade-off is honest: it cannot follow an individual across sessions the way cookie-based tracking can — which is exactly the point for privacy-first measurement.
- The IAB TCF and the consent string
The IAB Europe Transparency & Consent Framework (TCF) is an industry standard for capturing and communicating users' consent choices across the advertising supply chain. A consent management platform encodes the user's choices into a standardised 'TC string' that downstream vendors read. It is widely used in ad tech and can touch analytics tied to it. This is an educational overview, not legal advice.
- Privacy-first analytics
Cookieless by design, less consent plumbing to manage.
Sources and verification notes
- Google — Consent mode overview (Analytics Help)Vendor documentation. Educational, not legal advice.
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.