On June 15, 2026, Google changes how data flows between Google Analytics 4 and Google Ads. If your GA4 property is linked to Google Ads (most are), this affects how advertising cookies, user IDs, and remarketing audiences are controlled. The date is confirmed by Google, the change is real, and the impact on your reporting is bigger than the announcement suggests.
In plain terms: Google Signals stops being the gatekeeper for Google Ads data collection. Consent Mode's ad_storage parameter inside Google Ads takes over as the sole authority. Before June 15, both settings governed the flow. After, only Consent Mode does.
This guide explains what changes, who it affects, and the specific audit to run before the deadline so your reports stay clean the first week of June 16.
What changes on June 15, 2026
Google's phrasing in the official announcement: "Google Ads settings will exclusively control Google Ads data" and "Google Analytics settings will exclusively control data used within Google Analytics for behavioral reporting."
Why it matters
This change hits harder than the announcement suggests.
The end of dual control. Today, if Consent Mode isn't set up right, Google Signals acts as a fallback for Google Ads cookies and IDs. After June 15, that fallback is gone. Any site running a loose Consent Mode implementation will silently lose advertising data the day of the switch.
Audience sizes may shrink. Remarketing audiences in GA4 that rely on Google Signals for cross-device reach will now only include users who explicitly granted ad_storage via Consent Mode. If your consent banner is ambiguous, or if users have been rejecting ad_storage at higher rates than you thought, your lists will shrink on June 15.
Cross-channel reporting gets cleaner but stricter. Dashboards that aggregate Google Ads + GA4 + other channels have historically had to reconcile two overlapping consent signals for Google. After June 15, Consent Mode is the single control point. Cleaner, but also less forgiving of misconfigurations.
What this means for your reports
If your reporting stack pulls from both GA4 and Google Ads APIs, three things change in practice:
- Signed-in user reports in GA4 continue to work exactly as they do today. Google Signals retains that job.
- Remarketing and Google Ads audience lists built from GA4 only include users who granted
ad_storage. Compare list sizes on June 14 vs June 16 to see your real consent capture rate. - Cross-channel blended reports no longer need to juggle Signals vs Consent for the Google Ads slice. After June 15, Consent Mode alone governs Google Ads data collection across every dashboard.
For agencies managing multiple clients, the audit burden grows. Every client's consent banner and Consent Mode tag configuration becomes critical. A misconfigured client loses data June 15 with no manual fallback.
Action plan: what to do before June 15
Run this 7-step audit in the next two weeks. It takes a few hours per property.
- Audit your Consent Mode implementation. Open Google Tag Manager or the gtag.js setup. Verify that
ad_storage,analytics_storage,ad_user_data, andad_personalizationare explicitly defined. Use Google Tag Assistant to confirm the signals fire correctly on page load and on user consent change. - Check GA4 → Admin → Data Collection. Note whether Google Signals is currently enabled. After June 15, this setting still matters for signed-in user reporting, but not for Google Ads data. Decide if you want to keep it on.
- Verify each Google Ads link. GA4 Admin → Product Links → Google Ads Links. Every linked account inherits the new behavior June 15. If you manage multiple accounts, build a spreadsheet listing property, Ads account ID, and current Google Signals status.
- Review audiences that depend on Google Signals. GA4 Admin → Audiences. Flag any that reference cross-device behavior. These only work after June 15 if
ad_storageconsent is granted. - Update your consent banner for Consent Mode v2 if you haven't already. Ambiguous consent flows silently block remarketing starting June 15. Test with Tag Assistant in both "accept all" and "reject all" user scenarios.
- Brief your stakeholders. Agencies: flag this change to every client. In-house teams: flag to analytics leadership and performance marketing. Reports comparing pre- and post-June 15 numbers will show shifts.
- Run a baseline report on June 10 and June 20. Capture Google Ads conversion counts, GA4 audience sizes, and remarketing list sizes. The pre/post comparison is your troubleshooting tool if anything looks off in July.
Timeline
- June 15, 2026: Google Signals stops controlling Google Ads data collection. Consent Mode
ad_storagebecomes the sole authority. - Later in 2026: Ads personalization settings move from GA4 to Google Ads. Consent Mode
ad_personalizationexclusively controls personalization for linked Ads accounts. Exact date pending from Google. - Later in 2026: IP addresses auto-collected by the Google Tag and SDK will be encrypted and flow to the linked Google Ads account instead of staying in GA4. Exact date pending.
FAQ
Does this affect GA4 properties that are NOT linked to Google Ads?
No. If your GA4 property has no Google Ads link, your data collection and reporting are unaffected by this change.
Do I still need Google Signals enabled after June 15?
Only if you want signed-in user association for behavioral reports (cross-device journeys, demographics, interests in GA4 itself). It no longer controls Google Ads data flow, so the decision is purely about GA4 reporting features.
What happens to existing remarketing audiences built in GA4?
They continue to exist but only include users who granted ad_storage via Consent Mode. Audience sizes may shrink if your previous consent capture was below 100%, because Google Signals is no longer available as a fallback.
Is this related to Consent Mode v2?
Yes. Consent Mode v2, which Google launched in 2024, is the framework gaining exclusive authority here. If your consent banner has not been updated for Consent Mode v2, do that first. It is the prerequisite for everything else.
Will my Google Ads conversion tracking break?
No. Conversion tracking itself is not changing. What changes is how Google Ads cookies and IDs are collected specifically through the GA4 tag. If you implement Google Ads conversion tracking directly (via the Google Ads tag, not the GA4 tag), this change does not affect you.
Conclusion
Google is simplifying a system that previously had two overlapping controls. The simplification is welcome for advanced users who run tight consent setups. It is unforgiving for anyone whose current data flow has been quietly leaning on Google Signals as a fallback.
Between now and June 15, run the 7-step audit above. After June 15, compare your audience sizes and conversion counts against the June 10 baseline. Any measurable drop, beyond normal week-over-week fluctuation, is probably your consent capture showing its real number for the first time.
Keep your cross-channel reports clean through the transition. Try Dataslayer free for 15 days. No credit card required.
