A B Test Significance Power Analyzer
Test whether an A/B result is statistically significant: enter visitors and conversions per variant to get z-score, p-value, lift and the sample size.
A B Test Significance Power Analyzer
Calculator
Adjust values & calculateEnter your values below. Every result is computed in your browser โ no data is sent to any server.
Formula: Z = (pB - pA) / sqrt(p_pool x (1 - p_pool) x (1/nA + 1/nB))
Worked example โ Significant at 95% | Lift: +18.75% | p-value: 0.021 | Variant B wins
Formula
Z = (pB - pA) / sqrt(p_pool x (1 - p_pool) x (1/nA + 1/nB))
The z-test for two proportions compares conversion rates by computing the pooled standard error and testing whether the observed difference is larger than expected by chance. The p-value from the z-score determines statistical significance.
Worked Examples
Example 1: E-commerce Button Color Test
Problem:Test a new green checkout button (B) against the original blue (A). Control: 10,000 visitors, 320 conversions. Variant: 10,000 visitors, 380 conversions. Use 95% confidence.
Solution:Rate A: 320/10000 = 3.200% Rate B: 380/10000 = 3.800% Pooled rate: 700/20000 = 3.500% SE = sqrt(0.035 x 0.965 x (1/10000 + 1/10000)) = 0.002603 Z = (0.038 - 0.032) / 0.002603 = 2.305 p-value = 0.0212 Since p < 0.05, the result is statistically significant.
Result:Significant at 95% | Lift: +18.75% | p-value: 0.021 | Variant B wins
Example 2: Landing Page Headline Test
Problem:Test a new headline (B) vs original (A). Control: 3,000 visitors, 90 signups. Variant: 3,000 visitors, 105 signups. 95% confidence level.
Solution:Rate A: 90/3000 = 3.000% Rate B: 105/3000 = 3.500% Pooled rate: 195/6000 = 3.250% SE = sqrt(0.0325 x 0.9675 x (1/3000 + 1/3000)) = 0.004575 Z = (0.035 - 0.030) / 0.004575 = 1.093 p-value = 0.2745 Since p > 0.05, the result is NOT statistically significant.
Result:Not Significant | Lift: +16.67% | p-value: 0.275 | Need ~19,750 visitors per group for 80% power
Frequently Asked Questions
What is statistical significance in A/B testing?
Statistical significance in A/B testing tells you whether the observed difference between your control (A) and variant (B) is likely due to a real effect rather than random chance. It is quantified by the p-value, which represents the probability of observing a difference as large as (or larger than) what you measured, assuming there is actually no real difference between the two versions. A commonly used threshold is p < 0.05, meaning there is less than a 5% chance the result is due to random variation. However, statistical significance alone does not tell you the practical importance of the difference or whether the observed lift is meaningful for your business. You should always consider effect size and confidence intervals alongside significance.
What is statistical power and why does it matter?
Statistical power is the probability that your test will correctly detect a real difference between variants when one actually exists. A test with 80% power has an 80% chance of detecting a true effect and a 20% chance of missing it (a Type II error or false negative). Power depends on four factors: sample size, effect size (how big the real difference is), significance level (alpha), and baseline conversion rate. Running underpowered tests is a common mistake that leads teams to conclude that a variant has no effect when it actually does. Before starting an A/B test, you should calculate the required sample size to achieve at least 80% power for the minimum detectable effect that would be practically meaningful to your business.
How long should I run an A/B test?
You should run an A/B test until you reach the pre-calculated sample size needed for adequate statistical power, typically 80% or higher. Stopping a test early because it looks significant (called peeking) inflates your false positive rate dramatically. As a guideline, most tests should run for at least one full business cycle (usually one to two weeks) to account for day-of-week effects and traffic patterns. Additionally, never run a test indefinitely hoping for significance, as this is a form of p-hacking. If your traffic is low, you may need to test larger changes that produce bigger effect sizes, or accept that you need several weeks or months of data. Tools like sequential testing or Bayesian methods can allow valid early stopping.
What is the difference between one-tailed and two-tailed tests?
A two-tailed test checks whether variant B is significantly different from variant A in either direction (better or worse), while a one-tailed test only checks one direction (e.g., whether B is better than A). Two-tailed tests are generally recommended for A/B testing because changes can sometimes hurt performance unexpectedly. With a two-tailed test at 95% confidence, the alpha of 0.05 is split between both tails (0.025 each), making it slightly harder to reach significance compared to a one-tailed test. A one-tailed test has more power to detect a difference in the predicted direction but completely ignores the possibility that the variant could be worse. A B Test Significance Power Analyzer uses a two-tailed test by default, which is the standard approach in most A/B testing frameworks.
What are common mistakes in A/B testing?
Common A/B testing mistakes include peeking at results and stopping early when significance is reached, which inflates false positive rates far above the nominal alpha level. Another frequent error is running tests with insufficient sample size, leading to underpowered experiments that cannot reliably detect real effects. Testing too many variations simultaneously without correcting for multiple comparisons increases the chance of false positives. Not accounting for external factors such as seasonality, marketing campaigns, or holidays can confound results. Segment-based analysis after the fact (post-hoc segmentation) is also problematic because finding significant effects in cherry-picked subgroups is nearly guaranteed by chance alone. Finally, ignoring practical significance and focusing solely on statistical significance can lead to implementing changes with trivially small effects.
How should I interpret the confidence interval for the difference in conversion rates?
The interval brackets the plausible range for the true absolute difference between the variant and control rates, expressed in percentage points. It is built from the unpooled standard error, because once you are estimating the size of an effect you no longer assume both arms share one underlying rate. If the interval spans zero, the data cannot rule out no difference at your confidence level. An interval that stays positive but is very wide still supports shipping, though it will not pin down how large the win is.
What is a minimum detectable effect and how does it drive required sample size?
The minimum detectable effect is the smallest true difference you want the experiment to be able to catch. Set it from what would actually change a business decision rather than from what you hope to see. Required sample size scales with the inverse square of that difference, so halving the minimum detectable effect roughly quadruples the visitors needed per arm. Baseline conversion rate matters too: rarer conversions carry proportionally more sampling noise, so a low baseline demands far more traffic for the same sensitivity.
What is the difference between the absolute difference and the relative lift?
The absolute difference is the variant rate minus the control rate, measured in percentage points. Relative lift divides that gap by the control rate. Moving from a 3.0% to a 3.5% conversion rate is 0.5 percentage points in absolute terms but a 16.7% relative lift, and the relative figure always looks more dramatic at low baselines. The z-test and the confidence interval here operate on the absolute difference, so report both: the percentage-point figure is what translates into forecast revenue.
Why should I check for sample ratio mismatch before trusting a p-value?
Sample ratio mismatch means the traffic split you observed differs materially from the split you assigned, such as a planned 50/50 test delivering clearly unequal visitor counts. It normally signals an instrumentation defect: redirect latency on one arm, bot filtering that hits the variant harder, or users leaving before the variant renders. Because the imbalance is not random, the two groups are no longer comparable and the assumptions behind the z-test break. Fix the assignment pipeline and rerun rather than interpreting the result.
When does the normal approximation behind this z-test stop being reliable?
The two-proportion z-test approximates a binomial count with a normal curve, which holds well when the expected number of conversions and non-conversions in each arm is comfortably above roughly five to ten. At very low conversion rates you can violate that even with thousands of visitors: 2,000 sessions at a 0.2% rate produce only about four expected conversions. In that regime an exact method such as Fisher's exact test, or a Bayesian beta-binomial model, gives more trustworthy tail probabilities.
References
Background & Theory
History
Reviewed for accuracy by Daniel Agrici, Founder & Lead Developer ยท Editorial policy
Related Calculators
๐A/B Test Significance
Calculate statistical significance and required sample size for A/B tests
๐งฎExperiment Design Assistant: Sample Size & Power
Calculate experiment design assistant with inputs, formulas, and instant results.
โ๏ธA/B Test Sample Size & Power
Calculate required sample size for A/B tests with statistical power and MDE analysis
๐ฌExperiment Power & Sample Size Checker
Calculate A/B test sample size, statistical power, and test duration
๐งฎAutomatic Distribution Fit Analyzer
Calculate automatic distribution fit analyzer with inputs, formulas, and instant results.
๐งฎSLA Risk Analyzer Uptime Targets
Calculate sla risk analyzer uptime targets with inputs, formulas, and instant results.
๐งฎText Sentiment Analyzer
Calculate text sentiment analyzer with interactive inputs and clear steps.
๐งฎColor Palette Balance AI
Calculate color palette balance ai with inputs, formulas, and instant results.