Google Signals in GA4: What It Does and When to Enable It
Google Signals is one of the most misunderstood settings in GA4. It unlocks valuable cross device and demographic reports, but it also introduces data thresholds that suppress data in smaller segments. Knowing whether to enable it, and what to expect when you do, depends on your reporting needs and audience size.
What Google Signals does
Google Signals enriches GA4 data with cross device user journey information for users who are signed in to their Google accounts and have Ads Personalisation enabled.
When Signals is on, GA4 can recognise when the same user visits your site from their phone and their laptop, and count them as one user rather than two.
It also enables demographic reports (age, gender) and interest category data derived from Google's advertising profile. These come from Google's own data, not from anything you collect directly.
The data requires a minimum threshold of users before GA4 will display it, segments too small are suppressed and shown as "(other)".
The data thresholds problem
Enabling Signals introduces data thresholds in reports that break down by demographic dimensions. When a dimension combination (e. g.
, "35-44 / Female / London") contains fewer users than Google's minimum threshold, that row is suppressed and its data rolled into an "(other)" bucket.
For sites with lower traffic volumes or narrow audiences, enabling Signals can cause a significant portion of data to disappear into "(other)".
If you're auditing a GA4 property and see a large "(other)" row in audience segment reports, check whether Signals is enabled, it's the most common cause.
When to enable it and when not to
Enable Signals if: you have significant traffic volume (100K+ monthly sessions), you need cross device user counts, or you want to build GA4 audiences for remarketing to signed in Google users.
The cross device user count improvement is most meaningful for businesses where the same users often switch between devices.
Consider leaving it off if: your traffic is heavily niche and low volume, you use GA4 primarily for high cardinality segment analysis (where thresholds will suppress too much data), or your privacy policy and consent framework don't cover the additional data enrichment.
Audit your property to verify whether Signals is currently set correctly for your use case.
Ready to audit your GA4 property?
Run a full GA4 audit in under 10 minutes. Free to start.
Start Free Audit