All terms

CRO Glossary

Traffic Throttling

Deliberately limiting the percentage or volume of visitors exposed to a test variant to manage risk.

Traffic throttling is the practice of capping how much of a site's traffic sees a new experience during an experiment, rather than splitting 50/50 from the start. Teams commonly throttle a risky variant to 5-10% of traffic initially, then increase the allocation once early signals suggest no major bugs, performance regressions, or catastrophic drops in key metrics.

This matters because full-traffic exposure to an untested variant can cause outsized damage if something breaks — a broken checkout flow shown to half your visitors is far costlier than the same bug shown to five percent. Throttling gives teams a safety valve: it limits blast radius while still collecting real user data, and it's often paired with automated kill switches that pause a test if guardrail metrics move sharply in the wrong direction.

A practical example: a fintech company launches a redesigned onboarding flow. Instead of a straight A/B split, they throttle the new flow to 5% of new sign-ups for the first 48 hours, monitor drop-off and error rates, and only ramp up to a full 50/50 split once they're confident the flow is stable. This is different from a slow ramp-up used purely for statistical sequencing — throttling is primarily a risk-management lever, though the two concepts often work together in practice.

One trade-off to keep in mind is that throttling extends the time needed to reach a meaningful sample size, since fewer users are being exposed to the variant of interest each day.

Related terms

See this in the wild

ABWatcher watches how top teams apply traffic throttling.

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