Consent state dimension
The consent state describes the Consent Mode signals attached to a hit — chiefly whether analytics_storage and ad_storage are granted or denied. GA4 reads these signals to decide whether to use cookies and how to process the hit; when consent is denied, measurement may be cookieless and gaps can be filled by GA4's behavioural modelling. Treating consent state as identity, or ignoring its effect on data completeness, leads to misreadings.
What this means
Consent state is the set of Google Consent Mode signals on a request — most importantly analytics_storage (controls analytics cookies) and ad_storage (controls advertising cookies), each granted or denied. The tag reads these before deciding how to measure.
With analytics_storage granted, GA4 measures with cookies as usual. With it denied, GA4 collects cookieless pings (where configured) and may model the missing behaviour.
Why it shapes your data
Denied consent means fewer cookie-based observations, so GA4 can fill conversions and behaviour using modelling. That makes consent state inseparable from data completeness: a property with high denial rates carries more modelled and less observed data. Report consented and modelled portions transparently. Consent Mode and banner design are legal questions — treat this as educational, not advice.
- analytics_storage and ad_storage drive cookie use
- Denied consent can produce cookieless, modelled data
- Denial rate affects observed-vs-modelled balance
How it appears in analytics and logs
A denied analytics_storage signal means the hit was processed without analytics cookies, often contributing to modelled rather than fully observed data.
Diagnostic use case
Use consent state to understand how much of your data is consented versus modelled, and to keep granted and denied measurement appropriately separated.
What WebmasterID can help detect
WebmasterID is consent-aware by design, helping you distinguish consented, cookieless, and modelled measurement instead of presenting them as one undifferentiated total.
Common mistakes
- Treating consent state as a user identifier.
- Ignoring modelling when denial rates are high.
- Assuming denied consent means no data at all.
Privacy and accuracy notes
Consent state is a privacy control, not a tracking key. This page is educational, not legal advice; configure Consent Mode and banners with your own legal counsel.
Related pages
- Signed in with user ID dimension
The signed in with user ID dimension reports whether activity occurred while a User-ID was set — typically because the person was logged in. GA4 derives it from the presence of a developer-supplied User-ID on the session. It enables cross-device stitching of authenticated activity, but only when you have a lawful basis and a non-personal identifier, so it is governed by consent and policy, not enabled by default.
- Consent Mode v2 signals
Consent Mode v2 is Google's updated mechanism for passing a user's consent choices to Google tags, extending the original analytics and ad-storage signals with two advertising-focused parameters. When consent is absent, tags adjust behaviour rather than firing fully. This page explains the v2 signals and how they shape what data Google tags collect.
- Consent, modelling, and data gaps
Where consent is required before analytics runs, declined or pending consent means no data is collected for those visitors — a real gap, not lost interest. Some tools fill the gap with modelled estimates rather than measured counts. This page explains how consent shapes collection, what modelling is, and how to read a dataset that mixes measured and modelled data. Educational, not legal advice.
- Privacy-first analytics
Consent-aware measurement with clear data provenance.
Sources and verification notes
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.