Google Consent Mode v2 Explained (And Why You Need It)

Q: Does Consent Mode v2 affect Google Analytics 4 as well as Google Ads?

Yes. The analytics_storage signal controls whether GA4 writes measurement cookies. In advanced mode with analytics_storage denied, GA4 still receives a cookieless event ping, which contributes to Google's behavioral modeling for analytics. In basic mode with analytics_storage denied, GA4 does not fire at all and you have a complete data gap for that user.

TL;DR

Consent Mode v2 tells Google tags how to behave when a user accepts or declines your cookie banner.
Google made it required for EEA traffic in March 2024. US sites that run any Google tag are not exempt from the technical need.
There are four consent signals: analytics_storage, ad_storage, ad_user_data, and ad_personalization. The last two are new in v2.
Basic mode blocks tags until consent. Advanced mode fires cookieless pings even on decline, feeding conversion modeling.
A misconfigured default state silently kills your data. Most sites have it wrong.
Setup runs through your CMP and GTM. Getting the order of operations right is everything.

Google Consent Mode v2 adjusts how Google tags fire based on user consent signals, so you can stay compliant with privacy regulations and still recover measurement data through conversion modeling.

Before Consent Mode existed, you had two options when a user declined cookies: fire the tags anyway (a compliance risk) or block them entirely (a measurement gap). Neither was good. Consent Mode is Google's answer to that problem.

Here is the short version of how it works. When a user lands on your site, your consent management platform (CMP) presents a banner. The user makes a choice. That choice gets pushed into the dataLayer as a set of consent signals. Google Tag Manager reads those signals and decides how each Google tag should behave. Tags either fire fully, fire in a limited cookieless mode, or do not fire at all, depending on what the user agreed to and which mode you have deployed.

Version 2 of this system, released in late 2023, added two new signal types and tightened the requirements for anyone serving users in the European Economic Area (EEA). It also became a hard requirement from Google for continued access to certain advertising features.

Why Google Made It Required (And Why US Firms Are Not Off the Hook)

Google required Consent Mode v2 for all sites serving EEA users starting March 2024, making it a hard requirement for running Google Ads or using Google Analytics in those markets.

Google's official documentation confirms that as of March 2024, advertisers using Google Ads audience features or remarketing for EEA users must use a Google-certified CMP and implement Consent Mode v2. Sites that did not comply stopped seeing personalized ads data and audience lists for EEA traffic.

If your business is US-only and you are reading this thinking it does not apply to you, consider two things.

First, if any EEA user ever lands on your site, even organically, you are technically in scope. A US law firm running Google Ads does not need EEA traffic to run campaigns, but if international visitors arrive and your tags fire without consent infrastructure, you are exposed.

Second, and more practically, the same consent and measurement architecture that satisfies EEA requirements is the same architecture that makes your Google Analytics 4 and Google Ads data more defensible in a world where browser-level cookie restrictions are tightening across every market. Google's own guidance on Consent Mode frames it as a forward-looking measurement infrastructure decision, not only a compliance checkbox.

Build it once. It protects your data in every market.

This is where most explainers get thin. The four signals do different things, and misunderstanding them leads to misconfigured setups.

`analytics_storage`

Controls whether cookies used for analytics measurement are stored. When denied, Google Analytics 4 does not write a measurement cookie but can still receive a cookieless event ping if you are in advanced mode.

`ad_storage`

Controls whether cookies used for ad measurement and remarketing are stored. This includes the Google Ads conversion cookie. When denied, no conversion cookie is written, but a cookieless ping can still reach Google Ads in advanced mode.

`ad_user_data` (new in v2)

Consent Mode v2 introduced two new consent signal types, ad_user_data and ad_personalization, which give advertisers granular control over whether user data is used for ad targeting and personalization.

Controls whether user data collected on your site is sent to Google for ad purposes. Think of it as the signal that governs whether Google can use this user's behavioral data to improve your ad targeting. Denying this signal means Google does not receive the user-level data for ad matching, even if ad_storage is granted.

`ad_personalization`

Controls whether data can be used to personalize ads for this user, which includes remarketing audiences and similar audience features. A user can grant ad_storage but deny ad_personalization, which means Google can measure the conversion but cannot use that user's data to build or seed a remarketing list.

These four signals give you, and the user, real granularity. A cookie banner that only asks about analytics vs. advertising is no longer enough. Your CMP needs to map its consent categories to all four of these signals correctly.

Basic Mode vs. Advanced Mode: The Real Tradeoff

This is the decision with the biggest downstream impact on your measurement.

Basic Mode

Basic mode blocks all Google tags from firing until consent is granted, which is simpler but means you lose all modeling data from users who decline.

In basic mode, no Google tag fires at all until the user grants consent. If the user dismisses the banner, clicks "reject all," or ignores it, your GA4 tag and Google Ads tag do not fire. Zero data is collected. Zero pings are sent.

This is the simplest implementation. It is also the most data-destructive. In markets where decline rates are high, you are flying blind on a meaningful portion of your traffic. You get no conversion modeling, no behavioral signals, nothing.

Basic mode is appropriate when your legal team has determined that any data collection before consent is impermissible in your specific context. Outside of that mandate, it creates measurement gaps you can avoid.

Advanced Mode

In advanced mode, Google tags still fire when a user declines, but they send cookieless pings that feed conversion modeling rather than storing individual user data.

In advanced mode, Google tags fire even when a user has not consented or has declined. But they fire in a limited state. No cookies are written. No user-identifiable data is stored. What does get sent is a cookieless ping, a minimal signal that tells Google something happened on this page, without linking it to an individual.

Google's conversion modeling then uses these aggregate pings, along with patterns from consented users, to statistically estimate the conversions that happened among non-consenting users. This recovered data flows back into your Google Ads reporting and Smart Bidding under the "modeled conversions" label.

The tradeoff is implementation complexity. Advanced mode requires that your tags be on the page and ready to fire before the user interacts with the banner, which means your tag firing order and default consent state setup have to be exactly right.

For most advertisers running performance campaigns, advanced mode is the correct choice. The modeling is not perfect, but it is substantially better than a zero-data gap.

How Conversion Modeling Recovers Lost Conversions

When a user converts without granting consent, you would normally lose that conversion entirely. Conversion modeling is how Google partially recovers it.

The mechanism works like this. Google observes patterns across all users where consent was granted: what paths they took, what devices they used, what time of day, what the lag was between click and conversion. When a non-consenting user completes a similar path, Google uses those patterns to infer that a conversion likely occurred and assigns a statistical weight to it.

Google documents this behavior as part of its measurement and modeling approach. Modeled conversions appear in your Google Ads account under the same conversion columns as observed conversions, and they feed into Smart Bidding signals.

Two important caveats. First, modeling is only possible in advanced mode. If you are on basic mode, those cookieless pings never happen, so there is no signal to model from. Second, modeling accuracy improves with volume. A small-traffic site will see less reliable modeling than a high-traffic one because there are fewer consented-user patterns to learn from.

For RGDM clients running Google Ads at meaningful spend levels, this is not a theoretical benefit. It is the difference between your tCPA (target cost per acquisition) bidding algorithm having enough signal to optimize versus going into a learning reset every time consent rates fluctuate.

The technical pipeline runs in this order, and the order matters.

Your CMP loads first. On page load, before your analytics or ad tags fire, the CMP checks whether this user has a stored consent preference. If they do, it pushes the consent state immediately. If they do not, it presents the banner.

That consent state gets pushed to the GTM dataLayer as a gtag('consent', 'default', {...}) or gtag('consent', 'update', {...}) call. GTM reads those signals before deciding whether to fire the tags associated with each consent type.
Consent Mode connects to your consent management platform via a dataLayer push, and Google Tag Manager reads those signals before deciding whether to fire each tag.

If you are using a Google-certified CMP, most of this is handled by the CMP's GTM template. The CMP publishes a GTM tag template that manages the dataLayer push automatically. You configure your consent categories inside the CMP, map them to the four Google signals, and publish.

If you are using a custom cookie banner or a non-certified CMP, you are writing those dataLayer pushes manually, which is where implementation errors concentrate.

The key technical requirement for advanced mode is that the consent default call must fire before any Google tags fire. In GTM, this means your Consent Initialization trigger, not the standard Page View trigger, is what the CMP tag fires on. If you get this wrong, the tags have already fired before the consent state is set, and you are effectively running without consent infrastructure.

Setup Overview and the Mistakes That Silently Break Tracking

You do not need a step-by-step walkthrough here (that belongs in a setup guide), but you do need to understand the failure modes, because most of the sites we audit have at least one of them.

Mistake 1: Hardcoding the default state to "granted."

Some implementations set analytics_storage: 'granted' and ad_storage: 'granted' as the default before the banner fires. This means every user is treated as consented until they explicitly decline. In the EEA, this is legally backwards and voids the purpose of the consent infrastructure entirely. The correct default for EEA users is 'denied' for all four signals.

Mistake 2: Pushing the consent update after the tag fires.

If your page load sequence fires the GA4 tag before the CMP has pushed the consent update, the tag has already run without consent context. GTM's Consent Initialization trigger exists specifically to prevent this. Use it.

Mistake 3: Not mapping all four signals.

Many older CMP configurations were built for v1, which only had two signals. If you updated your Google tags to v2 but your CMP template is still only setting analytics_storage and ad_storage, the ad_user_data and ad_personalization signals are undefined, which Google treats as denied by default. Your remarketing audiences stop building. This is one of the most common silent failures we find in audits.

Mistake 4: Not testing with a non-EEA geo override.

Because many CMP setups only show the consent banner to EEA users, US-based developers never see the banner during testing and assume setup is working correctly. Use GTM's preview mode combined with a location test to verify the full consent flow for EEA visitors.

If you want your tracking audited against these failure modes, our tracking and automation service is where we start with every new client. A broken consent setup does not throw errors. It just quietly drains your bidding algorithm of the signal it needs to perform.

Frequently Asked Questions

What is Google Consent Mode v2?

Google Consent Mode v2 is a framework that tells Google tags how to behave based on the consent choices a user makes on your cookie banner. It uses four consent signals, analytics_storage, ad_storage, ad_user_data, and ad_personalization, to control whether cookies are stored, whether user data is sent to Google for ad purposes, and whether that data can be used for ad personalization. Version 2 added the ad_user_data and ad_personalization signals, which were not present in version 1.

Is Consent Mode v2 mandatory?

For sites serving users in the European Economic Area that use Google Ads audience features or remarketing, yes. Google made Consent Mode v2 a hard requirement starting March 2024. Sites that did not comply lost access to personalized ad features for EEA traffic. For US-only sites with no EEA visitors, there is no regulatory mandate from Google, but the same architecture improves measurement quality across all markets as browser-level cookie restrictions tighten.

What is the difference between basic and advanced consent mode?

In basic mode, all Google tags are blocked from firing until the user grants consent. No data is collected from non-consenting users, including no cookieless pings, so conversion modeling is not possible for those users. In advanced mode, Google tags fire even when a user has not consented, but they run in a cookieless state that sends minimal pings without writing cookies or storing user data. Those pings feed Google's conversion modeling, which statistically recovers a portion of the conversions from non-consenting users.

How do I implement Consent Mode v2?

Implementation runs through three components: a consent management platform (CMP), Google Tag Manager, and your Google tags. The CMP presents the banner and captures user choices. It then pushes those choices to the GTM dataLayer as consent signal updates. GTM reads those signals before firing your GA4 and Google Ads tags. For advanced mode, the critical requirement is that the default consent state must be set before any Google tags fire, which means using GTM's Consent Initialization trigger for your CMP tag. Most Google-certified CMPs provide a GTM template that handles the dataLayer push automatically. If you are starting from scratch, book a strategy call and we will walk through your current setup.

Does Consent Mode v2 affect Google Analytics 4 as well as Google Ads?

Yes. The analytics_storage signal controls whether GA4 writes measurement cookies. In advanced mode with analytics_storage denied, GA4 still receives a cookieless event ping, which contributes to Google's behavioral modeling for analytics. In basic mode with analytics_storage denied, GA4 does not fire at all and you have a complete data gap for that user.

Will conversion modeling make up for all the data I lose from non-consenting users?

No. Conversion modeling recovers a portion of the gap, not all of it. The accuracy of modeling depends on the volume of consented traffic available as a reference population. A site with low overall traffic will see less reliable modeling than a high-volume site. Advanced mode gives the modeling system the cookieless pings it needs to work. Without those pings, which is what happens in basic mode, modeling has no signal to work from at all.

How do I know if my Consent Mode setup is broken?

The most reliable audit method is to open GTM's preview mode, simulate a user declining consent, and then check your GA4 DebugView and Google Ads conversion tags to confirm they are either not firing (basic mode) or firing in a cookieless state (advanced mode). A common sign of a broken setup is that your GA4 real-time report still shows 100% of visitors even from regions where high banner-decline rates are expected. Another sign is that your Google Ads audience lists stop growing after you deploy a CMP. Both can indicate that consent signals are not being applied correctly.

Consent Mode v2 is not a checkbox. It is infrastructure. Get it wrong and your bidding algorithms are running on incomplete data, your audience lists are not building, and you have no visibility into how much of your conversion volume you are actually losing.

If you want your current setup audited against the failure modes above, start here.