.svg)
If you’ve been noticing notifications pop up in your Google Analytics or Tag Manager accounts lately, it’s a good time to take a closer look.
Google is rolling out a significant update to its data infrastructure. If you rely on digital marketing to find new customers, optimise your bidding, or build remarketing audiences, this change will alter how your campaigns collect data behind the scenes.
Here is a straightforward breakdown of what is changing, how it looks in your dashboard, and how to update your setup smoothly before the deadline.
Essentially, regulatory requirements, particularly across Europe and the UK, require tech platforms to obtain explicit user consent before data is used for advertising. To meet these standards, Google is shifting how it processes this information.
Historically, advertisers had a bit of a safety net. If a website's cookie banner wasn't perfectly aligned with Google's technical requirements, an admin feature within Google Analytics 4 called Google Signals could often bridge the gap. When enabled, Signals allowed Google to utilise logged-in account data to help fill in the blanks for cross-device tracking and audience building.
That architecture changes on June 15, 2026.
According to Google's official documentation, they are separating these features to simplify how data flows to specific destinations. Moving forward, the Google Signals toggle will only apply to internal GA4 behavioural reporting. It will no longer serve as a backup for Google Ads data.
From June 15th, explicit consent captured directly on your website becomes the sole standard for powering your ad tracking.
Google isn't treating this like a policy violation, so you won't see flashing red emergency banners on your main Google Ads overview page. Instead, the notifications are tucked away where the data is actually managed.
First, you can find alerts in the GA4 Admin Section. If you log into Google Analytics 4 and go to Admin, then Data Collection and Modification, and finally Data Collection, you will see an information banner right next to the Google Signals toggle explaining the upcoming data separation.
Second, check the Tag Diagnostics Tab. Inside Google Tag Manager or your Google Tag settings, you may see a yellow warning status like "Consent missing" or "Incomplete Consent Setup" if your site isn't passing parameters correctly.
The catch is that these diagnostic tools suffer from a 48 to 72 hour reporting lag. If your setup isn't working on June 15th, the UI won't alert you instantly. Instead, you'll simply see your reported conversion numbers start to drift downward a few days later.
Without the backup support of Google Signals, a standard tag implementation won't be enough to keep everything running smoothly. If Google doesn't receive specific consent data directly from your site's code, it will default to a highly restricted tracking mode.
If your consent framework isn't updated by the June 15th deadline, expect gaps in three key areas.
Your audience lists will shrink. Remarketing lists that depend on cross-device tracking will face drops in volume. If the specific ad_storage and ad_personalization parameters aren't explicitly granted by the user and passed by your site, Google Ads cannot add those users to your audiences.
You will also have less data for Smart Bidding. Google’s automated bidding strategies rely heavily on steady conversion data to optimise your spend. If conversion tags lack the proper consent parameters, the algorithm has less information to work with, which can lead to fluctuations in your cost per acquisition.
Finally, you will face gaps in reporting. Your campaigns will still run, but your dashboard reporting will likely show a drop in tracked conversions. This makes it much harder to see exactly which keywords or creatives are actually driving business.
The good news is that updating your setup is completely manageable, and getting ahead of it ensures your data remains accurate.
If you are using an older or completely custom cookie pop-up, it might not be communicating correctly with Google's systems. Switching to a Consent Management Platform that is officially certified by Google is often the easiest fix. Choosing a certified provider ensures the framework is built to talk to Google's tags automatically in the required technical language.
Your development team or web administrator can usually implement this via Google Tag Manager. You need to ensure your website passes two specific parameters alongside your existing tags, which are ad_user_data and ad_personalization.
A basic implementation means tags remain completely blocked until a user explicitly clicks "Accept." This is straightforward but means you won't collect any data from users who opt out.
An advanced implementation means tags load in a default "denied" state. If a user declines tracking, the site still sends anonymous, cookieless pings to Google. Google can then use behavioural modelling to help estimate your missing conversion data, keeping your reports more accurate.
You can easily test the setup yourself before the deadline. Open Google Tag Manager, launch Preview mode, and visit your site. Look at the "Consent" tab for your main Google Ads tags. When you accept the banner, ad_storage and ad_personalization should update to granted. If you reject it, it should read denied.
These updates represent a broader shift toward a privacy-first web, and Google is adapting its tools accordingly.
By ensuring your cookie banner is certified and your tracking tags are passing the correct consent signals, you can protect your data continuity and keep your campaigns running smoothly past June 15th. It takes a little technical maintenance upfront, but it keeps your marketing strategy on solid ground.
Back to hub
