Bell Statistics

What is a global holdout?

A global holdout is a small share of users permanently excluded from everything a team ships. Comparing it against everyone else measures what a quarter or a year of releases actually delivered, rather than trusting the sum of what each individual experiment reported.

Also called
long-term holdout, always-on holdout, org-level holdout, universal control
Allon Korem

Written by Allon Korem

Chief Executive Officer

Last updated

In plain English

Individual experiments answer individual questions. A global holdout answers a different and harder one: across everything this team shipped last quarter, what actually changed? It works by permanently withholding all releases from a small randomly chosen slice of users — typically 1 to 5% — and comparing them against the population receiving normal development.

The reason to bother is that summing experiment results reliably overstates reality, usually by a large factor, and every mechanism that causes this is invisible from inside the individual tests. Novelty effects inflate short-horizon readings. Winner's curse means a result that barely cleared significance is more likely to have been lucky than to be at its estimated size. Interactions mean two changes that each worked can cancel when shipped together. And proxy metrics transfer to real outcomes at a fraction of the assumed rate. Each experiment can be correctly run and correctly analysed and the total still not appear.

Organisations that do this consistently report the same shape of finding: the cumulative effect measured against a global holdout is materially smaller than the sum of the wins, often by half or more. That is not a sign the programme is failing. It is a correction to a systematic overstatement that no other measurement can catch, and knowing the real number is what makes forecasting and investment decisions honest.

Two properties make it expensive to run. It requires infrastructure discipline — every experiment and every release must respect the holdout, and a single team shipping around it silently invalidates the comparison for everyone. And it has weak statistical power, because precision is set by the small arm: a 2% holdout of a million users gives roughly the precision of a 20,000-user experiment, which resolves only fairly large cumulative effects. That is usually acceptable, since the question is about aggregate movement rather than a single change.

Distinguish it from a holdout group, which withholds one specific change and is tied to it. The global version is not attached to anything: it is the counterfactual for the whole development effort. The practical cost is that users in it drift progressively further from the current product, which raises a genuine question about how long anyone can reasonably be held there — most teams rotate the membership periodically, accepting a small loss of comparability to avoid stranding a group on a year-old experience.

The formula

One comparison, and the two arithmetic facts that explain why it is worth running and why it cannot be run at high precision.

The comparison
cumulative effect = E[ Y | all releases ] − E[ Y | global holdout ]

Measures everything shipped in the period at once, including interactions between changes.

Why the sum overstates
Σ reported effects > measured cumulative effect

Novelty decay, winner's curse, negative interactions and weak proxy transfer all push the same way.

Power is set by the small arm
SE ≈ σ / √n_holdout

A 2% holdout of a million users has the precision of a 20,000-user experiment — see the sample size calculator.

What it costs
cost = holdout share × cumulative effect × duration

Grows as the programme succeeds, which is the uncomfortable part: a good year makes the holdout more expensive.

Worked example

A consumer app maintains a 3% global holdout for a full year. Over that period the team shipped 34 experiments that reached significance on their primary metric, weekly sessions per user, with reported lifts summing to 22%. At year end the holdout is compared against the rest.

Global holdout
3% of 2.4 million users = 72,000
Experiments shipped as wins
34
Sum of reported lifts
+22.0%
Measured cumulative lift
+7.4%, 95% CI +4.9% to +9.9%
Realisation rate
34%
Retention, holdout vs shipped
no detectable difference

A year of shipped wins totalling 22% delivered a measured 7.4%. Roughly a third of the claimed value appeared.

A 34% realisation rate sounds like a failure and is close to what well-run programmes report, which is the useful calibration here. The individual experiments were not wrong — each measured a real short-horizon effect on the population it was run on. What the sum ignores is that novelty decay removed part of several, that changes shipped in the same quarter competed for the same attention, and that a handful of the 34 were borderline results that were probably overstated at the point of shipping. The right response is to keep the realisation rate as a standing multiplier on forecasts rather than to distrust the experiments. Two cautions on reading this table. The interval spans 4.9% to 9.9%, so the realisation rate is somewhere between 22% and 45% rather than exactly a third. And the absence of a retention difference is reassuring but weakly evidenced: at 72,000 holdout users only a fairly large retention effect would have been detectable.

Common misconceptions

If every experiment was properly run, the effects should add up.
Several mechanisms break additivity and all push the same direction. Novelty decay shrinks effects after the test window, winner's curse means marginal results are overstated, and changes shipped together can interact negatively. None is visible from inside an individual experiment, which is precisely why a separate cumulative measurement is needed.
A global holdout is just a large control group.
A control group is attached to one experiment and ends with it. A global holdout is attached to nothing and persists, so it measures the combined effect of everything shipped including the interactions between changes. That combination is exactly what no experiment can observe.
A low realisation rate means the experimentation programme is not working.
Realisation rates around a third are normal for well-run programmes. The programme is still delivering — 7.4% of genuine improvement is real value — and the finding is that forecasts built by summing test results were overstated. Knowing the multiplier is what makes planning honest.

Frequently asked questions

How big should a global holdout be?
Between 1 and 5% for most consumer products, sized by what cumulative effect you need to detect rather than by what percentage feels safe. Precision is governed by the holdout arm alone, so a 1% holdout of 500,000 users gives the power of a 5,000-user experiment and will only resolve large effects. Work backwards from the smallest annual movement worth knowing about.
How long can you keep users in a global holdout?
Most teams rotate membership every six to twelve months. The problem with holding indefinitely is drift: users stranded on a two-year-old product are no longer a plausible counterfactual for what current users would experience, and the gap increasingly reflects accumulated divergence rather than a clean comparison. Rotating costs some comparability across periods and avoids the worse problem.
What does a global holdout require from the platform?
That every experiment and every release checks it, without exception. One team shipping around the holdout invalidates the comparison for everyone and does so silently — there is no error, just a number that quietly stops meaning what it claims. In practice this means enforcing it at the assignment layer rather than by convention, and auditing periodically that no release path bypasses it.

Related terms

  • Control group

    The counterfactual, made concrete — and the reason a before-and-after comparison is not an experiment.

  • Holdout group

    A control that outlives the experiment — the only way to see what a change did after month one.

  • Novelty effect

    Curiosity, measured and mistaken for improvement — and the reason a strong week-one result is the least trustworthy kind.

  • Treatment group

    The users who get the change — and the counting rule that decides whether the comparison is still randomised.

Calculate it

  • A/B test sample size

    Size a two-proportion experiment before you launch, then read the lift and its interval once it lands.

  • Two-sample t-test

    Compare the average of two independent groups — plan the sample size, then test the result.

Knowing the term is the easy part

Applying it to a live measurement problem is the part that goes wrong. If you are designing an experiment, reading a result you do not trust, or trying to work out what your marketing actually caused, that is the work we do.