On April 15, 2026, Google sent an email to all customers with linked GA4 and Google Ads accounts announcing a change taking effect June 15, 2026. The notice was short, framed as a simplification, and easy to miss. What it actually describes is the removal of Google Signals as a privacy control over advertising data, a change that Krista Seiden, a former Google Analytics product manager (2016-2019) and founder of KS Digital, is calling one of the most significant privacy control removals advertisers have seen in years. Her April 21 LinkedIn post on the topic generated 650+ reactions and 69 comments within hours, a level of engagement that reflects how seriously practitioners are taking this. If your business runs Google Ads campaigns linked to GA4, you have until June 15 to audit your Consent Mode setup. Here is what changed, why it matters, and exactly what to do.
What Happened: The Google Signals Change June 2026
Google Signals is a GA4 feature that associates behavioral data with signed-in Google users, enabling cross-device reporting and audience building. Currently, Signals governs both GA4 internal reporting and advertising data collection for linked Google Ads accounts. That dual role ends on June 15, 2026.
After that date, Google Signals will be restricted to behavioral reporting inside GA4 only. The authority over advertising data, including all advertising identifiers, cookies, and behavioral attribution flowing to Google Ads, transfers exclusively to the ad_storage consent signal in Consent Mode. Google framed this as "simplifying controls and streamlining the consent process," but as reported by PPC.land citing Seiden's analysis, the practical effect is that a privacy lever marketers could use to restrict ad data collection is being removed.
Timeline:
April 15, 2026: Google emails affected accounts. The 90-day disclosure update window begins.
April 21, 2026: Krista Seiden posts her critique on LinkedIn. 650+ reactions, 69 comments within hours.
June 15, 2026: Change takes effect. Signals loses authority over ad data.
ad_storagebecomes the only control.
Why the Google Signals Change Matters for Your Marketing
What Google Signals Actually Does Now
Right now, if you have Signals enabled, it serves two functions: it powers cross-device reporting in GA4 (linking behavior across devices when users are signed into Google), and it governs whether advertising identifiers flow to linked Google Ads accounts. If you have Signals disabled, it acts as a brake on ad data collection, even if your Consent Mode is loosely configured. That brake is being removed.
What Changes on June 15
After June 15, the only thing that determines whether Google Ads receives advertising data from your GA4 property is the ad_storage consent signal. If ad_storage is granted, Google Ads gets full access to advertising cookies, identifiers, and behavioral signals. If ad_storage is denied, Google Ads is restricted to non-persistent methods only (such as URL parameters like gclid), which significantly limits conversion tracking and remarketing pool size. Seiden's concern, shared by GDPR officers and privacy engineers in the LinkedIn thread, is that this consolidation increases legal exposure for EU/EEA data controllers who may not realize their ad_storage configuration is granting more data access than they intended.
The Consent Mode Gap Most Businesses Do Not Know They Have
This is where most coverage of this story stops. What gets less attention is that the majority of businesses that have "implemented" Consent Mode have done so incorrectly, or incompletely, and the June 15 change removes the Signals fallback that was quietly protecting some of them.
Consent Mode v2 requires four consent signals: analytics_storage, ad_storage, ad_user_data, and ad_personalization. Each must default to denied before any user interaction, then update to granted after the user accepts via a Consent Management Platform (CMP). Proper implementation means the consent_default command fires before any Google tags load, not after. Most implementations I audit get this backwards. The CMP fires, the tags fire first, and then the consent update catches up too late to matter for that session.
Current data puts GA4 Consent Mode v2 adoption at around 31%. That means roughly 69% of GA4-linked Google Ads accounts are running without proper Consent Mode. Some of those accounts had Signals enabled as a partial safeguard. After June 15, that safeguard is gone. If ad_storage is misconfigured or absent, those accounts will either lose attribution data (if ad_storage defaults to denied without a proper grant pathway) or unknowingly over-collect data (if ad_storage is defaulting to granted with no CMP in place). Neither outcome is acceptable from a compliance or measurement standpoint.
The 7-Step Signals Safety Checklist Before June 15, 2026
No competing coverage on this story includes a concrete implementation checklist. Here is the exact audit I run for clients before any Consent Mode change of this scope:
Confirm GA4-Ads linkage. In GA4, go to Admin > Product Links > Google Ads Links. If your property is linked, this change applies to you. Document the linked account IDs.
Locate your Consent Mode initialization tag. In Google Tag Manager, search for your Consent initialization tag (usually labeled "Consent Defaults" or "Consent Mode v2"). Verify it is triggering on "All Pages" and positioned before any Google tags via tag sequencing or trigger priority.
Verify
ad_storagedefaults to denied. Open the tag configuration and confirmad_storage: 'denied'is set in the default state. If you seead_storage: 'granted'as the default, that is a GDPR exposure and a misconfiguration that predates this change but becomes more critical after it.Audit your CMP configuration. If you use OneTrust, Cookiebot, Usercentrics, or a similar platform, log in and verify that the "Advertising" or "Marketing" consent category maps to
ad_storageandad_personalization. Missing this mapping means user consent never reaches Google's consent signals.Update your privacy disclosure. Google requires disclosure updates within 90 days of April 15 (deadline: June 15). Your privacy policy must describe the
ad_storageconsent mechanism and what data it controls. Have your legal team review the language, especially for EU/EEA audiences.Test with Google Tag Assistant. Navigate to your site with Tag Assistant active. Verify that
consent_defaultfires first, withad_storage: denied, and thatconsent_updatefires after user acceptance withad_storage: granted. Any deviation from that sequence is a bug.Document your configuration for compliance records. Export a screenshot of your Consent Mode tag settings, your CMP mapping, and your privacy disclosure version. Date-stamp it. GDPR enforcement requires you to demonstrate what consent configuration was in place and when.
How MKDM Can Help
Consent Mode audits are part of every Google Ads engagement I run. The June 15 deadline is tight for any business that has not yet confirmed its ad_storage configuration, and the consequences of getting it wrong go beyond lost data. For EU advertisers, a misconfigured ad_storage tag that defaults to granted without proper CMP consent is a live GDPR liability.
If you want a second set of eyes on your Consent Mode setup before June 15, or if you are not sure whether your property is even affected by this change, contact MKDM for a quick audit. I can review your GTM container, confirm your CMP mapping, and flag any configuration gaps before they become a compliance problem.
Frequently Asked Questions
What is Google Signals and why is it changing in June 2026?
Google Signals is a GA4 feature that links behavioral data to signed-in Google users for cross-device reporting and audience building. Starting June 15, 2026, Google is removing Signals as a control over Google Ads data collection. After that date, Signals will only govern behavioral reporting inside GA4, while ad_storage in Consent Mode becomes the sole authority over all advertising data flowing between GA4 and Google Ads. The change was announced via email on April 15, 2026, and drew sharp criticism from former Google Analytics PM Krista Seiden, who argued it benefits Google by consolidating control in a layer (Consent Mode) that many organizations have not implemented correctly.
Does the Google Signals change affect my business if I am not in the EU?
Yes. The change applies to all GA4 properties linked to Google Ads accounts globally, not just EU businesses. Any advertiser using cross-device reporting, remarketing audiences, or conversion tracking that relies on Google Signals data will be affected. GDPR risk is elevated for EU advertisers, but attribution and measurement impacts apply to accounts worldwide. If your GA4 property is linked to a Google Ads account, you need to complete the 7-step checklist above before June 15.
What is Consent Mode ad_storage and how do I check if it is set up correctly?
ad_storage is a Consent Mode parameter that controls whether Google Ads cookies and advertising identifiers can fire on your site. To check your setup: open Google Tag Manager, find your Consent Mode initialization tag, and verify that ad_storage defaults to denied before user interaction, then updates to granted after the user accepts via your CMP. Use Google Tag Assistant to test live consent signal behavior on your domain and confirm the sequence fires in the correct order.
What happens if I do not update my privacy disclosure before June 15, 2026?
Google requires all affected accounts to update their privacy disclosures within 90 days of the April 15 notification, making June 15 the effective deadline. Missing the disclosure update creates legal exposure under GDPR for EU advertisers and risks a policy violation from Google. The bigger operational risk: if your Consent Mode is misconfigured, you will lose attribution data and remarketing audiences with no Signals fallback to compensate, and you may not notice until campaign performance data starts diverging from expectations weeks later.
Originally published at mattkundodigitalmarketing.com
Top comments (0)