linkutm Logo
Glossary Term

Consent Mode

glossary consent mode featured

Consent Mode is a Google framework that adjusts how Google tags behave based on a user’s cookie consent choices. It lets tools like Google Analytics 4 and Google Ads respect a visitor’s decision to accept or reject tracking, without breaking measurement entirely. Google introduced it in 2020 and released Consent Mode v2 in late 2023.

Why Consent Mode Matters

Consent Mode keeps measurement working when users reject cookies. Without it, a rejected cookie banner means Google tags either fire illegally or not at all. Consent Mode gives a third option: the tags load, read the user’s choice, and adjust what they collect.

For advertisers, it is not optional. Since March 2024, Google requires Consent Mode v2 for anyone using Google Ads audiences, remarketing, or personalized ads with traffic from the European Economic Area and the UK. Accounts without it lose access to remarketing lists and see reduced conversion data.

The framework also recovers lost data through conversion modeling. When users decline cookies, Google uses machine learning to estimate the conversions that tracking would have captured. This fills the gap that a cookie consent rejection would otherwise leave in reporting.

The Four Consent Signals

Consent Mode controls tag behavior through four consent parameters. Each is set to granted or denied based on the user’s choice:

  • ad_storage controls cookies used for advertising, such as conversion and remarketing tags.
  • analytics_storage controls cookies used for analytics, such as GA4 measurement.
  • ad_user_data controls whether user data can be sent to Google for advertising. Added in v2.
  • ad_personalization controls whether data can be used for personalized ads and remarketing. Added in v2.

The two v2 signals are what separate Consent Mode v2 from the original. They exist to satisfy the EU Digital Markets Act, which requires explicit permission before Google uses data for ad personalization.

Basic vs Advanced Consent Mode

Consent Mode has two implementation types, and the choice affects how much data you recover.

Basic Consent Mode blocks Google tags completely until the user consents. No pings are sent before a choice is made. If a user declines, Google receives nothing, and conversion modeling is limited.

Advanced Consent Mode loads Google tags immediately. Before consent, tags send anonymized, cookieless pings that carry no identifiers. If the user declines, these pings still feed conversion modeling, so you recover more data. If the user accepts, full tracking resumes.

Advanced mode collects more, but it loads tags before consent, so many teams pair it with careful legal review. Denied users still get no cookies in either mode.

How Consent Mode Works

Consent Mode runs on two gtag commands: a default state and an update. The sequence is:

  1. The page loads. A consent default command sets every signal to denied before any tag fires.
  2. The cookie banner appears. The user accepts or rejects categories.
  3. A consent update command pushes the new state to Google tags.
  4. Tags read the state. Granted signals allow cookies; denied signals switch to cookieless pings or stay blocked.

A default consent state in gtag.js looks like this:

How to Set Up Consent Mode

Most sites set up Consent Mode through a certified Consent Management Platform rather than hand-coding it. The common paths are:

  • Certified CMP. Tools like Cookiebot, OneTrust, and Usercentrics integrate with Consent Mode and push the update signals automatically.
  • Google Tag Manager. GTM has built-in consent settings. Configure a consent initialization trigger and map your CMP to the four signals.
  • gtag.js. Add the default and update commands manually. This suits simple sites without a tag manager.

Consent Mode is not a consent banner. It reacts to consent but does not collect it, so you still need a CMP or banner to capture the user’s choice. Verify the setup in Google Tag Assistant, which shows each signal’s state as you accept or reject.

Consent Mode and Campaign Tracking

Consent Mode handles cookie-based signals, but URL-based tracking works regardless of consent. UTM parameters live in the link, not a cookie, so they identify the source campaign even when a user denies every consent signal.

That makes UTM tagging a durable complement to modeled data. Google Consent Mode estimates the conversions you lose to rejections, while UTM tags keep raw channel attribution intact in your reports.

Frequently Asked Questions

What is Google Consent Mode?

Google Consent Mode is a framework that adjusts how Google tags behave based on a user’s cookie consent choices. It lets GA4 and Google Ads respect a rejection without stopping measurement completely. When users decline, tags switch to anonymized signals and Google models the missing conversions.

What is the difference between Consent Mode and Consent Mode v2?

Consent Mode v2 adds two signals the original lacked: ad_user_data and ad_personalization. These control whether user data goes to Google for advertising and personalized ads. Google made v2 mandatory in March 2024 for EEA and UK advertisers using audiences or remarketing.

Is Consent Mode the same as a cookie banner?

No. A cookie banner or CMP collects the user’s consent. Consent Mode reacts to that choice by adjusting tag behavior. You need both: a banner to capture consent and Consent Mode to enforce it in Google tags.

Do I need Consent Mode if I do not target the EU?

Consent Mode v2 is only required for advertisers serving EEA and UK traffic through Google Ads audiences. Sites with no European visitors are not obligated to use it. Many implement it anyway to standardize privacy handling across all regions.

To keep campaign attribution accurate even when visitors reject cookies, tag your links with UTM parameters.

Back to Glossary