Google Signals and Consent Mode in GA4: The 2026 Update Every Marketer Needs to Read
Google Signals in plain terms
Google Signals connects the activity of the same visitor across phones, tablets, and desktops. It only works when that visitor is signed into a Google account with Ads Personalisation switched on.
Without Google Signals, one person browsing on two devices shows up as two users. With it, the report reflects one journey.
Consent Mode in plain terms
Consent Mode is the layer that reads the visitor's cookie choices and passes them to Google's tags. It uses four signals: ad_storage, analytics_storage, ad_user_data, and ad_personalization. A tested Google Consent Mode v2 banner from Seers maps these four in the right order without manual code.
What changed on 15 June 2026
Before the change, disabling Google Signals also stopped Google Ads data flow. That link is gone. Google Signals now only enriches GA4 reporting. The ad_storage consent signal is the only control that decides if ad data reaches Google Ads.
For teams that used Google Signals as a compliance safeguard, that safeguard is now inside Consent Mode. If the CMP is misconfigured, ad data can flow even when it should not.
Why this matters
Reports will read differently after the switch. Behavioural modelling in GA4 needs 1,000 daily denied events and 1,000 daily granted users to activate. Sites below that threshold lose visibility on denied users entirely.
Privacy notices that mention Google Signals as an ad data control are now outdated. Marketing, legal, and analytics teams need to align.
A simple next step
Book a CMP audit this month. Confirm the four consent signals default to denied and only move to granted after banner accept. A full walk-through is on the Seers guide to GA4 Consent Mode and Google Signals, and their wider compliance work sits at seers.ai.
.png)
Comments
Post a Comment