All terms

CRO Glossary

Test Contamination

When users or data leak between control and variant groups, biasing an experiment's results.

Test contamination happens when the separation between control and treatment breaks down, so the two groups no longer represent clean, independent populations. This can occur when a user clears cookies and gets re-bucketed into a different variant, when someone uses multiple devices, when internal QA traffic leaks into production data, or when a change in one variant accidentally affects the experience of another (for example, a shared cache, shared inventory, or a backend service that serves both groups).

The danger is that contamination quietly dilutes or distorts the measured effect without throwing an obvious error. Unlike a sample ratio mismatch, which is usually easy to spot in the numbers, contamination can look like a normal, healthy test while still producing misleading conclusions. Teams often only discover it after the fact, when a result fails to replicate or when a post-launch metric doesn't match the reported lift.

A common real-world example is a marketplace test where a new pricing algorithm is shown to only half of buyers, but that algorithm changes overall demand and therefore the supply and prices seen by the control group too. Because the two groups aren't truly isolated, the observed lift is unreliable.

Guarding against contamination usually means auditing randomization logic, ensuring stable user identifiers, isolating shared backend resources where feasible, and building monitoring that flags cross-variant leakage early, before it undermines the read-out.

Related terms

See this in the wild

ABWatcher watches how top teams apply test contamination.

Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.