Consent Mode v2: What to Set Up Before the June 15, 2026 Deadline

What Changes on June 15, 2026

This is not a sudden policy change. Google has been rolling back legacy data pipelines since late 2023. Here is the full timeline.

November 2023: Google announces Consent Mode v2 and introduces two new parameters — ad_user_data and ad_personalization — on top of the existing ad_storage and analytics_storage.

February 2024: Google removes Google Signals from GA4 reporting identity. Properties using “Blended” reporting identity, which relied on Google Signals for cross-device user stitching, are automatically migrated.

6 March 2024: Consent Mode v2 becomes mandatory for new EEA audience building and remarketing in Google Ads. Any advertiser without it stops accumulating new EEA remarketing audiences from this date.

June 15, 2026: Final deprecation. Every legacy Google Signals data path that was grandfathered during the transition period shuts off. There is no further grace period.

Three definitions to know

• Consent Mode v2 is Google’s updated protocol that passes 4 consent signals to Google Tags before any data collection. Without it, Google cannot lawfully process EEA/UK visitor data for advertising purposes.
• A CMP (Consent Management Platform) is a tool that displays a cookie consent banner and passes the user’s decision to analytics and advertising tags. Examples: CookieYes, Cookiebot, Complianz.
• Google Signals was a legacy GA4 feature that collected cross-device and demographic data without requiring explicit CMP-level consent. It is being fully retired on June 15, 2026.

Who Is Affected

Category 1: EU/EEA-based businesses advertising on Google

If you are running Google Ads campaigns in Germany, France, the Netherlands, or anywhere in the EEA, you have been under the Consent Mode v2 mandate since March 2024. The June 15 deadline closes the remaining legacy data paths. German businesses face strict DSGVO enforcement, and German data protection authorities are active in enforcement around consent management. Non-compliance is not a theoretical risk.

Category 2: UK businesses post-Brexit

The UK is no longer in the EU, but UK GDPR mirrors the EU standard on consent for online tracking. Google applies Consent Mode requirements based on user geolocation, not advertiser location. If your UK e-commerce site or B2B SaaS receives traffic from EEA visitors — even incidentally — Consent Mode v2 applies to that traffic. UK businesses operating on Shopify, WooCommerce, or any other platform with GA4 and Google Ads are affected.

Category 3: US, AU, and other non-EEA advertisers targeting Europe

As of May 2026, Google applies Consent Mode requirements based on user geolocation, not advertiser location. A US direct-to-consumer brand running Advantage+ Shopping or Performance Max campaigns that includes EEA/UK in its targeting is fully subject to these rules. I have clients in this situation — they were surprised to learn this applies to them.

What Breaks Without Consent Mode v2

The table below compares legacy Google Signals behaviour against the two Consent Mode tiers.

What breaks specifically after June 15, 2026

Missing Consent Mode v2 is effectively one of the Google Ads mistakes that drain your budget — except this one has a hard external deadline rather than being a configuration choice.

10 Pre-Deadline Checks

Work through these in order. Each one is a specific action, not a vague suggestion.

1. Verify default consent state in your Google Tag

   Open GTM or your gtag.js snippet. Confirm that your default consent state sets all four parameters to denied for EEA/UK visitors. The code should look like this:

   gtag('consent', 'default', {
     'ad_storage': 'denied',
     'analytics_storage': 'denied',
     'ad_user_data': 'denied',
     'ad_personalization': 'denied',
     'region': ['EEA', 'GB']
   });

   If ad_user_data and ad_personalization are absent, you have Consent Mode v1. You need to add them.

2. Open GTM → Admin → Consent Overview

   In Google Tag Manager, go to Admin → Consent Overview. Every tag should show a green tick for its consent category. If you see amber or red warnings, those tags are not consent-aware and may fire without user consent.

3. Confirm the consent initialization trigger fires first

   In GTM, the “Consent Initialization” trigger must fire before any other trigger. If your GA4 configuration tag or Google Ads conversion tag fires on “All Pages” without checking consent first, data is flowing before you have permission to collect it.

4. Test your CMP banner — verify the update command fires

   Click “Accept all” on your cookie banner, then open browser DevTools → Network tab and search for consent. You should see a gtag('consent', 'update', {...}) call with ad_storage: 'granted' and the other three parameters updating accordingly. If you do not see this call, your CMP is not passing consent back to Google Tags.

5. Verify your CMP is Google-certified

   Go to cmppartnerprogram.withgoogle.com and search for your CMP provider. If it is not listed, you have two options: switch to a certified CMP, or implement Consent Mode manually via GTM (more work, more risk of error). The certified list as of May 2026 includes CookieYes, Cookiebot, Complianz, Iubenda, OneTrust, and others.

6. Check GA4 Admin → Product Links → Google Ads Links

   In GA4, navigate to Admin → Product Links → Google Ads Links. Confirm the link to your Google Ads account is active (green status). Without this link, consent-mode data cannot flow from GA4 to Google Ads for audience building and conversion import — even if Consent Mode is otherwise correctly configured.

7. GA4 Admin → Data Collection → consent settings

   In GA4 Admin → Data Collection and Modification → Data Collection, review the consent settings panel. Google rolled out a new consent-based data collection acknowledgment in 2025. Confirm this is acknowledged and that your settings reflect your CMP integration.

8. Run Tag Assistant in debug mode — check consent_granted events

   Open Google Tag Assistant (tagassistant.google.com), connect it to your site, and interact with the cookie banner. After accepting cookies, you should see consent_granted events in the event stream with the correct parameter values. If Tag Assistant shows consent events with incorrect states, something in your CMP integration is broken.

9. Check Google Ads → Audience Manager → status

   In Google Ads, go to Tools → Audience Manager and review your remarketing audiences. Status should show “In use” for active audiences. If you see “Needs attention” or declining user counts on EEA-heavy audiences, Consent Mode is either missing or incorrectly configured.

10. Test with a EU VPN → GA4 Realtime

    The cleanest end-to-end test: connect to a VPN with a German or French exit node, visit your site, accept cookies, then check GA4 Realtime. You should see the session appear. If the session does not appear in Realtime after accepting cookies, something in the consent flow is blocking data collection.

Which CMP to Choose

Prices and features as of May 2026. Verify current pricing at each vendor before purchasing.

My recommendations by platform

• WordPress site → Complianz. Free plugin for basic compliance, $59/year for full Consent Mode v2 with GTM integration. Native WP plugin means no JavaScript conflicts.
• Shopify or platform-agnostic → CookieYes free tier. Consent Mode v2 is included, setup is straightforward, works on any platform via script embed.
• Budget £6-10/month → Cookiebot Premium Lite. Well-established, Google-certified, used widely across DE and UK markets.
• Multi-language European site → Iubenda. Handles IAB TCF 2.2 alongside Consent Mode v2 and supports multiple jurisdictions from a single dashboard.

If you are evaluating alternatives to Google Analytics altogether, read my GA4 vs Matomo vs Plausible comparison.

If you are setting up GA4, GTM, and Google Ads from scratch alongside this, start with the GA4 + GTM + Google Ads base setup guide first, then come back here for the consent layer.

Common Setup Mistakes

1. Configuring only two of the four parameters

   The two new v2 parameters — ad_user_data and ad_personalization — are the ones most commonly missing. Having ad_storage and analytics_storage correct but missing the v2 parameters means you are on Consent Mode v1, not v2. Check your default consent state and your CMP update command for all four.

2. Consent Mode Basic when Advanced is needed

   Consent Mode Basic fires tags only after consent is given, with no modeling for users who decline. For advertisers running Performance Max or Smart Bidding campaigns targeting Germany or France, this means significantly reduced conversion modeling accuracy. Advanced is the correct implementation for any advertiser who cares about EU campaign performance.

3. CMP banner not passing the update command

   Users click “Accept” but gtag('consent', 'update', {...}) never fires. This happens when the CMP plugin is installed but the GTM integration is incomplete. The banner looks functional, but Google Tags never receive the consent update — so all sessions appear as “no consent,” including those from users who accepted.

4. Consent initialization trigger firing too late

   In GTM, the default consent state must be set before any other tag runs. A common failure: the default consent state is set inside a Custom HTML tag firing on DOM Ready, by which point GA4 and Google Ads tags have already fired. Use the “Consent Initialization” trigger type, which GTM executes before all others by design.

5. Basic mode with no geo-restriction

   A global Consent Mode Basic setup with no region restriction creates two problems simultaneously: non-EU traffic is unnecessarily restricted, and EU traffic lacks Advanced modeling. The fix: add region: ['EEA', 'GB'] to the default denied state and upgrade the EU-targeted configuration to Advanced.

This Takes 4 Hours, Not 4 Weeks

Here is a realistic time breakdown:

If you already have a CMP installed, you are looking at 2-3 hours, not 4. The only scenario where this takes longer is if your tagging setup is custom or heavily customized, or if you are migrating from a non-certified CMP.

The risk of not doing it before June 15 is concrete: shrinking remarketing audiences, degraded Smart Bidding, and blank demographic reports. The cost of doing it is an afternoon.

Frequently asked questions