GA4 + Google Ads Consent Split: What Changes June 15

On June 15, 2026, Google changes how Google Analytics 4 and Google Ads share data — and the change quietly removes a control that a lot of SaaS teams have been relying on without fully realizing it. If your stack uses GA4 alongside Google Ads, this is not a cosmetic settings tweak. It alters which lever actually decides whether behavioral data flows into your linked ad account, and it does so with four days' notice for anyone reading this on publication day. Below is what is changing, why it matters for conversion tracking and compliance, and the specific checks to run before the deadline.

What is actually changing

Until now, two separate mechanisms could influence whether GA4-sourced data reached Google Ads: the Google Signals toggle inside GA4, and the consent state expressed through Consent Mode. From June 15, those roles split cleanly. As Piwik PRO explains in its breakdown of the change, Google is separating the controls that govern data use in GA4 and Google Ads, so that each platform's data is governed where that data is used. Google Signals will keep doing one job — deciding whether Analytics associates data with signed-in users for behavioral reporting inside GA4 — and nothing more.

The decisive control for advertising data becomes the ad_storage signal in Consent Mode. After the change, ad_storage is the sole authority over whether activity collected for a linked Google Ads account is stored and associated. PPC Land, covering the rollout, framed it bluntly: Google is stripping Analytics of ad-data authority in a June 2026 consent overhaul. In plain terms, the platform where the data is used now owns the control for that data, and for Google Ads that control is the consent signal you send — not a checkbox in the GA4 admin.

Why the "Signals off" backstop disappears

Here is the part that catches teams out. For years, a common informal safeguard was to turn Google Signals off in GA4 — the reasoning being that if a consent banner was imperfect or a tag misfired, having Signals disabled would at least limit how much advertising data leaked. It was never a formal compliance mechanism, but plenty of privacy-cautious teams used it as a belt-and-braces second line of defense.

After June 15 that line of defense is gone. If ad_storage is granted through Consent Mode, Google Ads will collect and associate the activity with the user's signed-in Google account, regardless of whether Google Signals is on or off. The Signals toggle simply no longer touches the Google Ads pathway. This is corroborated across vendor analyses including Merkle's note on the updates to Google Analytics data controls. The upshot: your true control is now the accuracy of the consent state you pass, which raises the stakes on getting Consent Mode exactly right.

What it means for conversion tracking and remarketing

Consent logic stops being a legal footnote tucked inside a banner plugin and becomes a direct input to measurement quality. The same ad_storage signal now governs conversion attribution, audience eligibility, remarketing reach, and modeled measurement. If your implementation has been over-granting ad_storage — for example defaulting to granted before a user chooses — you may have been inflating remarketing audiences and conversion counts in ways that were partly masked by the old dual-control setup. After June 15, the relationship between your consent signal and what Google Ads receives is more direct and less forgiving.

The flip side matters too. Teams that correctly withhold ad_storage until consent is given may see reported conversions and audience sizes shift on June 15, because the ad pathway now follows the consent signal faithfully. That is not a bug; it is the system finally reflecting your stated consent policy. The risk is misreading a legitimate, consent-driven drop as a tracking failure and "fixing" it by loosening consent — which would trade a reporting dip for genuine compliance exposure. Understanding the difference is exactly why we treat GA4 privacy and server-side tracking as an architecture question, not a banner question.

The three checks to run before June 15

First, audit how ad_storage is set in your Consent Mode implementation. Find every place the signal is granted or denied — your CMP, your GTM container, any hardcoded defaults — and confirm there is a single, intentional source of truth. Second, confirm your default consent state is denied until a user makes a choice. With the old Signals backstop gone, a "granted by default" configuration now flows straight through to Google Ads, which is precisely what most SaaS compliance postures are trying to avoid.

Third, verify that your reject path actually withholds ad_storage rather than merely hiding the banner. Click "reject" in a staging environment and inspect the consent signal that fires; a surprising number of setups visually dismiss the banner while still granting advertising storage. Dataslayer's walkthrough of what changes on June 15, 2026 is a useful checklist to test against. Do this in a staging container, not production, so you observe the new behavior before your live reports do.

The bigger picture: consent is moving closer to the data

This change fits a clear 2026 pattern: control is migrating to where data is actually used, and consent signals are becoming the load-bearing mechanism rather than platform-level toggles. Matomo's review of the year's shifts describes regulators and platforms alike looking under the hood of how measurement is configured. The era when a single admin checkbox could serve as a privacy safety net is ending; what you collect and share is now determined by the explicit signals your stack emits.

For SaaS teams, the strategic read is that coupling your measurement tightly to the GA4-and-Google-Ads pipeline means inheriting every one of these control changes on Google's timeline, not yours. Analytics that runs first-party, in aggregate, on your own infrastructure is insulated from this specific change because it never depended on ad_storage in the first place — the same reasoning behind moving toward cookieless, first-party acquisition data. Whatever you decide long-term, the immediate task is concrete: get your Consent Mode configuration right, test it in staging, and do it before June 15.