- From June 15, 2026, Consent Mode (not Google Analytics settings) is the single control for ad data. [3][5]
- ad_storage alone decides whether conversions and remarketing flow to Google Ads. [3]
- The classic failure: your CMP wires analytics_storage but not ad_storage. Analytics looks fine; Ads bleeds. [3]
- Advanced Mode recovers modeled conversions from non-consenting users via cookieless pings. [4][6]
- Do nothing for EU traffic and you face policy warnings and serving restrictions. [2]
Most of the cookieless conversation has been about a distant future: the Privacy Sandbox, Topics, a world without third-party IDs. That future is real but slow. The thing that will actually move your numbers has a date on it: June 15, 2026, when Google Analytics stops making its own advertising decisions and hands the whole thing to Consent Mode.
Google Ads stops reading Analytics. It reads only your consent signals.
After June 15, Google Signals loses its authority and ad_storage becomes the sole parameter governing conversion tracking and remarketing audiences. If the consent signal is wrong, the data doesn't flow, and there is no Analytics-side setting left to save you. [1][3]
The trap is that Analytics keeps looking healthy
Here is the failure that will catch the most accounts. A consent platform that sets analytics_storage but never ad_storage. Today, Google Signals partly covers the gap. After the cutover it doesn't. Google Analytics 4 (GA4) keeps showing sessions and events (the dashboard looks normal) while the linked Google Ads account watches conversions and audiences quietly fall, because the one switch that now matters was never connected. [3] The problem isn't visible where you'd look for it.
This didn't come from nowhere. Enforcement has been tightening for two years.
Score your own stack
Tick only what is actually true today. Not what's on the roadmap. The number is the share of your consent stack that will keep advertising data flowing after the cutover.
Are you wired for June 15?
Seven things decide it. The score weights them by how much conversion and audience data each one controls.
"Ready" needs the three wiring essentials all ticked (Consent Mode live, all four signals, and ad_storage set), not just a high total. Miss one of those and a strong score still can't make you ready. That's the point.
Basic vs Advanced is the decision that limits your losses
If you've done nothing else, do this one. The mode you run changes how much signal survives a refusal.
No consent: tags are blocked entirely. Zero data for that user. Full visibility loss on every refusal.
No consent: tags still fire, set no cookies, send cookieless pings. Google models the conversions you can't see.
Advanced Mode won't hand back identifiable users or remarketing. Those genuinely require consent. But it keeps modeled conversions flowing, which for most EU-exposed accounts is the difference between a measurement dent and a measurement hole. Google's own Consent Mode documentation describes the mechanics: denied-consent tags store no cookies and send cookieless pings that carry consent state and key-event signals, which Google then uses to model the gaps. [4][6]
None of this is a Privacy Sandbox project you can schedule for next year. It's a consent-wiring job with a fixed deadline, an invisible failure mode, and a direct line to your reported revenue. Audit the four signals, confirm ad_storage is set on refusal and grant, turn on Advanced Mode, and watch consent rate against conversions across the cutover. The accounts that get hurt won't be the ones that planned for a cookieless future. They'll be the ones that missed a switch.
Sources
- Google · Consent Mode: developer implementation guide
- AuditSocials · Google Ads Consent Mode v2: EU enforcement timeline & implementation
- UniConsent · The 15 June 2026 Google Ads Consent Mode change
- Usercentrics · Google Consent Mode: Basic vs Advanced
- Google · Updates to Google Analytics Data ControlsGoogle's own announcement of the June 15, 2026 consent control change
- Google · About consent modeGoogle's doc on basic vs advanced consent mode, cookieless pings, and conversion modeling
Frequently asked questions
What actually changes on June 15, 2026?
Google Analytics stops referencing its own advertising settings (including Google Signals) and relies entirely on the signals your consent management platform sends through Consent Mode. After the cutover, ad_storage is the single parameter governing whether conversions and remarketing audiences flow from GA4 to Google Ads. Analytics data can keep collecting while advertising data quietly stops.
What is the most common way this breaks?
A consent platform that sets analytics_storage but not ad_storage. Before the change, Google Signals could partly cover for that. After it, GA4 still shows sessions and events, but linked Google Ads accounts see conversions and audiences fall, because the one switch that now matters was never wired. The failure is invisible in Analytics, which is what makes it dangerous.
Do I lose all data for users who refuse consent?
Only in Basic Mode. In Advanced Mode, Google tags still fire without consent but set no cookies or identifiers. They send cookieless, anonymized pings that Google uses to model conversions. Advanced Mode is the main way to recover part of the signal from non-consenting users. It won't give you identifiable data or remarketing, but it keeps modeled conversions alive.
Which consent parameters do I need?
All four: ad_storage (ad cookies and identifiers), analytics_storage (analytics cookies), ad_user_data (sending user data for ads, e.g. enhanced conversions), and ad_personalization (using data for personalized ads). After the cutover, ad_storage governs conversion tracking and remarketing, and ad_personalization gates whether Analytics data can be used for personalized ads.
What happens if I do nothing for EU traffic?
You lose remarketing and audience building for EEA/UK users, lose conversion modeling for non-consented users, and in 2026's full-enforcement phase your account receives policy-compliance warnings and faces potential serving restrictions on EU-targeted campaigns. The enforcement has been ratcheting since March 2024. This is the step that makes it bite.
Is the June 15, 2026, change the same as the Privacy Sandbox?
No. The Privacy Sandbox is the slow, longer-term shift away from third-party identifiers, while this is a consent-wiring job with a fixed deadline and an immediate effect on reported revenue. Treating it as a future project you can schedule for next year is exactly how accounts get caught, because the cutover acts on the signals your consent platform sends today.
How do I check whether my stack is ready before the cutover?
Audit the four consent signals and confirm your platform sets ad_storage on both grant and refusal, not analytics_storage alone. Verify Consent Mode is live on all EU, EEA, and UK traffic, turn on Advanced Mode for modeled conversions, and monitor consent rate against conversions and audience size across the cutover. Readiness needs the three wiring essentials all in place, not just a high checklist score.
How long has this consent enforcement been building?
Since March 2024, when new remarketing audiences stopped forming from EEA and UK traffic. Existing remarketing audiences stopped populating in September 2024, and conversion modeling for non-consented users was disabled in March 2025 for accounts without Consent Mode implemented, while accounts running Consent Mode Advanced still receive modeled conversions. The June 15, 2026, cutover is the step that makes ad_storage the single switch and brings full enforcement.
Mikołaj Salecki
Writes about media, tech, and AI business for people who actually run digital. Former agency lead. Skeptic of frameworks that read better than they perform.
Get the next issue by email.
One letter, once a week. Sharp coverage of media, tech, and AI business. No filler.
