HomeGlossary › Google Signals
GA4 Architecture & Concepts

Google Signals

Google Signals is a GA4 setting that, once turned on, uses data from signed-in Google users who have enabled Ads Personalization. It gives GA4 three things it can't otherwise produce: cross-device tracking, demographic and interest data, and cross-device remarketing. In effect, it lets Google stitch together the same person across their phone, laptop, and tablet.

Why it matters

Without Google Signals, the age, gender, and interest reports in GA4 are largely empty, and a visitor who browses on mobile then converts on desktop looks like two different people. Turning it on fills in that picture. It also affects how GA4 counts users, because it improves de-duplication across devices — which is why your user numbers can shift after you enable it.

A concrete example

A consultant enables Google Signals and suddenly the demographics report shows that most of their readers are 35 to 54 and interested in business services. That data was always unavailable before — not because the visitors changed, but because GA4 had no way to identify them. The cross-device benefit also means a prospect who reads on their commute and books a call from their office desk now counts as one engaged user, not two.

The common misreading

People panic when demographic rows show "(thresholding applied)" or go blank, and assume Google Signals broke. It didn't. To protect individual privacy, GA4 withholds data when a segment is too small to anonymise — this is data thresholding, and it interacts closely with your reporting identity and consent mode settings. Missing rows usually mean low traffic, not a misconfiguration.

Settings like Google Signals quietly change your numbers. WebSignalytics watches for shifts that come from configuration rather than real behaviour — and explains the difference in plain language.

See how it works