What’s changing with Google Signals and Consent Mode this June?

Most Google Ads accounts are quietly running two consent controls at once, and most teams don’t realise it.

Right now, the collection of Google Ads cookies and IDs via the Google Analytics tag is controlled jointly by the Google Signals setting in GA4 and your Consent Mode Ads settings. One acts as a fallback for the other. That dual-control structure ends on 15 June 2026.

From that date, Google Analytics will transition to using Consent Mode (within Google Ads) as the single control for data. Your users’ privacy selections, managed via Ads Consent Mode settings, will exclusively govern how data is collected and used.

The change is framed as a simplification. In practical terms, it removes a safety net that many accounts have been relying on, sometimes without knowing it. This article covers what’s changing, who it affects, and what you need to audit before the deadline.

What is Google Signals, and what is changing on 15 June 2026?

Google Signals is a GA4 setting that associates your Analytics data with signed-in Google users. When enabled, it allows Google to use that data for cross-device reporting, remarketing audiences, and demographic insights inside your reports.

Until now, it has also served a second function: acting as a co-controller of whether Google Ads can collect advertising cookies and identifiers from your GA4 tag.

That dual role ends on 15 June 2026. After that date, the Google Signals setting in GA4 admin will retain only one function: controlling whether Analytics-sourced data is associated with signed-in user information for behavioural reporting.

Everything related to Google Ads data collection moves to Consent Mode.

What does Consent Mode actually control?

Consent Mode is the framework that tells Google tags how to behave based on a user’s cookie consent choices. It operates through four core parameters:

• ad_storage: controls whether advertising cookies and device IDs can be set
• ad_user_data: controls whether user data can be sent to Google for advertising purposes
• ad_personalization: controls whether data can be used for personalised ads
• analytics_storage: controls whether Analytics measurement cookies can be set

From 15 June, these parameters become more critical than ever. Previously, there was a dual-layer control structure with Google Signals. Now Consent Mode alone manages all Google Ads data flow.

Why is Google making this change?

Google’s stated rationale is to simplify data controls and remove redundant settings between Analytics and Ads. The principle is straightforward: data controls should live where the data is used. GA4 settings control behavioural reporting in GA4. Google Ads settings control data in Google Ads.

Until now, some of those controls were buried in Analytics settings rather than clearly surfaced in ad consent banners or tag implementations, which created confusion for marketers. Consolidating authority under Consent Mode is designed to give a single, consistent source of truth.

Whether that benefits advertisers or primarily benefits Google’s data collection is a question worth sitting with. The June 2026 change extends the logic Google established when it made Consent Mode effectively mandatory for EEA-facing accounts in July 2025, when non-compliant advertisers began losing conversion tracking, remarketing, and personalised ad functionality.

Who is affected by this change?

This change affects any organisation that has linked a GA4 property to a Google Ads account. That is standard practice for the vast majority of advertisers running paid search or display campaigns in the UK.

The degree of impact depends on how your Consent Mode is currently set up.

If you have Consent Mode v2 correctly configured

For those with Consent Mode v2 Advanced already properly configured and all four parameters active, the transition will be largely transparent. Consent Mode was already operating as the single control, so the removal of Google Signals from that role changes very little in practice.

That said, “correctly configured” is doing a lot of work in that sentence. It is worth verifying rather than assuming.

If you have Google Signals disabled in GA4

This is where the change has a less obvious consequence. Brands with Google Signals disabled must pay particular attention. Under the new setup, they may encounter increased Ads-linked data if users grant ad consent.

Previously, disabling Google Signals acted as a partial brake on data flowing into Google Ads, even if Consent Mode was permissive. From 15 June, that brake is gone. If a user grants ad_storage consent, Google Ads will use the full range of available signals regardless of what the Signals toggle says in GA4.

If your Consent Mode implementation is incomplete or incorrect

Consent implementations sending incomplete parameters will cause greater data loss, because Signals will no longer serve as a fallback. Gaps that were previously absorbed by the dual-control structure will now have direct consequences for measurement, attribution, and audience data.

The diagnostic tools Google provides carry a 48 to 72-hour detection latency for consent signal updates, meaning implementation issues can persist for up to three days before they register. That lag becomes more consequential when ad_storage is the only authority over advertising data collection.

If you are not running Google Ads

If your GA4 property has no Google Ads link, this change has no direct impact on your data collection. The Signals change concerns GA4 to Google Ads data flow specifically.

What does the binary consent decision mean for campaign performance?

One of the more significant practical consequences of this change is how little room it leaves for nuance. Under the new structure, the outcome of a user’s consent decision is effectively all or nothing.

As tracking expert Simo Ahava noted: “There’s no middle ground here. Either grant ad_storage and Google will use all available ads signals at their disposal (including linking the user with their Google sign-in), or set it to denied and Google will not access any identifiers apart from what’s available in the URL.”

In practical terms, that means two very different data environments depending on what your users click on the cookie banner.

When ad_storage is granted

If ad_storage is granted, Google Ads may use all available advertising signals, including linking activity to a user’s signed-in Google account when possible. That includes cross-device data, audience membership, and demographic signals that feed into Smart Bidding and Performance Max campaigns.

For accounts that rely heavily on audience targeting or automated bidding strategies, this is the data environment those systems are optimised to work within.

When ad_storage is denied

If ad_storage is denied, Google will be limited to less persistent signals, such as URL parameters like gclid. Conversion modelling via Consent Mode will still operate, but the richness of the data feeding attribution and audience lists is significantly reduced.

The consequence is not just a reporting gap. Smart Bidding algorithms depend on signal quality. Thinner data means slower learning, less accurate bid optimisation, and audiences that are harder to build and maintain.

What this means for measurement and attribution

From June, whether Google Ads can use identifiers will depend almost entirely on the ad_storage signal, so any gaps or errors in Consent Mode setup could directly affect campaign performance data.

This is worth framing clearly for clients and stakeholders. It is not a technical compliance exercise in isolation. It is a measurement infrastructure decision with a direct line to reported ROAS, conversion volume, and audience reach.

What should you audit before 15 June 2026?

With less than two months until the deadline, the priority is verifying your Consent Mode implementation is accurate, complete, and firing correctly. Here is what to work through.

1. Confirm Consent Mode v2 is implemented

Consent Mode v2 is the current required standard. It introduced ad_user_data and ad_personalization as parameters alongside the original ad_storage and analytics_storage.

If your implementation predates March 2024, there is a reasonable chance it is running v1 only. Check with your developer or tag management team that all four parameters are present and updating correctly based on user consent choices.

2. Verify your CMP is sending correct signals

Your Consent Management Platform (CMP) is the tool that presents the cookie banner and passes consent signals to your tags. A CMP that is integrated but misconfigured can send incomplete or incorrect parameter states without any visible error.

The fastest way to verify your CMP’s consent default and update signals is the InfoTrust Consent Mode Inspector Chrome extension. It displays the state of all four parameters on page load without needing to open DevTools.

Check both the default state (what fires before a user makes a choice) and the update state (what fires after they accept or decline).

3. Check ad_storage behaviour against your consent rate data

Pull your consent acceptance rates from your CMP dashboard and cross-reference them against the volume of ad_storage: granted signals firing in GA4. If those numbers are materially out of step, your implementation has a gap.

Confirm that Consent Mode update calls are firing correctly and that ad_storage settings accurately reflect user choices. This is the single most important check before 15 June.

4. Review your Google Signals settings with fresh eyes

If you have Google Signals disabled in GA4 and have been treating that as a data-sharing control for Ads, that assumption no longer holds from 15 June. Revisit why Signals was disabled and whether your Consent Mode configuration now covers what you intended Signals to protect.

5. Establish a pre-June reporting baseline

Verifying that your CMP sends correct signals and establishing a pre-June reporting baseline is good practice. Document your current conversion volumes, audience sizes, and attribution data now. If something shifts after 15 June, you need a clean reference point to diagnose whether it is a consent issue, a campaign issue, or a reporting artefact.

6. Flag incomplete implementations for immediate remediation

Any incomplete or incorrectly configured Consent Mode implementation will have a direct impact on your Google Ads data once Signals no longer serves as a fallback. If your audit surfaces gaps, they need fixing before the deadline, not after.

If your paid media setup needs a full review ahead of June, our team works across Google Ads consent infrastructure, tracking architecture, and campaign performance. See how we approach paid media.

Conclusion

Google is not asking advertisers to do anything unreasonable here. Consent Mode has been the recommended standard for EEA and UK advertisers for some time. What changes on 15 June is the consequences of getting it wrong.

The removal of Google Signals as a co-controller takes away a layer of redundancy that many accounts have been quietly relying on. From that date, ad_storage is the single authority over whether Google Ads can collect and use advertising identifiers. There is no fallback, and there is no middle ground.

The practical steps are clear:

• Verify Consent Mode v2 is fully implemented with all four parameters
• Confirm your CMP is sending correct signals on both default and update states
• Cross-reference consent acceptance rates against ad_storage granted signals
• Establish a reporting baseline before 15 June so you can isolate any post-change movement

For most well-configured accounts, this transition will be uneventful. For accounts with gaps, it will show up in measurement, attribution, and audience data before anyone has had a chance to investigate why.

If you want a second pair of eyes on your consent setup or your broader paid media tracking architecture, get in touch with the Roar team.

Frequently Asked Questions

What is changing with Google Signals on 15 June 2026?

From 15 June 2026, Google Signals will no longer control whether Google Ads can collect advertising cookies and identifiers from your GA4 tag. That authority moves exclusively to Consent Mode, specifically the ad_storage parameter managed within Google Ads. Google Signals will continue to exist, but its role narrows to controlling signed-in user data for behavioural reporting inside GA4.

Does this affect me if I am not running Google Ads?

No. This change specifically concerns the data flow between GA4 and linked Google Ads accounts. If your GA4 property has no Google Ads link, your data collection and reporting are unaffected by this update.

What happens if my Consent Mode implementation has gaps after 15 June?

Any incomplete or incorrectly configured Consent Mode implementation will have a direct impact on your Google Ads data. Without Google Signals acting as a fallback, missing or incorrect parameters mean Google Ads loses the ability to collect advertising identifiers for users where consent status is unclear. That affects conversion tracking, audience building, and Smart Bidding signal quality.

What is the difference between Consent Mode v1 and v2?

Consent Mode v1 introduced ad_storage and analytics_storage as the two core parameters. Consent Mode v2, which became the required standard in March 2024, added ad_user_data and ad_personalization. If your implementation predates that update, it is likely running v1 only and will need upgrading before the June deadline.

Will disabling Google Signals still protect my data after 15 June?

Not in the way it does today. Currently, disabling Google Signals in GA4 acts as a partial brake on data flowing into Google Ads. From 15 June, that is no longer the case. If a user grants ad_storage consent, Google Ads will use the full range of available advertising signals regardless of what your Signals setting says in GA4.

How do I check whether my Consent Mode is working correctly?

The most straightforward method is the InfoTrust Consent Mode Inspector Chrome extension, which shows the state of all four Consent Mode parameters on page load without requiring DevTools access. Cross-reference those results against your CMP’s consent acceptance rate data to confirm signals are firing accurately and consistently.

What should I do if I find issues before the deadline?

Prioritise fixing any incomplete parameter implementations first, as these carry the highest risk after 15 June. Then verify your CMP integration and confirm that ad_storage signals accurately reflect your users’ actual consent choices. If you need support auditing your consent setup or paid media tracking architecture, our team is available to help.