Analytics and Tracking

Sampling Error

Also called Sampled data, estimated reporting

The distortion introduced when a report is calculated from part of the data and scaled up to represent all of it.

Quick facts: Sampling Error

Category
Analytics and Tracking
Also called
Sampled data, estimated reporting
Level
Intermediate
Affects
Report accuracy, segment analysis, client reporting, decision confidence
Where to see it
GA4 explorations, Looker Studio, Google Ads reports, BigQuery exports
In this article4
  1. What sampling error measures
  2. Why sampling error matters
  3. Common mistakes with sampling error
  4. How to act on it

What sampling error measures

When a reporting tool has more data than it will process in the time allowed, it takes a portion, calculates the answer from that portion and scales the result up. Sampling error is the gap between that estimate and the answer you would have got from every row. It is not a bug and it is not the tool lying — it is the price of a fast answer over a complete one.

The size of the gap depends on how thin the slice is and how rare the thing you are counting is. Broad totals from a large slice come back close to the truth. A narrow segment — one city, one landing page, one campaign in a small market — may be represented by very few real sessions in the sample, and scaling those few up magnifies whatever accident they contain. That is why sampled reports can look confident and stable at the top level while the detail underneath swings from one refresh to the next.

Why sampling error matters

It changes what a report can be used for. A sampled figure is fine for direction — this channel is growing, that page is losing traffic — and unfit for anything that has to reconcile with money or with a person. Nobody should be paid a commission, billed or invoiced on a scaled estimate.

The risk is sharper for small and local businesses. A campaign in Nepal that draws modest daily traffic will have very little of it inside a sample, so the segment reports built from it are the least reliable part of the account and often the ones a client asks about most.

Common mistakes with sampling error

The first is not checking whether a report is sampled at all. Most tools say so, quietly, near the top of the report, and most people scroll past it. If you never look, you cannot tell a real change from an artefact of the slice.

The second is chasing tiny movements. When a segment is thin, small differences between periods are noise, and re-running the same report can produce a different answer. Building a story around that movement wastes the meeting. A related mistake is confusing sampling with thresholding, where rows are withheld to protect identity, or with cardinality limits, where values are bundled together. All three make a report incomplete, but each needs a different response.

How to act on it

Look for the sampling notice before you read the numbers, and treat a sampled report as a signal rather than a count. Shorten the date range, remove filters you do not need and drop custom segments — each of those makes it more likely the tool can answer from the full set.

For anything that must be exact, go to a source that does not sample: the platform’s standard reports, an export to a data warehouse, or the business’s own records. In practice, most reporting dashboards should carry a note saying which figures are estimates, so the person reading them knows which ones will hold up under scrutiny.

Do and do not

Do

  • Check for the sampling notice before reading any figure
  • Shorten date ranges and drop segments to reduce sampling
  • Use unsampled sources for anything tied to money

Do not

  • Report a sampled estimate to a client as an exact count
  • Read small movements in a thin segment as real change
  • Confuse sampling with thresholding or cardinality limits

Questions people ask about this

When does a report get sampled?

Usually when you ask a question the tool cannot answer from its ready-made tables — a long date range, a custom segment, an unusual combination of dimensions, or a heavy exploration. Standard, pre-built reports over short periods are far less likely to be sampled. Most tools display a notice when it happens, so check for that before reading the numbers.

Is a sampled report still useful?

Yes, for direction. It will tell you reliably that one channel is growing while another shrinks, or which pages carry most of the traffic. It should not be used where the number itself matters: billing, commission, tax, reconciling with a CRM, or reporting a figure to a client as fact. Use an unsampled source for those.

How do I get rid of sampling?

Reduce what the tool has to process. Shorten the date range, remove filters and custom segments, and use standard reports rather than custom explorations. If the analysis genuinely needs everything, export the raw data to a warehouse and query it there, or take the figure from a system that holds complete records, such as your CRM or order database.

Related terms

Found this useful?

Share it, or ask an AI to summarise it

Back to the glossary

Knowing the term is the easy part

Applying it to your own site and budget is the work. Book a call and I will tell you what actually applies to you.