Consent mode is a tag configuration mechanism, best known from Google’s tagging platform, that passes a visitor’s consent choices from a consent banner to analytics and advertising tags, so that each tag adjusts its behavior to the consent state. Instead of only loading or blocking tags, consent mode tells them whether they may use cookies, send user data for advertising or personalize ads.
In privacy in marketing, consent mode sits at the junction of legal compliance and measurement. It lets organizations respect refusals while preserving some aggregate measurement, but it also raises questions about how much data may be sent when a visitor has said no.
How consent mode passes consent states to tags
Consent mode works through two commands issued in the page’s tagging layer. A default command runs before any measurement tag fires and sets each consent type, usually to denied for visitors in regions that require opt-in consent. An update command runs when the visitor makes a choice in the consent management platform and switches the relevant types to granted or keeps them denied.
Tags read these states at the moment they fire. With analytics storage denied, an analytics tag does not read or write its cookies. With ad storage denied, advertising tags do not use advertising cookies. A wait-for-update setting, typically a few hundred milliseconds, lets tags pause briefly so that a returning visitor’s stored choice can be applied before the first hit is sent.
Defaults can be set per region, which allows a site to apply denied defaults for visitors from the European Economic Area while using granted defaults where the law permits opt-out models. The consent banner itself remains the job of a consent management platform; consent mode only transports the result.
Consent types and what they control
Consent mode uses a fixed set of consent types, each controlling a different aspect of tag behavior. The second version of the framework added two types that concern advertising use of user data rather than storage on the device.
| Consent type | What it controls | Typical banner category |
|---|---|---|
| ad_storage | Advertising cookies and device identifiers | Marketing |
| analytics_storage | Analytics cookies such as visit duration | Statistics |
| ad_user_data | Sending user data to the platform for advertising | Marketing |
| ad_personalization | Use of data for personalized advertising and remarketing | Marketing |
| functionality_storage | Storage supporting site functions such as language | Preferences |
| personalization_storage | Storage for personalized content | Preferences |
| security_storage | Storage for authentication and fraud prevention | Strictly necessary |
Since March 2024, advertisers who want to use audience and personalization features for traffic from the European Economic Area are expected to send the ad_user_data and ad_personalization signals. Missing signals can lead to restricted audience lists and conversion data for that traffic.
Basic and advanced implementation compared
Consent mode can be implemented in two ways that differ in what happens before or without consent. The choice has both legal and measurement consequences, so it should be made together by legal and analytics teams.
| Aspect | Basic implementation | Advanced implementation |
|---|---|---|
| Tag loading before choice | Tags blocked until consent | Tags load with denied defaults |
| Data sent after refusal | None | Cookieless pings without identifiers |
| Conversion modeling | General model based on all advertisers | Advertiser-specific model from own pings |
| Measurement gap after refusal | Larger | Smaller, filled by modeling |
| Legal exposure | Lower | Higher, debated in some jurisdictions |
Cookieless pings in advanced mode carry information such as the timestamp, page, user agent, consent state and whether a conversion happened, while the IP address is still visible to the receiving server. The platform uses these pings for conversion modeling and behavioral modeling, which estimate the activity of non-consenting visitors from consenting ones once traffic thresholds are reached.
Consent mode compared with related marketing concepts
Consent mode is a signal transport layer, not a data strategy. It is often mentioned together with neighboring Terms of the Topic, but it serves a narrower purpose.
| Concept | Role | Relationship to consent mode |
|---|---|---|
| Consent management platform | Collects and records user choices | Supplies the states that consent mode transmits |
| Cookieless measurement | Measures without device storage | Advanced consent mode is one form of it |
| First-party data | Data collected directly by the organization | Its advertising use is gated by ad_user_data |
| Zero-party data | Data users share intentionally | Still subject to consent signals when used for ads |
| Server-side tagging | Moves tag processing to a controlled server | Must forward consent states to every vendor |
Compliance questions and common implementation errors
Consent mode does not make a website compliant by itself. Under the ePrivacy rules, reading or storing information on a device requires consent, and some regulators and practitioners argue that advanced-mode pings after refusal may still involve processing that requires a legal basis. The question is not settled uniformly across European jurisdictions, so the decision should be documented.
- Defaults set too late: tags fire before the default command, so the first page view is collected without any consent state.
- Banner and signals out of sync: the visitor refuses marketing, but the update command still grants ad_storage.
- Missing version two signals: ad_user_data and ad_personalization are never sent, which limits audiences.
- Third-party tags ignored: tags from other vendors do not read consent mode and must be blocked separately.
- Modeled data treated as observed: reports mix modeled conversions with measured ones without clear labeling.
A reliable setup is verified with tag debugging tools that show the consent state attached to each hit, tested for both acceptance and refusal paths and for every region with a different default.
Put simply
Consent mode is a way for a website to tell its measurement and advertising tools what a visitor agreed to. If the visitor accepts cookies, the tools work normally. If the visitor refuses, the tools switch to a limited mode.
It is like a receptionist who passes a note to every department saying what a guest allowed. Each department then follows the guest’s wishes. The note itself does not ask the question. A separate consent banner does that.
In practice
An online furniture shop selling across Europe runs paid search campaigns and uses a consent banner. Its audit shows that analytics and advertising tags fire on the first page view before the banner appears, and that refusals are not reaching the advertising platform at all.
The team configures the tag manager so that a denied default for all four main consent types loads before any other tag for visitors from the European Economic Area, connects the banner to send update commands, and chooses the basic implementation after its legal review. Measured conversions from European traffic fall, as expected, but the shop now has consistent consent records, working audience signals for consenting visitors and a clear audit trail showing that refusals stop data collection.