Anyone who runs Google Ads and uses Google Analytics was handed a change in June 2026 that is easy to miss: since 15 June it has no longer been the Google Signals toggle but Consent Mode that decides whether Google Ads cookies and IDs are collected. For many SMEs this is not a disaster – but it is a good reason to review their own tracking.

1. What Google Has Changed – in One Sentence
Until now there were two levers: the Google Signals toggle in Google Analytics and Consent Mode on your website. Since 15 June 2026 the division of tasks has been clearer – and, for Ads data, stricter: Consent Mode is the only control for whether Google Ads cookies and IDs are collected.
The Google Signals toggle is not disappearing. But it now only controls whether Analytics data is linked with information from signed-in Google users for behavioural reporting – that is, for reports and demographic analyses. It no longer works as a privacy brake for Google Ads.
In short: If you had switched Google Signals off to limit the flow of data to Google Ads, you can no longer rely on that. What matters now is that your Consent Mode works correctly.
2. Before and After at a Glance
The following overview compares how the data flows were controlled before and after the changeover. It is a simplified representation of the information in Google Analytics Help.
Simplified representation based on information in Google Analytics Help. As of 30 September 2026.
3. What the Google Signals Toggle Still Does
Google Signals remains relevant for one particular area of use: linking Analytics data with information from signed-in users for behavioural reporting. If you use demographic reports or cross-device analyses, you should check whether the toggle fits your data protection policy.
What is new is the separation of responsibilities: the toggle answers the question “How is Analytics data evaluated?”, no longer “Do cookies and IDs flow towards Google Ads?”. That second question is the job of Consent Mode.
4. Consent Mode: The Central Control for Ads Cookies and IDs
According to Google and to analyses by specialist sources such as Usercentrics and PPC Land, Consent Mode (in combination with Google Ads) decides whether advertising cookies and device IDs are collected. Specialists point above all to the ad_storage signal here. If a visitor rejects advertising cookies, that route stays closed.
In practice this means that your Consent Mode implementation carries more responsibility than it used to. According to PPC Land, the analytics expert Simo Ahava points out that the change puts more pressure on the Consent Mode implementation: the update calls must be made correctly and contain the right signals.
On a related note: in our article Cookieless & Consent Mode v2: staying measurable we explain how you stay measurable whatever your consent rate.
5. Where Things Can Go Wrong in Practice
Three situations deserve a second look on SME websites, particularly with visitors from the EU and the UK:
No Consent Mode in Use
Without Consent Mode, tags work with their default settings. Usercentrics classes this situation as the highest risk.
Wrong Default Values
If the default values are not set to “denied” before the user decides, data can flow towards Google Ads without valid consent. This site, too, sets the default values to “denied” before the Tag Manager loads – that is exactly the order you should check on your own site.
Banner and Technology Do Not Match
Your cookie banner must pass the visitor's decision on to Google in real time, and your privacy policy should describe the data flow between Analytics and Ads correctly. According to PPC Land, errors sometimes only show up in the tag diagnostics after up to 72 hours – so test actively rather than waiting.
6. What Else Follows Later in 2026
Google has announced two further steps. First, for properties linked to Google Ads, the ad_personalization signal alone is to determine whether Analytics data is used for personalisation in the Ads account. The help page does not yet give an exact date for this.
Second, IP addresses collected automatically by the Google tag and SDK are to flow in encrypted form to the linked Google Ads account. Google intends to publish details later in the year. We did not find any final dates in our research; you should therefore check the current status in the official Analytics Help.
For measurement as a whole it is also worth looking at server-side tracking and, if your figures fluctuate anyway, at our article on wrong GA4 figures.
7. Checklist: What SMEs Should Check Now
8. Conclusion: It Is Consent That Protects, Not the Toggle
The change looks small technically, but it shifts the responsibility: a toggle in Analytics is no longer a safeguard for Ads data. Whether cookies and IDs flow is decided by your visitors' consent – and therefore by the quality of your Consent Mode implementation.
Our assessment: for SMEs this is an opportunity to check the foundations of their tracking thoroughly for once. Those who align banner, Consent Mode and privacy policy with one another protect themselves legally and keep reliable data for Google Ads. This article is not a substitute for legal advice.
Also read: Google Ads: offline conversions and 7-day attribution.
9. FAQ: Google Signals and Consent Mode
What did Google change in Google Analytics on 15 June 2026?
Since 15 June 2026, the Google Signals toggle in the Analytics admin area has only controlled whether Analytics data is linked with information from signed-in users for behavioural reporting. Whether Google Ads cookies and IDs are collected is governed by Consent Mode alone.
Do I have to change anything in Google Analytics now?
Google does not name any mandatory action on its help page. A check is sensible all the same: is Consent Mode integrated cleanly, are the default values set to “denied” before consent, and does your cookie banner report the user's decision back to Google correctly?
What if I had Google Signals deactivated until now?
Then you were able to use it to slow the flow of data to Google Ads. That additional brake no longer applies. Whether Ads cookies and IDs are collected now depends on the visitor's consent and on your Consent Mode implementation.
Have ad personalisation and IP addresses already been switched over?
Google has announced that later in 2026 the ad_personalization signal alone will determine whether Analytics data is used for personalisation in a linked Ads account. For IP addresses, Google will only give further details later. Check the current status in Analytics Help.