You open a GA4 report and see an orange triangle with an exclamation mark next to your data. The tooltip says something about "thresholding applied" or "data has been withheld to protect user privacy." Your numbers are incomplete — and there's no obvious explanation in the interface. Here's what's happening and what you can do about it.

What Is Thresholding?

GA4 applies thresholding — automatic data suppression — when a report contains dimensions that could theoretically identify individual users. When a particular combination of dimensions has fewer than a minimum threshold of users (Google doesn't publish the exact number, but it's typically around 50), GA4 removes that row from the report entirely to protect privacy.

The orange triangle appears at the report level when any rows have been removed. It does not tell you which rows were affected or by how much — only that some data is missing.

What Triggers Thresholding?

Thresholding is most commonly triggered by:

The Google Signals Fix

If thresholding is affecting your standard acquisition or conversion reports, the most effective fix is changing your Reporting Identity setting. Go to Admin → Property Settings → Reporting Identity and switch from "Blended" or "Observed" to "Device-based."

Device-based identity doesn't use Google Signals data for reporting, which removes the threshold requirement entirely for most report types. The trade-off: you lose cross-device user stitching and demographic data. For most properties, this is worthwhile — accurate session and conversion data is more valuable than demographic estimates.

Important: Keep Google Signals enabled even if you switch to Device-based reporting identity. Google Signals is still required for remarketing audiences and Consent Mode modelling. Only the Reporting Identity setting needs to change.

The Exploration Workaround

Standard GA4 reports are more prone to thresholding than Explorations. If you're seeing the orange triangle in Acquisition or Engagement reports, recreate the same analysis in Explore → Free Form. Explorations sometimes surface data that standard reports suppress, particularly for recent date ranges.

How GA4 Health Check Flags This

GA4 Health Check's Privacy & Compliance module checks your Reporting Identity setting and Google Signals configuration as part of the automated audit — flagging combinations that are likely to cause thresholding in standard reports. See the full list of checks in our comprehensive GA4 audit checklist. Run a 60-second audit to check your property's configuration.

Travis Gunn
Founder of GA4 Health Check. Working with Google Analytics since 2013, with over 250 clients audited across almost every industry vertical. 100% Job Success on Upwork for over a decade.