There is a deadline nine days from today that will break audience targeting and conversion attribution for advertisers who don't act. June 15, 2026 is when Google removes a compliance mechanism that many advertisers never realized they were relying on.
What's Being Removed
For two years, advertisers have had two controls over advertising data collection:
- Consent Mode in GTM — the user-facing
ad_storagesignal controlled by your Consent Management Platform (CMP) - Google Signals toggle in GA4 Admin — a backend switch that, when OFF, blocked cross-device identifiers and advertising cookies from flowing from GA4 to Google Ads
This "dual-control" model acted as a safety net. Even if your CMP was misconfigured and ad_storage was firing granted incorrectly, the Signals toggle being OFF would block the data from reaching Google Ads.
Starting June 15, 2026, that safety net is gone. Google Signals still controls behavioral reporting inside GA4, but has zero authority over what data flows to Google Ads. Consent Mode becomes the sole point of control.
Who Is Immediately at Risk
The highest-risk profile: advertisers who turned Google Signals OFF in GA4 as a GDPR/CCPA compliance shortcut, without fully configuring their CMP. On June 15, your Signals toggle still says OFF — but Google Ads starts receiving ad_storage data because your CMP is leaking it. You go from "technically compliant via backend toggle" to "collecting data without proper user consent" without changing a single setting.
What Breaks Without Correct Consent Mode
- GA4-based remarketing audiences shrink or stop updating
- Cross-device conversion attribution fails for conversions relying on linked sign-in data
- Smart Bidding loses data density — CPAs drift upward
- Conversion modeling only works if Consent Mode signals are firing correctly in the first place
The Four-Step Audit You Must Complete Before June 15
1. Verify ad_storage in Tag Assistant. Enable debug mode, browse your site, and interact with your consent banner. Confirm that ad_storage defaults to denied before consent and only flips to granted after explicit acceptance — and that the update fires BEFORE Google Ads tags trigger.
2. Check the gcd consent string in network requests. Open Chrome DevTools → Network tab → filter for requests to google-analytics.com and googleads.g.doubleclick.net. Find the gcd string in URL parameters. Absent or malformed means your consent signal isn't being received correctly, regardless of what your dashboard shows.
3. Verify CMP-to-GTM wiring. Most CMPs have a GTM template or JS integration. Verify the CMP correctly calls gtag('consent', 'update', {...}) in the data layer. A "green" CMP dashboard status means the banner is showing — not that the consent state is being communicated to Google tags.
4. Check server-side GTM if you have it. Ensure your server container is not stripping or modifying consent state before forwarding data to Google's collection endpoints. Server-side setups can silently drop consent parameters.
After June 15: Update Your Privacy Policy
The removal of the GA4 Signals override is a meaningful change to how advertising data flows on your property. Update your privacy policy to reflect that user consent via the ad_storage signal is now the exclusive mechanism controlling advertising data collection.
Nine days is not much time. The CMP misconfiguration risk is real. Run the Tag Assistant check today and escalate to your developer if ad_storage is not behaving correctly. Agencies managing multiple accounts: audit your top accounts now, prioritizing those with legacy "Signals OFF" configurations.
Sources: Google Ads Help: About Consent Mode · Google Analytics Help: Google Signals · Search Engine Land: GA4 Override Removal
