What's changing on June 15
Right now, two settings jointly control whether Google Ads can read advertising cookies and user IDs from your website: the Google Signals setting in GA4 and the ad_storage parameter in Consent Mode. Either one can restrict ad data if misconfigured.
On June 15, that changes. Google Ads will stop reading the GA4 Google Signals setting entirely. ad_storage in Consent Mode becomes the single gate. If it signals denied (intentionally or because your CMP is misconfigured), Google Ads gets no advertising cookies, no user IDs, and no conversion signals from those sessions.
The practical shift: the ad_storage signal sent from your website in real time is now the only thing that determines what ad data gets collected.
The safety net that's disappearing
Here's why this matters even if you don't run EU campaigns.
Many accounts have used "Google Signals OFF" in GA4 as a privacy backstop. The logic was: even if the consent banner was broken or the GTM container fired in the wrong order, having Signals disabled in GA4 would limit ad-related data exposure as a fallback.
That backstop is gone after June 15. GA4 settings no longer control Ads behavior.
If your CMP fires after GTM loads (a common implementation error), or if the consent update doesn't reach the GTM dataLayer before tracking tags fire, ad_storage may be sent as granted even when a user chose to decline. Previously, Google Signals OFF could catch some of this. Now, nothing does.
The reverse is also true. If ad_storage is incorrectly set to denied for all users due to a misconfiguration, your conversion data shrinks, remarketing lists shrink, and Smart Bidding loses signal. No error message. No alert. Just smaller numbers you may not attribute to the right cause for weeks.
Who this hits hardest
Two types of accounts are most exposed.
Accounts running EU/EEA campaigns under GDPR who implemented Consent Mode v2 but haven't verified the actual signal flow since setup. CMPs send consent updates through the browser to GTM; GTM reads them and updates the dataLayer; then tracking tags fire. If any step in that chain is broken — wrong trigger timing, outdated CMP template, wrong tag configuration — the signal you think you're sending isn't the one Google Ads receives.
Accounts that implemented Consent Mode when it first launched and haven't touched it since. CMP providers have updated their SDKs multiple times. Tag templates drift. If you're on a custom CMP integration rather than a certified Google partner CMP, the margin for error is higher.
US-only accounts with no consent requirements are less immediately exposed. But if Europe is in your growth plans, this is the infrastructure to get right before you scale spend into those markets.
What to check before Sunday
Four things worth verifying in the next four days.
Run the GTM preview tool and watch the actual firing sequence: does the consent update fire before or after your Google Ads conversion tag? The update needs to arrive first. If conversion tags fire before the consent event, Smart Bidding is operating on a signal it shouldn't have.
Check your CMP against the dataLayer directly. Log in from an EU location (or use a VPN), decline targeting cookies, then inspect the dataLayer for ad_storage. It should read denied. If it reads granted or isn't present at all, your CMP isn't sending the right signal regardless of what its dashboard shows.
Pull your EU-targeted campaign conversion volume for the last 30 days and save it as a baseline. Run the same report after June 20. Any drop in reported conversions on EU traffic is your signal that the setup was relying on the GA4 backstop.
Review your privacy documentation. If it references GA4 Google Signals as an ad data control, that's no longer accurate after June 15 — and regulators can read privacy policies.
The broader shift happening here
Google is moving the source of truth for ad data collection from analytics settings to website-side code. The stated reason is simplification. The practical effect is that advertisers now own the full risk of their CMP implementation, with no platform-side fallback.
This follows the same pattern across all major platforms: iOS 14 removed the safety net for Meta, GA4's own data controls shift moved it for analytics, and June 15 does it for Google Ads consent. The platforms are not providing workarounds for missing first-party infrastructure anymore — they're expecting you to have built it correctly.
Accounts that have treated their CMP as a legal checkbox rather than a measurement input are about to find out the difference.
If you want to see how your account's tracking setup stacks up — consent mode, conversion configuration, data quality — Gromerce's free audit surfaces those gaps in under three minutes.
Your consent setup either works or it doesn't. After June 15, there's nothing downstream to catch the difference.
Related articles: google-ads-data-retention-cut-june-2026 · google-journey-aware-bidding-lead-gen-2026 · google-merchant-center-conversational-attributes-2026
Sources: Google Analytics Help Center, PPC.land, Dataslayer.ai, ALM Corp, Merkle, The Drum, June 2026
