Sampling in explorations
GA4's Explore module samples differently from standard reports. When an exploration's query exceeds an event-count quota for the date range, GA4 analyses a representative subset and scales the results, flagging the sampling level. Deep, wide, or long-range explorations are most exposed. This page explains when Explorations sample and how to read the sampling indicator.
How Exploration sampling works
Standard GA4 reports are mostly unsampled because they read pre-aggregated tables, but Explorations run ad-hoc queries. When an exploration's underlying query would exceed the event-count quota for the chosen date range, GA4 samples: it computes over a subset of events and scales the result to estimate the whole, rather than scanning every event.
Reading and reducing sampling
Every exploration shows a data-quality indicator; a value below 100% means the result is based on a sample, and hovering reveals the share of events used. The wider the date range, the more dimensions, and the more events involved, the more likely sampling kicks in.
To reduce it: shorten the date range, narrow the query, or move the analysis to the BigQuery export where the full event stream is available unsampled. Higher analytics tiers raise the sampling thresholds but do not remove them.
- Standard reports mostly unsampled; Explorations can sample
- Sampling triggers when the query exceeds the event-count quota
- A sub-100% indicator flags a scaled estimate
- Shorten range / narrow query / use BigQuery to avoid it
How it appears in analytics and logs
An Exploration showing a sub-100% data indicator is sampled: the figures are scaled estimates from a subset, not exact counts of the full period.
Diagnostic use case
Explain why an Exploration's totals differ from a standard report or a shorter date range, traced to sampling that the standard report avoided.
What WebmasterID can help detect
WebmasterID computes reports over your full first-party event set, so ad-hoc analysis does not silently drop to a sampled subset.
Common mistakes
- Ignoring the sampling indicator on an exploration.
- Comparing a sampled exploration to an unsampled standard report.
- Running very wide, long-range explorations and trusting exact totals.
Privacy and accuracy notes
Sampling is a computational technique on already-collected events, not new tracking. This page is educational, not legal advice.
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.
- 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.
- BigQuery vs UI discrepancies
When GA4's BigQuery export and the reporting interface show different totals, it is usually not a bug. The UI applies sampling, data thresholds, (other) aggregation, and behavioral/conversion modeling on top of the raw event stream; BigQuery exports the unmodeled, unsampled events. Knowing which transformations the UI adds explains most gaps.
- Website Observability
Full-dataset reporting without exploration sampling.
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.