What Is Consent Mode? Google's Privacy Framework Explained

Consent Mode lets Google tags adjust their behavior based on whether users accept cookies. Here's what it does, why you need it, and how it affects your data.

consent modeprivacyGDPRcookiesGoogle AdsGA4beginner

Privacy laws require websites to ask users for permission before tracking them with cookies. You’ve seen the banners — “Accept all cookies” or “Reject non-essential cookies.” But what happens to your Google Analytics and Google Ads data when someone clicks “Reject”?

That’s where Consent Mode comes in.

Consent Mode is a Google framework that tells your Google tags (GA4, Google Ads, Floodlight) whether the user has given consent, so the tags can adjust their behavior accordingly.

When a user accepts cookies, your tags work normally. When a user rejects cookies, your tags switch to a restricted mode that doesn’t store cookies or collect personal identifiers — but still sends limited, anonymized pings to Google so your data isn’t completely lost.

Why It Exists

Two converging forces created Consent Mode:

Privacy laws. GDPR (Europe), CCPA (California), and similar laws require user consent before setting tracking cookies. If you track users who said “no,” you face fines.

Data loss. When cookie consent banners first appeared, users who rejected cookies simply disappeared from analytics. Some websites saw 30-50% of their traffic vanish from GA4 reports. Advertisers lost visibility into conversions, ROAS dropped, and ad platforms couldn’t optimize properly.

Consent Mode solves both problems. It respects the user’s choice while recovering some of the data that would otherwise be lost.

How It Works

Consent Mode operates through two consent states:

Consent TypeWhat It ControlsWhen It Matters
analytics_storageWhether GA4 can set analytics cookiesAlways (all websites using GA4)
ad_storageWhether Google Ads/Floodlight can set ad cookiesWhen running Google Ads
ad_user_dataWhether user data can be sent to Google for advertisingRequired since March 2024
ad_personalizationWhether data can be used for ad personalization (remarketing)When using remarketing audiences

Each consent type is either granted or denied. Your cookie consent banner (OneTrust, Cookiebot, CookieYes, etc.) communicates the user’s choice to Google’s tags via Consent Mode.

Tags work normally. Cookies are set. Full data is collected. Event parameters, user properties, and identifiers all flow to GA4 and Google Ads.

Tags switch to restricted mode:

  • No cookies are set or read
  • No user identifiers are stored
  • Cookieless pings are still sent to Google — these contain limited information like timestamp, user agent, and the page URL, but no personal data
  • Google uses modeling to estimate the conversions and behavior of users who denied consent, based on the patterns of users who granted it

This modeling is the key innovation. Instead of losing 30% of your data, Google estimates what that 30% probably did based on what the consenting 70% did. The result: your GA4 reports and Google Ads conversion counts are closer to reality.

Google launched Consent Mode v1 in 2020. In March 2024, they upgraded to Consent Mode v2, which added the ad_user_data and ad_personalization signals.

The critical change: As of March 2024, Google Ads requires Consent Mode v2 for any website that targets users in the European Economic Area. Without it, you can’t build remarketing audiences, can’t use enhanced conversions, and can’t see conversion data for European traffic.

For the full implementation walkthrough, see our Consent Mode v2 implementation guide.

The Two Implementation Modes

Google tags don’t fire at all until the user makes a consent choice. If they accept, tags fire. If they reject, nothing happens. No cookieless pings, no modeling.

Pros: Simplest to implement. Maximum privacy. Cons: You lose all data from users who reject cookies. No modeling to fill the gap.

Google tags load immediately but in a restricted state. Cookieless pings are sent regardless of consent. When the user makes their choice, tags adjust accordingly.

Pros: Google can model conversions for non-consenting users. Less data loss. Cons: More complex setup. Some privacy advocates argue that even cookieless pings require consent (this is debated).

Google recommends Advanced mode because it enables the behavioral modeling that recovers lost data. Most businesses with meaningful European traffic should use Advanced mode.

GA4 Impact

With Advanced Consent Mode, GA4 uses modeling to fill gaps in your data. You’ll see a notification in reports when modeled data is included. The modeling is generally accurate for aggregate trends but less reliable for individual user paths.

Without Consent Mode: Users who reject cookies are invisible. If 40% of your European traffic rejects cookies, you’re missing 40% of that traffic in your reports.

With Advanced Consent Mode: Google models the behavior of non-consenting users. Your traffic numbers are much closer to reality, though not perfectly accurate.

The impact on Google Ads is even bigger than GA4:

  • Conversion tracking: Without Consent Mode, conversions from non-consenting users aren’t counted. Your ROAS looks artificially low.
  • Smart bidding: Google’s bidding algorithms need conversion data to optimize. Less data means worse optimization.
  • Audience building: Remarketing audiences shrink dramatically without consenting users.

With Consent Mode v2, Google models the conversions it can’t directly observe and includes them in your reporting (marked as modeled). This keeps your Smart Bidding algorithms fed with sufficient data to optimize properly.

The implementation involves two components:

You need a Consent Management Platform. These are the tools that show the cookie banner and collect the user’s choice:

  • Cookiebot — Popular, Google-certified CMP
  • OneTrust — Enterprise-grade, comprehensive
  • CookieYes — Budget-friendly, easy to set up
  • Termly — Simple and affordable
  • Osano — Privacy-focused

The CMP must support Google Consent Mode integration. Most major CMPs do.

2. Google Tag Configuration

Your Google tags (GA4, Google Ads) need to be configured to read the consent state from your CMP. This is usually done in Google Tag Manager:

  1. Set default consent states (denied for all, before the banner loads)
  2. CMP fires and shows the banner
  3. User makes their choice
  4. CMP updates the consent state via gtag('consent', 'update', {...})
  5. Google tags adjust their behavior based on the updated consent

If you’re using GTM, our cookie consent banner GTM guide has the step-by-step setup for the most popular CMPs.

Common Mistakes

If you don’t set a default consent state, Google tags assume consent is granted until told otherwise. This means tags fire fully before the banner loads — which violates GDPR if the user hasn’t consented yet.

Fix: Set all consent types to denied by default, before any Google tags fire.

Using Basic Mode When You Need Advanced

Basic mode is simpler, but it throws away data from non-consenting users entirely. If you have significant European traffic and run Google Ads, you need Advanced mode for the modeling to work.

Not Updating to v2

If you implemented Consent Mode before March 2024, you may still be running v1. Check whether your implementation includes the ad_user_data and ad_personalization consent types. Without them, Google Ads features like remarketing and enhanced conversions won’t work for European users.

Consent Mode is not a cookie banner. It’s a technical framework that connects your cookie banner to your Google tags. You still need a CMP to show the banner and collect consent.

If you target users in the EU/EEA: Yes, mandatory for Google Ads as of March 2024. Strongly recommended for GA4 to avoid data loss.

If you only target US users: Not legally required in most states, but still recommended. California’s CCPA requires opt-out capability, and other states are passing similar laws. Setting up Consent Mode now prepares you for the future.

If you don’t run Google Ads: Consent Mode still helps GA4 recover data from users who reject cookies. Less critical than for advertisers, but still valuable.

The Bottom Line

Consent Mode is Google’s answer to “how do we respect privacy while still measuring what matters.” It lets your tracking adjust based on user consent, and it uses modeling to fill in the gaps. If you run Google Ads and target any European traffic, it’s no longer optional.

The good news: once it’s set up, it works automatically. The bad news: many websites have it configured incorrectly — or not at all — and are losing conversion data they don’t even know about.

Not sure if your Consent Mode setup is working? Run a free scan and we’ll check your consent configuration along with your full tracking setup.