CRO Glossary
Experiment Kill Criteria
Pre-defined conditions under which a running experiment is stopped early, regardless of its statistical results.
Kill criteria are rules set before an experiment launches that specify when to halt it prematurely — for example, if a guardrail metric like page load time, error rate, or revenue drops beyond an acceptable threshold. Unlike stopping a test because it reached significance, kill criteria exist to prevent harm: they're a safety net, not a decision rule about the primary hypothesis.
Teams care about this because experiments can go wrong in ways unrelated to the hypothesis being tested — a broken checkout button in the variant, a tracking bug, or a genuine regression in a critical business metric. Without pre-agreed kill criteria, teams either let damaging tests run too long (waiting for "enough data") or panic-stop tests based on gut feel, which introduces bias and undermines trust in results.
A concrete example: an e-commerce team testing a new checkout flow sets a kill criterion that if cart abandonment rate in the variant exceeds the control by more than 10 percentage points at any daily check, the test is stopped immediately and rolled back, even though the primary success metric (average order value) hasn't reached significance yet.
Good kill criteria are specific, measurable, and agreed upon during experiment design — typically documented in the experiment design document — rather than improvised mid-test, which keeps the decision objective and defensible.
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 experiment kill criteria.
Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.