Google Signals gives GA4 access to additional demographics and interest data from signed-in Google users who have Ads Personalization enabled. It can improve some audience and reporting use cases, but it can also introduce thresholding in affected reports and should be reviewed carefully for privacy-sensitive regions.
What Google signals provides
- Cross-device reporting support: For signed-in Google users with Ads Personalization enabled, Signals can help Google connect activity across devices for supported use cases.
- Demographics and interests: GA4 can show age, gender, and interest data in aggregate reports where Signals-supported data is available.
- Advertising use cases: Signals can support certain remarketing and ads-related capabilities, which is why it should be reviewed with both privacy and media teams.
The data thresholding consequence
Google documents that thresholding can limit reports and explorations when demographics, interests, or other signals-sensitive data could make individuals easier to infer. When that happens, GA4 shows a data quality indicator explaining that thresholding has been applied.
This usually shows up first in demographic reporting, where visible rows may not sum neatly to the total. The right takeaway is not that the property is broken. The takeaway is that the report has privacy protections that reduce visibility for low-volume segments. Read ourGA4 sampling and thresholdsguide for the full picture of how the platform applies these protections.
Want to check whether thresholding is affecting your GA4 property?
GDPR considerations
For EEA and UK users, Signals should be reviewed as part of the wider privacy and consent design. It may require a different legal and disclosure review than basic analytics collection. Implementation guidance can support that review, but it is not a substitute for legal advice. OurGDPR and GA4 compliance guidecovers the broader configuration tradeoffs to factor in.
If your organisation keeps Signals enabled in regulated regions, verify that the consent experience, internal policy, and technical behavior still align. Pair this with deliberateGA4 data retention settingsso the property does not store more than the consent design intended.
When to enable Google signals
- Primary audience is signed-in Google users with consent covering cross-device tracking
- Google Ads remarketing campaigns benefit from larger audience pools
- Demographic reporting is actively used and legally compliant
Signals is one of the higher-impact toggles you will encounter when going through a widerGA4 property configuration check.
When to disable Google signals
- Thresholding causing significant gaps in demographic or interest reports
- EEA/UK traffic significant and Signals processing not covered by consent
- Precise session and user counts more important than cross-device merging
Google signals audit action plan
Use this plan to validate your current Signals configuration and correct any issues.
Validate
- Check whether thresholding is occurring: open a Demographic Detail report and compare the sum of visible rows to the total, a gap means rows are being suppressed
- Look for the GA4 data quality indicator, which documents when thresholding is being applied
- Confirm whether Google Ads remarketing audiences depend on Signals-enriched data before disabling
- Review Admin > Data collection and modification > Reporting identity to see whether Blended or Device-based is active
Fix
- If thresholding is causing significant data gaps and remarketing is not the priority, disable Google Signals in Admin > Data Collection
- Review whether reporting identity should be changed if your reporting use case prioritises less modeled, less threshold-prone outputs
- For EEA/UK properties, confirm Signals behavior against your consent and legal review rather than treating it as a default-safe setting
- If Signals is needed only for a narrow use case, document that scope so teams do not overuse the resulting reports
Watch for
- Demographic report totals that do not match broader user totals, which can be normal under thresholding
- Teams exporting demographic reports as if they were complete segment counts
- Signals staying enabled by inertia even though the business no longer uses the related audiences or reports
Google signals checklist
- Signals status reviewed intentionally, not accepted as default
- Thresholding impact assessed by comparing demographic report totals to standard report totals
- For EEA/UK properties, Signals behavior reviewed alongside consent and legal requirements
- Reporting Identity aligned with whether Signals is enabled
Related guides to read next
GA4 Session Counting Explained
How GA4 counts sessions differently from Universal Analytics and what that means for your data.
Consent Mode v2 Guide
How to implement Consent Mode v2 correctly and what happens to your data when consent is denied.
GA4 Sampling and Thresholds
Understanding when GA4 applies sampling and thresholding and how to work around both.
GA4 Property Configuration Checks
The full list of property-level settings to review on every GA4 audit.
Check your Google signals configuration automatically
GA4 Audits helps surface Signals status, reporting identity choices, and related configuration checks so teams can review the tradeoffs with evidence.