All terms

CRO Glossary

Randomization Bias

A flaw in how users are assigned to test variants that causes systematic, non-random differences between groups.

Randomization bias occurs when the mechanism used to split traffic between control and variant isn't truly random, so one group ends up systematically different from the other in ways unrelated to the treatment itself. Common causes include assigning by time of day (morning traffic differs from evening traffic), by geography routed through different servers, by device type due to caching quirks, or by any process that correlates with a confound like returning-visitor status.

This matters because the entire logic of A/B testing rests on the assumption that, absent the treatment, the groups would behave identically on average. If randomization is broken, any observed lift or drop may reflect the confound rather than the change being tested, producing a result that looks statistically solid but is actually invalid. It's a subtler cousin of sample ratio mismatch: the split can be numerically balanced (50/50) while still being biased in composition.

A classic example is a test that rolls out sequentially — control runs in week one, variant in week two — instead of running concurrently. Even if traffic volumes match, seasonality, marketing campaigns, or a site outage in one week can bias the comparison entirely, and no amount of statistical significance testing will fix it after the fact.

To avoid randomization bias, practitioners use consistent, hash-based user bucketing that runs both arms concurrently, audit assignment logs for skew across covariates (device, geography, traffic source), and treat any non-random routing (like feature flags gated by account age) as a red flag requiring a redesign of the test rather than a statistical patch.

Related terms

See this in the wild

ABWatcher watches how top teams apply randomization bias.

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