Consent Mode v2 for Google Ads: Setup, Modeling, and What Happens to Conversions Without It

CH.01Choose Basic vs Advanced mode before you touch any code

This is the fork that decides everything downstream, and it is made before you write a single line of configuration. The two modes differ in when Google tags are allowed to load and what they are permitted to send while consent is still denied.

In Basic consent mode, Google tags are blocked from loading until the user interacts with the consent banner, and no data, not even consent status, is sent before consent. Basic only qualifies for a general, less-detailed conversion model. In Advanced consent mode, tags load with defaults set to denied, send cookieless pings when consent is denied, and qualify for an advertiser-specific, more detailed model. That advertiser-specific model is the better recovery engine, which is why Advanced is the right default for almost every account that depends on Google Ads measurement.

How the four signals split into two jobs

Consent Mode v2 sends four signals, and they are not interchangeable. ad_storage enables advertising-related storage such as cookies. analytics_storage enables analytics-related storage. ad_user_data is consent to send user data to Google for advertising, and ad_personalization is consent for personalized advertising and remarketing. The latter two were added in November 2023, which is what made it v2.

CH.02Install a Google-certified CMP and wire the banner

For EEA, UK, and Switzerland traffic, Google requires advertisers to collect end-user consent and pass the ad_user_data and ad_personalization signals to continue using measurement, personalization, and remarketing. Advertisers using a consent banner should use a Google-certified consent management platform. This requirement was tied to the compliance deadline in March 2024.

A certified CMP earns its place by automating the parts that break silently when hand-rolled. It versions the consent signals, maps the user's banner choice to the four flags, and keeps the integration current as Google revises the spec. Building this yourself is possible, but the maintenance surface is exactly where small accounts lose data without noticing.

• Pick a CMP from Google's certified list rather than a generic cookie banner plugin.
• Confirm it explicitly supports all four Consent Mode v2 signals, not just the original two.
• Check that it can scope defaults by region so non-EEA traffic is not over-restricted.

CH.03Set the default consent state to denied before any tags fire

Ordering is the whole game here. The default consent command must fire before any tags, so that nothing is sent under an assumed grant. In practice that means a gtag('consent', 'default', {...}) call with every signal set to denied, placed ahead of your Google tag and your CMP's update logic.

Pair the default with a wait_for_update value, commonly 500ms, which gives the CMP time to update consent before tags fire. Without it, tags can race ahead of the user's actual choice. Scope your defaults by region so EEA visitors get denied-by-default while you apply the appropriate state elsewhere.

CH.04Fire the update command on the user's choice

Once the visitor interacts with the banner, the CMP fires a gtag('consent', 'update', {...}) command that maps their choice onto the four signals. Granting marketing consent flips ad_storage, ad_user_data, and ad_personalization to granted; granting analytics flips analytics_storage. Denial leaves the relevant flags at denied.

The non-obvious requirement is timing relative to navigation. The update must be tracked on the page where the choice occurs, before any navigation away from it. If the user consents and immediately clicks through before the update propagates, that interaction is recorded under the denied default, and you have lost a signal you were entitled to keep.

1. Map CMP events to signalsWire each banner outcome (accept all, reject all, granular choices) to the exact set of consent flags it should set.
2. Fire update before navigationEnsure the update command runs on the same page as the choice, ahead of any redirect or route change.
3. Re-fire on consent changeIf a user revisits the banner and changes their mind, the update must run again so the new state is honored.

CH.05Turn on the recovery stack: Advanced mode, enhanced conversions, and ads_data_redaction

Setup keeps you compliant. The recovery stack is what wins back data after consent is denied. It has three parts that work together: Advanced mode and its cookieless pings, enhanced conversions, and ads_data_redaction with url_passthrough.

Enhanced conversions is the first-party-data bridge, but it is gated by consent in a way many managers miss. For EEA traffic, enhanced conversions data is only used for matching when both ad_storage and ad_user_data are granted. Without ad_user_data, hashed first-party data such as a SHA-256 email is not used for matching even if ad_storage is granted. That is why ad_user_data is the load-bearing signal for recovery, not just a compliance checkbox. If you want the deeper rationale for why first-party data is the foundation here, see our breakdown at first-party data in PPC.

Stack these correctly and you get cookieless pings from Advanced mode, consented hashed matches from enhanced conversions, and redaction that keeps you compliant when ad_storage is denied. None of these restore observation directly, but together they give the model the most material it can possibly work with. Before any of this matters, your underlying conversion tracking has to be correct, which we cover in how to set up conversion tracking correctly in Google Ads.

CH.06Validate signals are flowing and clear the modeling threshold

A setup that looks right in code can still fail in practice. Validation is two jobs: confirm the four signals actually fire in the right order, then confirm your account has enough volume for modeling to ever activate.

QA the signals

• Use Tag Assistant or your GTM preview to watch all four consent signals fire, and confirm the default fires before the Google tag.
• Toggle the banner to denied and verify cookieless pings still send under Advanced mode.
• Toggle to granted and verify the update command flips the correct flags on the same page.
• Check the consent diagnostics inside Google Ads for warnings about missing or malformed signals.

The threshold reality check

Consent mode conversion modeling requires a threshold of 700 ad clicks over a 7-day period, per country and domain grouping. Once met, models enter a training period before modeled conversions appear in reporting, and modeling can deactivate if traffic or consent rates fall below the threshold. The hard part is the per-country, per-domain math: a multi-market account that looks large in aggregate can still fail the bar in each individual EEA country.

CH.07What happens to your conversions without Consent Mode v2

For EEA, UK, and Switzerland traffic, skipping Consent Mode v2 is not a soft penalty. Without the ad_user_data and ad_personalization signals, Google cannot continue to use measurement, personalization, and remarketing for that traffic. The concrete losses compound across the account.

• Conversion tracking stops attributing unconsented EEA conversions, so reported conversions fall.
• Remarketing audiences stop populating from that traffic, shrinking your retargeting pools.
• Enhanced conversions cannot match, because ad_user_data is the signal that authorizes hashed first-party matching.
• Demographic and personalization reporting degrades for the affected traffic.

Here is the precise framing that matters for client conversations: Consent Mode does not restore lost conversions. Unconsented direct observation is permanently lost. What modeling does is estimate those conversions, and modeled conversions are estimates, not recovered observations. That distinction is the whole reporting story, and presenting modeled versus observed conversions cleanly to a client is its own discipline, covered in PPC reporting for clients.

The accounts that suffer most are the ones that installed a banner, called it done, and never checked whether modeling activated. Compliance and measurement are two separate jobs. Capconvert Paid Media playbook

There is a downstream cost beyond reporting. Modeled and lost conversions feed your automated bidding, and a consent-driven data gap degrades that signal quality. If Smart Bidding is learning from a thinner, partially modeled conversion stream, its decisions get worse, which is why this connects directly to Smart Bidding and to signal-hungry campaign types covered in Performance Max in 2026.

CH.08The 2026 change every advertiser needs on their radar

Keep one window on your roadmap. Google has signaled a change expected in 2026 that moves Google Analytics toward Consent Mode and the ad_storage signal as the single control governing Google Ads data sharing, rather than treating a separate lever as an independent control. A specific June 2026 date has circulated in third-party reporting, but we have not been able to confirm it on a Google page, so treat it as unverified. We are flagging the change so you re-check your configuration ahead of it; confirm the precise date and scope against Google's official announcement before you act on it.

The practical implication, if it lands as described, is that your Consent Mode implementation becomes even more load-bearing. A single control over data sharing means a misconfigured ad_storage default does more damage, because there is no secondary lever quietly compensating. The accounts that wired up Advanced mode cleanly will absorb the change without drama. The ones running a half-configured banner will feel it.