Skip to content
Faisal Mahmud TusherDigital marketing, SEO & analytics
with Faisal Tusher

Glossary term

Consent Mode

A Google tag feature that adjusts what tags collect according to the visitor's consent choices.
Analyticsplatform featureUpdated

Before consent mode, a tag either ran or was blocked. Google's consent mode replaced that switch with a state the tags can read. Google's tag documentation describes it as a way to communicate users' consent choices to Google tags, which then adjust how they use cookies and identifiers and what they send.

It is easy to give it more credit than it deserves. It does not display a banner or record proof of consent; a consent management platform does. It does not decide which laws apply, which regions need a banner or what the banner must say; those are legal and policy questions that the privacy, consent and measurement guide addresses. And it governs Google's tags directly; other vendors' tags respect the same choices only if the tag manager is configured to gate them.

The states are organised as consent types, each a named switch. The two that matter most to measurement are analytics_storage, which governs analytics cookies such as the identifier that links a visitor's sessions, and ad_storage, which governs advertising cookies such as click identifiers. Two further types, added more recently, govern advertising use of data: ad_user_data, whether user data may be sent to Google for advertising, and ad_personalization, whether it may be used for personalised advertising such as remarketing.

Every page load starts with a default state, declared before any Google tag runs, and changes with an update when the visitor chooses. The order matters: a default declared after the tags have loaded arrives too late to stop what they have already stored. The consent mode implementation guide covers the commands, regional defaults and verification step by step.

In practice: basic versus advanced implementation

Google documents two ways to implement consent mode, and they differ in what happens before a choice and after a refusal.

  • Basic: Google tags do not load until the visitor interacts with the banner. A visitor who declines sends nothing at all.
  • Advanced: Google tags load with the defaults set to denied. Before a choice, and after a refusal, they send cookieless pings that carry the consent state and basic information about the request but no identifying cookies.

The choice between them is as much a policy decision as a measurement one. Some organisations will not allow any request before consent; others accept the pings as Google describes them. Either way it should be made knowingly, and recorded, rather than inherited from a consent platform's template. Server-side setups do not change the decision: the server-side tagging basics explain that the banner and consent mode still run in the browser, where the visitor makes the choice.

Modelled conversions and how to read them

The reason many teams choose the advanced implementation is modelling. Google uses the cookieless pings, alongside data from consenting visitors, to estimate behaviour and conversions it could not observe, subject to eligibility conditions it documents. Modelled conversions appear inside the ordinary conversion columns; they are estimates, not counted events.

That has two consequences for anyone reading reports. A change to consent mode shows up as a change in reported conversions with no change in what customers did, so the date of every switch belongs in an annotation. And platform figures that include modelling will not match an analytics tool that excludes it; the guide to platform and analytics discrepancies lists consent among the documented causes. At the governance level, the tag governance guide treats consent gating as a control that every tag in the inventory must pass, and the Google Analytics setup checklist asks for the consent behaviour to be configured and confirmed in the container.

Illustrative example — not a real result

Conversions that fell when the banner arrived

Abbotsleigh Knitwear added a consent banner in October, using its consent platform's default setup, which blocked Google tags until a visitor accepted. Over the next month the shop's analytics recorded 410 purchases, against 640 orders in its e-commerce platform; about 62% of visitors accepted the banner. After a review with its privacy adviser, the shop moved to the advanced implementation, with defaults denied and cookieless pings before and after a refusal. Once Google's modelling became available for the property, Google Ads reported 590 conversions for a month in which the shop recorded 620 orders. The shop's monthly report now shows observed and modelled conversions on separate lines, with the date of the change marked.

A CMP shows the banner, stores the choice and issues the consent mode updates. GTM is where most sites set the defaults and make non-Google tags respect the same states. GA4 adjusts its cookies to the analytics state and, where eligible, fills gaps with modelled behaviour. Enhanced Conversions improves matching for consented conversions and depends on the advertising data state being granted; modelling estimates the unconsented ones, so the two address different gaps.

Common confusions

  • Consent mode collects consent. The banner does; consent mode relays the result.
  • Advanced mode tracks people who declined. It sends pings without identifying cookies; it does not set cookies for them.
  • Modelled conversions are tracked conversions. They are estimates and should be reported as such.
  • It makes a site compliant. Compliance depends on the banner, the policy and the law, not on the tags.
  • It covers every vendor's tags. It governs Google's tags; others need gating in the tag manager.

More terms to look up

Where this term is used

Sources

  1. Consent mode — Google Tag Platform

Related