CRO Glossary
Stopping Rule
A predefined rule that specifies exactly when an experiment will be ended and analyzed, set before the test begins.
A stopping rule is the decision criterion, fixed in advance, that tells a team when to stop collecting data and declare a result. It might be a sample size target, a calendar date, or a specific statistical threshold reached under a sequential testing plan. The point is that the rule is locked before the experiment launches, so the decision to stop isn't influenced by how the results happen to look partway through.
Stopping rules matter because they are the main defense against the peeking problem and p-hacking: if you keep checking results and stop as soon as you see significance, your actual false-positive rate is much higher than the nominal 5%, even though each individual check looked legitimate. A clear stopping rule removes that temptation and keeps the statistics honest.
For example, a team might commit to running a checkout redesign test until it reaches a pre-calculated sample size of 40,000 visitors per arm, or for a minimum of two full business cycles, whichever is longer, and to only look at results for a go/no-go decision at that point. If they want to check earlier, they use a sequential testing method designed for repeated looks rather than an ad hoc frequentist test.
Good practice is to write the stopping rule into the experiment design document alongside the hypothesis and MDE, so anyone reviewing the test later can verify the team didn't just stop when the p-value happened to dip below 0.05.
Related terms
Shrinkage Estimator
A statistical adjustment that pulls noisy per-variant or per-segment estimates toward an overall average to reduce overfitting to randomness.
Flicker Test
A diagnostic check to confirm whether users briefly see the original page before a variant renders in client-side experiments.
Pre-Experiment Bucketing Audit
A review process confirming users are being randomly and evenly assigned to experiment variants before launch.
Above-Fold Exclusion Rule
A test-design rule that deliberately prevents changes to above-the-fold elements so an experiment isolates below-the-fold effects.
Flicker-Free Testing
A technical setup that prevents users from briefly seeing the original page before a test variant loads.
Orthogonal Test Design
A test structure where multiple variables are changed independently so their individual effects can be measured without interference.
See this in the wild
ABWatcher watches how top teams apply stopping rule.
Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.