GA4's June 15, 2026 data-controls change — and the consent machinery a cookie-less tool never had
If you just heard that Google Analytics 4 "changed something" on June 15, 2026 and you run Google Ads, here's the short answer first: Google moved to Consent Mode (within Google Ads) as the single control over the Google Ads cookies and identifiers that GA4 collects via the Google tag and SDK. The Google Signals setting in your GA4 Admin no longer shares that job — from June 15 it only governs whether your Analytics data is associated with signed-in user information for behavioral and demographic reporting inside GA4. (Google's own support page is the primary source.)
Who this affects: GA4 properties linked to a Google Ads account. That's the scope — this consolidation governs the data flow to linked Ads accounts. What you must check: that your consent banner and Consent Mode are firing correctly, because after June 15 the ad_storage consent signal is the only gate on that advertising-identifier flow. If you don't run Google Ads, there's far less here for you — but the broader lesson holds for everyone: GA4's compliance correctness now hinges on consent machinery being wired up exactly right, and that machinery is precisely what a cookie-less tool doesn't have.
What actually changed on June 15
Before June 15, the GA4-to-Google-Ads collection of Google Ads cookies and IDs was controlled jointly: by the Google Signals toggle in GA4 Admin and by Consent Mode's Ads settings (ad_storage). Two layers, either of which could act as a brake.
After June 15, that split collapses into one gate:
ad_storage(Consent Mode) becomes the sole on/off switch for the GA4 to Google Ads advertising-identifier flow.- Google Signals is demoted to controlling only the association of your Analytics-sourced data with signed-in user information, for behavioral and demographic reporting inside GA4.
In plain terms: Signals is no longer a fallback. As Google's page puts it, after June 15 Signals "will only control the association of your Google Analytics sourced data with signed in user information for behavioral reporting."
A second, later-in-2026 stage (Google has named no firm date) goes further. The Consent Mode ad_personalization parameter becomes the exclusive control over whether GA4 data is used for audience personalization in the linked Ads account — the old multi-layer GA4 admin controls (account, property, Ads-link, and event level) stop governing it. Automatically-collected IP addresses will be encrypted and routed to the linked Google Ads account, governed by Ads settings.
Why this is an operational burden, not a one-time toggle
This is the part the second-source write-ups all land on, and they agree with Google. Piwik PRO and Dataslayer both describe the same consequence — Dataslayer puts it bluntly: "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."
After June 15, if ad_storage is granted via Consent Mode, Google Ads will collect and associate the activity regardless of whether the Google Signals toggle is on or off. Signals is no longer a second brake you can pull. The single gate is cleaner — and it's also a single point of failure.
So if your consent banner or your Consent Mode signal misfires — a tag that loads before consent, a default that's set wrong, a CMP update that quietly changes the signal — your conversions, audiences and Smart Bidding inputs can go wrong silently, with no Signals setting left to catch the gap. Nothing errors. The numbers just drift. That's the failure mode worth setting a reminder for if you depend on GA4-fed advertising.
None of this makes GA4 illegal or non-compliant — that's not the claim. It's that the correctness of your setup now rests entirely on consent plumbing being right, and stays your job to verify every time something in that chain changes.
Where a cookie-less tool sits in all this
Simplytics sets no visitor cookies and has no Google Ads integration or Consent Mode setup. It counts repeat visits on one site with a short-lived keyed daily visitor hash, deletes raw visit rows nightly and keeps daily totals, though a page path or event name in those totals can still identify someone.
And it does not share data with any ad network. There is no Consent Mode, no ad_storage, no Google Signals, no ad_personalization — nothing to reconfigure on June 15, nothing to re-check when the ad_personalization stage lands later in 2026, nothing to re-check on the next Google policy date after that. The whole apparatus this change reshuffles simply isn't present.
Before/after June 15 — what each tool asks of you
| Task | GA4 (linked to Google Ads) | Simplytics |
|---|---|---|
| Re-check which setting gates the Ads data flow | Yes — ad_storage is now the sole control |
Nothing to gate |
| Verify Consent Mode fires correctly on every page | Yes — single point of failure | No Consent Mode exists |
| Audit the Google Signals toggle's new, narrower role | Yes | No Signals |
Prepare for the later ad_personalization consolidation |
Yes — date unannounced | No ad_personalization |
| Check analytics consent and visitor notice | Yes — including default GA4 cookies | Yes — no visitor cookies to cover |
| Price | Free tool, paid configuration overhead | $12/year |
What GA4 does that we don't
GA4 does things Simplytics deliberately doesn't: ads attribution, audience building, remarketing, BigQuery export, Smart Bidding signals. If you run Google Ads and depend on GA4-fed remarketing, this June 15 change is something you have to handle, not avoid — Simplytics is not a remarketing tool and won't replace that pipeline.
The narrower point is this: most site owners just want to see visitors, pages, referrers and channels. For them, the Google Ads-specific consent-mode apparatus — Signals, ad_storage, ad_personalization and its configuration checks — is overhead in service of an ad-network integration they never use. A 1.2 KB analytics script avoids that integration.
It's also a question of price for what you actually need. Simplytics is $12/year — $1/month, billed yearly — a lot of functionality for a lot less money than the $9–15/month of Plausible and Fathom, and without the configuration overhead of "free" GA4. The script is ~1.2 KB gzipped, versus the ~140 KB of JavaScript gtag.js ships — and that setup tax is the same tax that June 15 just raised. The primary analytics database is hosted in the EU (Warsaw), and there's a 30-day free trial with no card.
The short version
On June 15, 2026, GA4 made Consent Mode the single control over the Google Ads data flow, demoting Google Signals to in-GA4 reporting and turning ad_storage into one gate — and one point of failure. If you run Google Ads through GA4, check that your consent signal fires correctly, and watch for the later ad_personalization stage.
If most of what you want is plain visitor numbers without any of that, a cookie-less tool sidesteps the whole thing. Simplytics is the cheapest paid, hosted privacy-friendly Google Analytics alternative at $1/month billed yearly (GA4 is free, self-hosted Matomo is free, and Simple Analytics has a free tier), with no Google Ads consent configuration to rework when Google's policy changes again. The full Google Analytics comparison and the other comparisons lay out the trade-offs — including the ones where GA4 wins — and the $12/year plan is there when you're ready.
Effective dates and control behavior reflect Google's published data-controls page as of June 17, 2026; the ad_personalization consolidation has no announced date. If Google revises the timeline, email us and we'll update this post.