"Data may be withheld": GA4 thresholding, explained
You open a GA4 report, see an orange icon and a row that should have numbers sitting blank. GA4 has withheld it. The data exists, Google is just refusing to show it, and the cause is usually one setting.
What thresholding is
To stop anyone being identified from small numbers, GA4 suppresses rows where counts are low enough that, combined with demographics or signals, a person might be re-identified. It shows a threshold icon instead of the value. Nothing is lost, it is withheld in that view.
Why small businesses hit it constantly
Thresholding kicks in mainly when Google Signals is enabled (it adds demographic/identity data), and low-traffic sites cross the low-count line all the time. So the businesses most desperate for every data point are the ones most often blocked from seeing it.
How to get your rows back
- Switch the reporting identity to Device-based (Admin, Reporting identity) to sidestep much Signals-driven thresholding.
- Reconsider whether you need Google Signals on at all for your use case.
- Widen the date range so counts clear the threshold.
- Use the BigQuery export, which is not thresholded.
There is a real trade-off here between demographic reporting and seeing your own small numbers. Choosing the right setting for your business is a five-minute fix once you know it exists.
Want us to check your tracking in 10 seconds?
Pop in your domain and we will show you what is firing, what is not, and where data is leaking. Free, no signup.
Check my tracking freeGet a plain-English audit
We check your live GA4, Google Tag Manager and consent setup by hand and tell you exactly what is wrong. The audit comes off any build.
See how it works & pricingDatahound are analytics and ad-tracking specialists. We fix broken GA4, Google Tag Manager and server-side tracking so every sale, form and call gets counted. Back to datahound.agency · All tracking guides · The (other) row in GA4