ROASStack
CRO & Experimentation14 min read

Statistical Significance in E-Commerce CRO: Sample Size, P-Value & Z-Score Playbook

Why most published split test 'winners' are statistical illusions. The complete mathematical guide to two-tailed Z-tests, calculating required sample sizes, preventing stopping rule fallacies, and ensuring test repeatability.

SL

Dr. Sarah Lin

Lead Quantitative Analyst

Last Updated: August 31, 2026
Companion Interactive Tool

A/B Test Statistical Significance & Sample Size Calculator

Calculate two-tailed Z-scores, p-values, confidence intervals, and required visitor sample sizes for CRO tests.

Launch Simulator

1. The Mathematics of A/B Hypothesis Testing

When testing a new checkout layout or product page variation (B) against your baseline control (A), you are testing a statistical hypothesis:

Null Hypothesis (H0)

Conversion Rate B = Conversion Rate A. Any observed difference is purely random variance.

Alternative Hypothesis (H1)

Conversion Rate B ≠ Conversion Rate A. The variation genuinely alters conversion behavior.

For large e-commerce traffic samples, we apply the Two-Tailed Z-Test for Independent Proportions:

Z = (p_B - p_A) / √[ p_pool × (1 - p_pool) × (1/N_A + 1/N_B) ]

Where p_pool = (Conversions_A + Conversions_B) / (Visitors_A + Visitors_B).

For a 95% confidence level (α = 0.05), the absolute Z-score must exceed 1.96. For 99% confidence (α = 0.01), Z must exceed 2.58.

2. Sample Size Estimation & Minimum Detectable Effect (MDE)

One of the most common mistakes in CRO is declaring a test conclusive before reaching the required sample size. The required sample size per variation is given by:

N = [ (Z_α/2 + Z_β)^2 × (p_A(1 - p_A) + p_B(1 - p_B)) ] / (p_B - p_A)^2
Baseline Conv RateTarget Relative Lift (MDE)Expected Variant RateSample Size / VariationTotal Test Traffic
2.0%+5.0% relative2.10%155,000310,000 visitors
2.0%+10.0% relative2.20%39,00078,000 visitors
2.0%+20.0% relative2.40%10,00020,000 visitors
4.0%+10.0% relative4.40%19,20038,400 visitors

3. The Peeking Problem & False Positive Rate Inflation

In conversion testing software (such as VWO, Optimizely, or Google Optimize historical logs), statistical confidence numbers fluctuate wildly during the first few days. A variant might show 98% confidence after 300 visitors simply due to an early cluster of transactions.

Statistical Law: Alpha Inflation on Sequential Tests

When an experimenter checks test results daily and stops the test the moment p < 0.05 is hit, the real false positive rate rises from 5% to over 30%. This means roughly 1 in 3 implemented "winners" is actually neutral or harmful to your business.

4. The 4 Golden Rules of Rigorous E-Commerce CRO

1

Pre-Determine Sample Size

Calculate required visitor traffic per variant before starting the test and never stop early.

2

Minimum 14 Full Days

Run experiments across at least two full business cycles to balance day-of-week customer variance.

3

Track Revenue Per Visitor (RPV)

A variation that boosts conversion rate but reduces Average Order Value (AOV) can lower total net profit.

4

Segment Mobile vs Desktop

Always evaluate device segments independently to prevent aggregate Simpson's Paradox distortions.

Frequently Asked Questions (A/B Testing Statistics)

Run Your Live Split Test Calculations

Input your control and variant visitor counts and conversion numbers to verify statistical confidence and p-values.

Open A/B Testing Statistical Engine