CRO Glossary
Test Collision
When two or more concurrently running experiments overlap on the same users or pages, contaminating each other's results.
Test collision happens when a user is simultaneously enrolled in multiple experiments that interact — either because the experiments touch the same UI element, or because being in one variant changes how a user behaves in the other test. Unlike simple interaction effects that are measured on purpose, collisions are usually accidental and undetected, which is what makes them dangerous.
This matters because it silently corrupts data: a team might conclude that a new checkout button color increased conversions, when in reality a concurrently running pricing experiment on the same page was the actual driver. Without careful tracking of which tests overlap on which pages and audiences, teams can ship false winners or kill good ideas based on contaminated reads.
A concrete example: Team A is testing a new homepage hero banner, and Team B is simultaneously testing a site-wide promotional pop-up. Some users see both changes at once. If the pop-up suppresses scrolling behavior, it could distort the hero banner test's click-through numbers even though the hero test itself was implemented correctly.
Mature experimentation programs guard against this with a centralized experiment registry, mutual exclusion groups (so a user can only be in one test from a colliding group at a time), or layered experimentation systems that explicitly separate traffic used by conflicting tests.
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 test collision.
Live A/B tests at 1,000+ high-converting brands, with plain-English hypothesis and takeaway.