Consent Mode v2 for Google Ads: what breaks without it

Without Consent Mode v2 signals, Google Ads stops receiving usable conversion and audience data from EEA and UK users — remarketing lists stop filling, conversion counts drop, and Smart Bidding loses the signal it needs in those markets. The two signals that matter are ad_user_data and ad_personalization, and they are precisely the ones missing from implementations built before 2024 that nobody has revisited.

What breaks without v2

Google requires the v2 signals for personalised advertising features in the EEA and UK. Without them:

• Remarketing audiences stop growing in those markets. Existing lists decay, new users are not added, and campaigns targeting them quietly starve.
• Conversion measurement degrades. Conversions from non-signalled users are not counted and, critically, not modelled either.
• Customer Match and similar features are restricted.
• Smart Bidding loses signal, so performance in those markets deteriorates in a way that looks like a market problem rather than a tagging one.

The last point is why this matters commercially: the failure presents as poor European performance, and the diagnosis usually lands on the media plan rather than on four missing parameters.

The four signals

Signal	Governs
ad_storage	Advertising cookies and identifiers
analytics_storage	Analytics cookies
ad_user_data	Sending user data to Google for advertising (v2)
ad_personalization	Personalised advertising and remarketing (v2)

An implementation setting only the first two passes casual inspection — the banner works, cookies behave, GA4 looks fine — and still degrades Google Ads for EEA traffic. This combination is extremely common.

Implementing it

The default must run before any Google tag, in the head:

<script>
  window.dataLayer = window.dataLayer || [];
  function gtag(){dataLayer.push(arguments);}

  gtag('consent', 'default', {
    ad_storage: 'denied',
    analytics_storage: 'denied',
    ad_user_data: 'denied',
    ad_personalization: 'denied',
    wait_for_update: 500
  });
</script>

And on the user's choice:

gtag('consent', 'update', {
  ad_storage: 'granted',
  analytics_storage: 'granted',
  ad_user_data: 'granted',
  ad_personalization: 'granted'
});

Three implementation details decide whether it works:

Ordering. If the default runs after your container, tags fire unrestricted in the gap. This is the most common technical failure.

wait_for_update. Gives your consent platform time to restore a stored choice before tags act on the default. Too short and returning acceptors are treated as new non-consenters on every first page load.

Region targeting. You can apply denied defaults to EEA and UK regions specifically while granting elsewhere. Worth doing deliberately rather than applying blanket global denial, which costs you data in markets that do not require it.

Basic versus Advanced, from an Ads perspective

The choice materially affects Google Ads results.

Basic blocks tags entirely until consent. Google receives nothing from non-consenting users, so no conversion modelling is possible — those conversions are simply absent.

Advanced loads tags in a restricted state, sending cookieless pings. Google can then model the conversions it cannot observe directly, typically recovering a meaningful share.

For advertisers, Advanced is usually the right choice provided your legal position permits it. Basic vs Advanced covers the trade-off in full, including the privacy considerations that sometimes point the other way.

Verifying it from the Ads side

The browser checks — gcs=G100 before consent, G111 after — confirm what leaves the page. Two platform checks confirm what Google actually received:

1. Google Ads diagnostics. Conversion actions display warnings when v2 signals are missing for EEA traffic. This is the most reliable single indicator that ad_user_data and ad_personalization are absent.
2. Audience sizes by region. EEA audiences smaller than non-EEA is expected. EEA audiences at or near zero, while traffic clearly exists, means signals are not arriving.

If diagnostics are clean and audiences are filling, the implementation is working. If either is wrong, the browser-level debugging steps will find the cause.

What to do about the data you already lost

If the v2 signals have been missing for months, the conversions from that period are gone — Google cannot retroactively model data it never received. But two recoveries are worth making.

Rebuild the audiences. Remarketing lists that stopped filling need time to repopulate once signals start arriving. Expect weeks before EEA audiences reach usable size again, and do not judge campaign performance in those markets until they have.

Re-baseline your targets. Any EEA cost-per-acquisition or ROAS target set during the broken period was calculated against undercounted conversions, so it was too pessimistic. Once signals flow, measured conversions rise and the same real performance now looks better. Reset the targets rather than reading the improvement as a campaign win.

Annotate the fix date in your reporting. A step change in EEA conversion volume that nobody documented gets attributed to whatever else happened that week, usually incorrectly.

The two failure directions

Tags firing before consent — a compliance exposure, and invisible because the data looks complete.

Consent never reaching Google — silent loss of all EEA advertising data, misdiagnosed as market performance.

Test both. Testing only the accept path is how sites end up firing before consent; testing only the deny path is how they end up with permanently denied tags.

FAQ

What happens if I do not implement Consent Mode v2?

Google restricts personalised advertising features for EEA and UK users. Remarketing lists stop filling, conversions are undercounted and unmodelled, and Smart Bidding performance degrades in those markets.

Which consent signals does Google Ads specifically need?

ad_user_data and ad_personalization are the v2 additions that govern advertising features, alongside ad_storage. All four should be set, but those are the ones most often missing.

Does Consent Mode v2 apply outside the EEA?

The requirement targets EEA and UK traffic. You can apply region-specific defaults so other markets are unaffected, which avoids giving up data you are not required to give up.

Will implementing Consent Mode v2 reduce my conversions?

Compared with tracking everyone regardless of consent, yes. Advanced Consent Mode plus modelling recovers a meaningful share, which is why implementation quality matters more than the decision to implement.

How do I know if my v2 signals are actually reaching Google?

Check Google Ads diagnostics for v2 warnings on your conversion actions, and confirm EEA audiences are still filling. Browser-side, check the gcs and gcd parameters on outgoing requests.

Check whether your site emits Consent Mode v2 calls at all — the free tracking audit inspects consent signals and banner presence on any URL.