On this page
- What it was
- The pre-2026 architecture — dual-lock control
- February 2024 — first demotion
- June 15, 2026 — the second demotion
- Further change later in 2026 (date TBD)
- Post-June 2026 architecture
- Ecommerce implications
- Remarketing audience decay
- Smart Bidding signal degradation
- Modeled conversions mask early damage
- Consent Mode misconfiguration exposure
- Privacy policy accuracy
- Google Analytics properties without Google Ads link
- Contradictions
- Key terms
Google Signals
Google Signals
Google Signals is a Google Analytics 4 feature that associates GA4-collected behavioral data with signed-in Google account information — enabling demographics/interests reporting and cross-device session stitching for users who have Ads Personalization enabled. As of June 15, 2026, its scope was significantly narrowed: it no longer controls whether Google Ads cookies and identifiers are collected; that authority passed entirely to Google Consent Mode v2's ad_storage parameter.
What it was
Google Signals was an opt-in GA4 property-level feature — not active by default — that used signed-in Google account data and Ads Personalization consent to stitch cross-device sessions together, matching a single user's behavior across phone, laptop, and tablet (MeasureU, 2026-06-10). When enabled, it unlocked three capability categories: cross-device reporting, enriched demographics/interests data, and advertising features including remarketing audience sharing with Google Ads (MeasureU, 2026-06-10).
Data originated from users who (a) were signed into a Google account and (b) had Ads Personalization turned on; it could additionally draw on location history, search history, YouTube history, and Google partner-site data (MeasureU, 2026-06-10). Signed-in user data collected via Signals expired after 26 months by default, subject to the property's Data Retention setting (as-of 2026-09-26; Google Analytics Help Center, answer/9445345).
The pre-2026 architecture — dual-lock control
Before June 15, 2026, two settings jointly controlled whether Google Ads cookies and IDs collected via the GA4 tag and Firebase SDK were used in Google Ads: the Google Signals toggle in GA4 Admin, and the Consent Mode ad_storage signal. Both had to permit tracking for the full advertising signal to flow — they acted as a dual lock (Usercentrics, 2026-06-23). Turning off Google Signals alone was sufficient to prevent advertising data from reaching Google Ads, regardless of ad_storage state (Seresa, 2026-05-27).
February 2024 — first demotion
In February 2024, Google removed Google Signals from the GA4 reporting identity hierarchy, meaning Signals identifiers no longer influenced how GA4 deduplicated users in standard reports and Explorations (MeasureU, 2026-06-10). Signals data continued to be used for advertising audiences and demographics reporting through to June 2026.
June 15, 2026 — the second demotion
On June 15, 2026, Google completed the separation: Consent Mode's ad_storage parameter became the sole authority over Google Ads cookie and ID collection (as-of 2026-09-26; Google Analytics Help Center, answer/17016975). The Google Signals toggle now governs only the association of GA4-sourced data with signed-in user information for behavioral reporting — demographics, interests, and cross-device journey stitching within GA4 (Google Analytics Help Center, answer/17016975). It no longer gates any Google Ads data flow (Piwik PRO, 2026-04-24).
Turning off Google Signals no longer stops data from flowing into Google Ads. If ad_storage is granted via Consent Mode, advertising features — including cross-device user recognition — proceed regardless of what the Signals toggle says (Piwik PRO, 2026-04-24).
Google's stated rationale: "simplify data controls and remove redundant settings between Google Analytics and Ads, so that for linked properties Google Ads settings exclusively control Ads data while GA settings exclusively control data used within GA for behavioral reporting" (Google Analytics Help Center, answer/17016975).
Further change later in 2026 (date TBD)
Google announced that ad_personalization will separately take over remarketing authority from GA4 in a second phase — moving ads personalization settings from GA4 to Google Ads entirely (as-of 2026-09-26, date unconfirmed). IP addresses auto-collected by the Google Tag and SDK will be encrypted and flow to the linked Google Ads account rather than staying in GA4 (Dataslayer, 2026-04-22).
Post-June 2026 architecture
After June 15, 2026, the two destinations operate under independent controls (Usercentrics, 2026-06-23):
| Destination | Gate |
|---|---|
| Google Analytics behavioral reporting (demographics, interests, cross-device stitching) | Google Signals setting / allow_google_signals API |
| Google Ads (remarketing, conversion tracking, Smart Bidding signals) | Consent Mode ad_storage |
| Enhanced Conversions / Customer Match | Consent Mode ad_user_data |
| Remarketing / similar audiences (phase 2, TBD 2026) | Consent Mode ad_personalization |
GA4's GA4 Attribution|Reporting Identity — controlling cross-device user-journey stitching in standard reports — uses three identity spaces (User-ID, Device ID, and Modeling) and does not depend on Google Signals (Google Analytics Help Center, answer/10976610). Google Analytics uses behavioral modeling to fill measurement gaps for users who decline cookies, using data from similar consenting users; this modeling capability is separate from Google Signals and continues post-June 2026 (Google Analytics Help Center, answer/10976610).
Ecommerce implications
Remarketing audience decay
Remarketing lists stop growing the moment a denied state is recorded, but existing audience members do not vanish — they age out over the membership window. A 540-day cart-abandoner list keeps performing for months while quietly bleeding new entries; the CPA looks fine until the list is too small to spend against (Notice Me Senpai, 2026-05-06, citing practitioner analysis).
Smart Bidding signal degradation
Smart Bidding loses signal in proportion to the drop in ad_storage-granted users; audience lists that appeared stable because Signals was silently providing cross-device reach will shrink without any error appearing in the dashboard (Seresa, 2026-05-27).
Modeled conversions mask early damage
Practitioner analysis warns that modeled conversions cover the first 4–6 weeks of signal degradation reasonably well, then the model loses confidence and reports get noisy — meaning a misconfiguration on June 15 may not visibly manifest in CPA until August 2026 (Notice Me Senpai, 2026-05-06).
Consent Mode misconfiguration exposure
Secure Privacy research (2026) found 67% of Consent Mode v2 implementations contain technical errors, with the most common error defaulting parameters to granted before the user makes a choice (as-of 2026, via Seresa). Teams that had turned Google Signals off as a privacy safeguard against ad data sharing were relying on a control that, after June 15, no longer performs that function (MeasureMinds, 2026-04-23).
One documented misconfiguration case saw conversions drop 90% overnight when consent signals stopped firing in the correct order; approximately 40% of lost attribution data recovered through modeled conversions and Enhanced Conversions backfill, with the other 60% unrecoverable (PPC Land / Jerry Bierenbroodspot, via Notice Me Senpai, 2026-05-06).
Privacy policy accuracy
Privacy policies and cookie notices that cited Google Signals as the mechanism controlling Google Ads data became inaccurate after June 15, 2026, and require updating to reference Consent Mode and ad_storage instead (MeasureMinds, 2026-04-23).
Google Analytics properties without Google Ads link
Google Analytics properties not linked to Google Ads are unaffected by the June 15 change (Dataslayer, 2026-04-22).
Contradictions
"Retired" vs. "demoted": Multiple practitioner sources published April–June 2026 (MeasureMinds, Dataslayer, Usercentrics, Piwik PRO) use language like "retired" or "deprecated" for Google Signals. Google's own Help Center (answer/17016975, retrieved 2026-09-26) and post-June analysis (Usercentrics, 2026-06-23) clarify that Signals was not switched off entirely — it was demoted to a behavioral-reporting-only role within GA4. The Seresa (2026-05-27) and Usercentrics posts are the most precise on this distinction.
Compliance framing: Piwik PRO (a direct GA4 competitor, 2026-04-24) characterizes the June 2026 change as increasing GDPR compliance risk by bundling cross-device tracking into a single ad consent signal without user granularity. Usercentrics (a CMP vendor, 2026-06-23) characterizes the same change as a technical simplification that makes compliance clearer, provided Consent Mode is correctly implemented. The underlying factual claims about the architecture are consistent; the compliance-risk framing diverges.
Key terms
| Term | Meaning |
|---|---|
| Google Signals | GA4 property-level feature associating behavioral data with signed-in Google account data; now governs behavioral reporting only |
ad_storage | Consent Mode parameter; sole gate for Google Ads cookie and ID collection post-June 2026 |
ad_user_data | Consent Mode parameter; gates Enhanced Conversions and Customer Match |
ad_personalization | Consent Mode parameter; to take over remarketing authority in phase 2 later 2026 |
analytics_storage | Consent Mode parameter; gates GA4 analytics cookie storage |
| Reporting Identity | GA4 setting controlling cross-device user-stitching: Blended / Observed / Device-based |
| Behavioral modeling | GA4 ML-based gap-fill for non-consenting users, using similar consenting users' patterns |