Google Consent Mode v2: What It Is and Why Your WordPress Site Needs It

6 min read Updated July 2026

If you run Google Analytics or Google Ads on a WordPress site with European visitors, Google Consent Mode v2 isn’t optional anymore — it’s the difference between keeping your conversion data and watching it disappear. Here’s what Consent Mode v2 actually does, why Google made it mandatory, and what you gain by implementing it properly.

Looking for setup instructions instead? See our step-by-step guide: How to enable Google Consent Mode v2.

Google Consent Mode is the mechanism by which your website tells Google’s tags — Analytics, Ads, Floodlight — whether the visitor has consented to tracking. Instead of your tags simply firing or not firing, Consent Mode gives them a signal describing what the visitor allowed, and Google’s products adjust their behavior accordingly.

Version 2, which Google began enforcing for EEA and UK traffic in March 2024, added two new signals on top of the original set:

  • ad_user_data — whether user data may be sent to Google for advertising purposes
  • ad_personalization — whether the visitor’s data may be used for personalized advertising (remarketing)

These join the existing signals (ad_storage, analytics_storage, and the functionality/personalization/security storage signals) to form the complete v2 set.

Why Google made it mandatory

Under the EU’s Digital Markets Act and GDPR pressure, Google now requires valid consent signals before its advertising products will process EEA/UK user data. In practice:

  • Without ad_user_data and ad_personalization set to granted, Google Ads won’t add EEA/UK visitors to remarketing audiences, and measurement of those users is restricted.
  • Without any Consent Mode signals at all, audience lists for European traffic degrade and stop refreshing, and conversion measurement for those visitors deteriorates.

If your Google Ads audiences have been mysteriously shrinking or your EU conversions look underreported, missing or misconfigured Consent Mode v2 signals are the most common culprit.

1. You keep measuring conversions — even from visitors who decline

This is the headline benefit. When a visitor declines tracking, Google doesn’t just get silence — it receives the denied signal. Google then uses conversion modeling to statistically fill the measurement gap left by non-consenting visitors, based on the behavior of comparable consenting ones. Advertisers implementing Consent Mode typically recover a meaningful share of otherwise-lost conversion data — Google has cited recovery rates north of 60% of ad-click-to-conversion journeys that would otherwise vanish. Without Consent Mode, a declined banner means those conversions simply never existed as far as your reports are concerned.

2. Your remarketing keeps working where it’s allowed

The two v2 signals exist precisely so Google Ads knows when it may build audiences. Send them correctly and consenting EEA/UK visitors keep flowing into your remarketing lists; omit them and Google errs on the side of exclusion — for everyone. For any business running retargeting campaigns in Europe, correct v2 signals directly protect campaign reach.

A surprisingly common compliance failure: the banner says “declined,” but the gtag snippet pasted in the theme header already fired before the banner even rendered. Consent Mode’s default-denied pattern fixes the ordering problem — the denied state is declared before any Google tag can act, and it’s only upgraded after a genuine choice. That’s both the compliant behavior and the honest one.

4. You’re aligned with where Google is going

Google has steadily tightened enforcement: warnings in Google Ads and GA4 for missing signals, degraded features for non-compliant setups, and certified-CMP requirements for ad-serving publishers. Sites with a clean Consent Mode v2 implementation haven’t had to scramble at any of these deadlines — the signals were already flowing.

5. No performance or caching penalty (done right)

Consent Mode is a lightweight JavaScript convention — a few gtag('consent', ...) calls. Implemented well, it adds no server round-trips and doesn’t break full-page caching, because the same HTML ships to every visitor and consent is applied in the browser.

Google supports two implementation styles. Basic consent mode holds Google tags entirely until consent, then loads them; declined visitors send nothing, and Google models conversions at a more general level. Advanced consent mode loads Google tags immediately but restricts them to cookieless “pings” while consent is denied, enabling more granular modeling — at the cost of contacting Google’s servers before the visitor has agreed to anything.

CoreConsent deliberately implements the basic pattern: the full v2 signal set defaults to denied before any tag can act, your Google tags stay held until the visitor consents, and the signals update the moment they do. For most site owners — and certainly for the privacy-first positioning that made you install a consent plugin in the first place — not contacting ad servers before consent is the right default.

How CoreConsent handles it

Consent Mode v2 support is built into CoreConsent — including the free version:

  • The complete v2 signal set (all seven signals, including ad_user_data and ad_personalization) is declared denied by default, before any Google tag can load.
  • When the visitor makes a choice, the signals update instantly to match — analytics and advertising signals map to the consent categories you’ve configured.
  • It’s caching-friendly: the consent logic runs in the browser, so your pages keep caching normally.

Setup takes a few minutes: enable Google Consent Mode v2 in CoreConsent →

Frequently asked questions

Do I need Consent Mode v2 if I only use Google Analytics, not Ads? If you have EEA/UK visitors, yes — analytics_storage governs GA4’s cookie behavior, and Google’s enforcement covers analytics measurement too. You can leave the ads-related services unconfigured, but the signal framework should be in place.

Does Consent Mode v2 replace my cookie banner? No — it’s the opposite of a replacement. The banner collects the choice; Consent Mode is how that choice is communicated to Google. You need both, working together.

Is Consent Mode v2 the same as being a “certified CMP”? No. Consent Mode v2 is a free technical integration any site can implement. Google’s certified-CMP requirement applies specifically to sites serving Google ads (AdSense, Ad Manager, AdMob) to EEA/UK visitors. For analytics and conversion tracking, Consent Mode v2 is the requirement — and CoreConsent supports it fully.

Will I lose data for visitors who decline? You’ll collect no observed data from them — that’s the point of their choice — but Google’s conversion modeling estimates the aggregate picture, so your reporting reflects reality far better than with no Consent Mode at all.

Was this article helpful?
Thanks for your feedback!

Related articles

Make your Google tag wait for consent Enable Google Consent Mode v2