All terms

CRO Glossary

Sample Size

The number of users or sessions included in an experiment, which determines how reliably it can detect a real effect.

Sample size is simply how many visitors, sessions, or conversions are collected in each arm of an experiment before analysis. It is one of the most fundamental levers in experimentation: too small a sample and even a real, meaningful effect can be statistically invisible; too large and you spend unnecessary time and traffic chasing precision you don't need.

Sample size interacts closely with baseline conversion rate, the minimum detectable effect you care about, and your desired statistical power. A test on a page that converts at 2% with a goal of detecting a 10% relative lift will need a much larger sample than a test on a page converting at 20% looking for the same relative lift, because rarer events require more observations to measure precisely. This is why low-traffic pages often struggle to run meaningful experiments at all without combining results over long periods or testing bigger, bolder changes.

Teams typically calculate the required sample size before launching a test, using a sample size calculator that takes baseline rate, MDE, significance threshold, and power as inputs. Deciding to stop early because results "look good," or extending a test past its planned sample size because results "aren't there yet," are common ways teams get burned by the peeking problem.

For example, a SaaS signup flow with a 5% baseline conversion rate might need roughly 25,000 visitors per variant to reliably detect a 2-percentage-point lift — a number worth knowing before committing a quarter's roadmap to the test.

Related terms

See this in the wild

ABWatcher watches how top teams apply sample size.

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