If you run any kind of digital advertising, Google Consent Mode V2 affects you — whether you've configured it or not. It's Google's framework for adjusting how its tags (Analytics, Ads, Tag Manager) behave based on the consent a visitor actually gives, and it's been a practical requirement for advertisers serving EEA and UK traffic since Google Consent Mode V2 became mandatory for EEA users in March 2024. Here's what it does, why it matters, and how to set it up.

What Is Google Consent Mode V2?

Consent Mode V2 is an update to Google's original Consent Mode framework that lets Google tags adjust their behavior based on two additional consent signals — ad_user_data and ad_personalization — alongside the original ad_storage and analytics_storage signals. In practice, it means:

  • Google tags respect whatever consent choice a visitor makes through your cookie banner.
  • Even when a visitor declines tracking cookies, Google can still receive aggregated, cookieless "pings" that support modeled conversions — so you're not flying completely blind on ad performance.
  • You stay eligible for Google Ads features (like remarketing audiences and conversion tracking) that would otherwise require full tracking consent.

Why It Matters

Two separate pressures make this relevant. First, regulatory: under GDPR, UK GDPR, and the ePrivacy rules that govern cookies, you need a valid legal basis — usually consent — before setting non-essential tracking cookies. Second, practical: Google has tied a growing list of ad platform features to Consent Mode being correctly implemented. If it's missing or misconfigured, you can lose access to certain remarketing and conversion-modeling features in Google Ads, on top of the compliance risk.

How to Set It Up

1. Get a consent management platform (CMP) that supports Consent Mode V2

You need a cookie banner tool that can actually fire the consent signals Google listens for — not just hide a cookie notice. Options include OneTrust, Cookiebot, Complianz, and FAZ Cookie Manager (the free, self-hosted consent tool we use here on rekla.ai, which supports Consent Mode V2 natively along with IAB TCF v2.3).

2. Map your consent categories to Google's signals

Your CMP needs to translate its own cookie categories (typically Necessary, Analytics, Marketing) into Google's four consent signals (ad_storage, analytics_storage, ad_user_data, ad_personalization). Most modern CMPs handle this mapping automatically once you connect them to Google Tag Manager or your gtag.js implementation — check your CMP's documentation for the exact integration steps.

3. Update your Google tags

Whether you're using gtag.js directly or Google Tag Manager, your tags need to be configured to check consent state before firing. If you're on Tag Manager, Google's built-in Consent Mode templates handle most of this for you once your CMP is connected.

4. Test before you trust it

Use Google Tag Assistant or GTM's preview mode to confirm tags are actually respecting consent state — that declined consent really blocks the tag, and accepted consent fires it correctly. Don't assume the integration works just because you followed the setup steps; verify it.

5. Use the conversion modeling data

Once it's running, Google Ads and Analytics will show you modeled conversions for users who didn't consent to tracking, alongside your directly-measured conversions. This won't be as precise as fully-consented data, but it's meaningfully better than losing that traffic segment from your reporting entirely.

A Few Things Worth Getting Right

  • Don't dark-pattern your banner. "Accept" and "Reject" should be equally easy to find and click. Regulators in the EU and UK have specifically called out banners that bury the reject option.
  • Keep your CMP and tag configuration in sync. If you add a new tracking pixel later, make sure it's wired into your CMP's consent categories — an unblocked tag defeats the entire point.
  • Review it periodically. Google updates Consent Mode's requirements and features periodically; a setup that was compliant a year ago is worth re-checking.

Why this matters for the tools we recommend

If you're running paid campaigns through Plai or managing client accounts in HighLevel, your consent setup upstream on your own site directly affects the quality of the conversion data feeding back into those platforms. Garbage consent signals in, garbage optimization out.

This guide reflects Google's publicly documented Consent Mode V2 requirements and general GDPR/UK GDPR/ePrivacy principles as of July 2026. It's not legal advice — for anything high-stakes, talk to a qualified data protection advisor.