All terms

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

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.