Consent Mode
Also known as: Google Consent Mode
A Google framework that adjusts how tags behave based on a user's consent choices for analytics and advertising cookies. When consent is denied, tags send anonymized, cookieless signals instead of full data, letting Google model conversions while respecting privacy preferences captured by your cookie banner.
Key Takeaways
- Consent Mode is a Google framework that adjusts how tags behave based on a user's consent choices.
- It reads consent states for analytics and advertising storage and changes tag behavior accordingly.
- When consent is denied, tags send anonymized, cookieless signals instead of collecting full data.
- Google can use those signals to model conversions that would otherwise be lost when users decline cookies.
- Consent Mode only works if your cookie banner actually passes consent signals into your tag platform.
How It Works
Consent Mode sits between your cookie banner and your Google tags. It defines consent states, such as analytics storage and ad storage, and each tag checks those states before deciding how to fire. If a user grants consent, tags operate normally; if they decline, tags switch to a restricted, cookieless mode.
In that restricted mode, tags still send anonymized pings without reading or writing identifying cookies. Google can then use modeling to estimate conversions from the users who declined, preserving measurement continuity that would otherwise vanish. This modeled data helps keep smart bidding and audiences from starving when consent rates are low.
The wiring matters. Consent Mode is commonly deployed through Google Tag Manager, and its signals should align with your broader Cookieless Tracking strategy and First-Party Data collection. Related features like Enhanced Conversions can complement it by using consented, hashed customer data to recover measurement.
Why It Matters
In regions with strict consent laws, Consent Mode preserves measurement continuity when users decline cookies. Without it, denied consent means lost conversions and broken audiences, which starves smart bidding of the data it needs to optimize.
Example
A European ecommerce store shows a cookie banner. When a visitor declines analytics and ad cookies, Consent Mode keeps tags from writing cookies but still sends anonymized signals. Google models the likely conversions from those declined sessions, so the store's reporting and bidding do not go dark for the large share of users who opt out.
Common Mistake
Installing a cookie banner but never wiring its consent signals into Consent Mode, so tags either block entirely or ignore consent. The banner and your tag platform must actually communicate consent states.
Frequently Asked Questions
What does Consent Mode do?
It adjusts how Google tags behave based on a user's consent choices. When consent is granted, tags collect data normally. When denied, tags send anonymized, cookieless signals so Google can model conversions while respecting the user's privacy preferences.
Do I still need a cookie banner with Consent Mode?
Yes. Consent Mode does not collect consent by itself. You still need a consent banner or platform to capture user choices, and it must pass those signals into Consent Mode so your tags respond correctly.
Does Consent Mode make me compliant with privacy laws?
Not on its own. Consent Mode is a technical framework for honoring consent signals, but compliance depends on your banner, disclosures, and how consent is collected. Treat it as one tool within a broader legal and privacy setup.
What is the difference between the basic and advanced setup?
In basic Consent Mode, tags do not fire at all until consent is granted. In advanced, tags load in a restricted cookieless state and send anonymized signals even before consent, which allows Google to model more of the declined traffic.