Sampling thresholds and cardinality interplay
Three GA4 mechanisms quietly limit what a report shows: sampling (when a query exceeds the event quota), data thresholds (privacy suppression of small groups), and cardinality limits (high-cardinality dimensions collapsing into an 'other' row). They have different triggers and effects, but in complex explorations they compound — so a report can be sampled, thresholded, and capped at once. This page untangles how they interact.
What this means
Sampling kicks in when an exploration query spans more events than the analysis quota, so GA4 computes from a subset and extrapolates. Data thresholds remove rows that could identify individuals in small, signal-bearing groups. Cardinality limits apply when a dimension has more unique values than GA4 will store per day, collapsing the rest into '(other)'.
Each has a different trigger — query size, privacy risk, dimension uniqueness — and a different fingerprint in the report.
How they compound
A wide, long-range exploration with demographic dimensions and a high-cardinality field can hit all three: sampled because of volume, thresholded because of demographics, and capped by '(other)' because of cardinality. The fixes differ — shorten the range or use standard reports to avoid sampling, drop demographic dimensions to ease thresholding, and reduce unique values to avoid the 'other' row.
- Sampling: query exceeds the event quota
- Thresholding: privacy suppression of small groups
- Cardinality: unique values collapse into (other)
- Complex reports can hit all three at once
How it appears in analytics and logs
Vague, incomplete, or non-reconciling reports can stem from any of three causes at once; identifying which is acting tells you whether to narrow the query, change dimensions, or reduce cardinality.
Diagnostic use case
Distinguish whether a report's missing or vague detail comes from sampling, thresholding, or cardinality so you apply the right remedy to each.
What WebmasterID can help detect
WebmasterID favors bounded, well-defined dimensions and aggregate reporting, reducing the cardinality and sampling pressures that obscure GA4 explorations.
Common mistakes
- Blaming sampling for what is actually thresholding.
- Ignoring the (other) row when reading high-cardinality dimensions.
- Running wide explorations that trigger all three limits.
Privacy and accuracy notes
Thresholding among these mechanisms is privacy-driven; sampling and cardinality are performance and storage limits. None should be defeated by re-identifying individuals. This page is educational.
Related pages
- Analytics sampling: when reports estimate
Sampling is when an analytics tool computes a report from a fraction of the data and extrapolates. It keeps big queries fast, but it adds estimation error — worst for small segments and rare events, where a few sampled sessions get scaled into a confident-looking number. Knowing when a report is sampled is the first defence.
- High cardinality and the (other) row
Every analytics tool has limits on how many distinct values a dimension can hold in a report. When a high-cardinality dimension — like full URLs or custom IDs — exceeds the limit, the overflow is bundled into an aggregate (other) row. Detail you expected vanishes into it, and totals look complete while breakdowns are not. This page explains the cause and the workarounds.
- Data thresholding in GA4
Data thresholding is a GA4 privacy mechanism: when a report could let someone infer the identity of individual users from low-volume rows (especially with Google Signals or demographics enabled), GA4 hides some data. The result is missing rows and report totals that do not reconcile. This page explains when thresholding applies and how to recognize it.
- Website Observability
Bounded dimensions that resist sampling and (other).
Sources and verification notes
Last reviewed 2026-06-24. Facts are checked against primary/official sources where available; uncertain specifics are marked “Data not yet verified” rather than guessed.