GA4 hides your smallest segments behind (other).
- “ga4 showing other instead of data”
- “ga4 data thresholding applied”
- “why is ga4 hiding my data”
Diagnosis
GA4 is not losing the data. It is withholding it. When a report could single out an individual, GA4 applies data thresholding: it rolls the small rows up into (other) or drops them, and the visible numbers stop summing to the total. It kicks in when Google Signals is on and a row’s user count is too low to stay anonymous. The hits are collected in full. The report just refuses to show them at that grain.
This is not sampling. Sampling is what happens to a large or complex query that exceeds a processing quota, mostly in Explorations. Thresholding is a privacy rule on small counts. Same complaint of “missing data,” two unrelated causes, two different fixes.
| SOURCE / MEDIUM | BLENDED (Signals) | DEVICE-BASED |
|---|---|---|
| google / organic | 4,210 | 4,210 |
| newsletter / email | (other) | 38 |
| partner-x / affiliate | (other) | 22 |
The newsletter and affiliate rows were there the whole time. The Blended view, which leans on Signals, rolled them into (other) to protect a handful of users. Device-based reporting does not, so they come back.
Where it shows
A (other) row in a breakdown, a “data threshold applied” note above a report, or named rows that will not add up to the total. Explorations are more prone to it than the standard reports, and the smaller the segment, the more likely it disappears. The tell: the data is fine in aggregate and only goes missing when you drill down.
℞ The fix
- Switch the report’s reporting identity to Device-based. In Admin, set reporting identity to Device-based instead of Blended or Observed. Device-based does not use Google Signals, so the thresholding that Signals triggers does not apply. You trade some cross-device and demographic detail for rows you can actually see.
- Pull the raw data from BigQuery. The GA4 BigQuery export is event-level, unsampled and unthresholded. For any report where the hidden rows matter, query the export instead of the UI.
- Widen the range or coarsen the breakdown. Thresholding hits low counts. A longer date range, or one less dimension in the breakdown, often lifts the row back over the threshold.
Thresholding is a privacy feature doing its job, not a bug. The fix is not to defeat it, it is to ask GA4 the question in a form it is allowed to answer. If the totals themselves look wrong, rather than just the breakdowns, that is a different problem, and it is filed under R-501 .