Skip to main content
Nonkera
ProductivityUpdated August 4, 2026

What Is Statistical Significance in A/B Testing? A Plain-English Guide

What statistical significance actually means in an A/B test, why peeking early causes false winners, and how to read a p-value without a stats background.

The question significance is actually answering

Run an A/B test and one variant will almost always come out ahead by some number — that's true even if the two variants are identical in every way that matters, purely from random noise in which visitors happened to land in which group. Statistical significance answers one specific, narrow question: is the gap you're seeing large enough, given how much data you've collected, that it's unlikely to be that kind of random noise? It's not a measure of how big the difference is, and it's not a guarantee the winning variant will keep winning by that exact margin forever — it's a confidence check on whether the result is real at all.

p-values, without the jargon

A p-value is the probability of seeing a difference at least as large as the one you observed, if there were actually no real difference between the variants at all. A p-value of 0.03 means: if A and B truly performed identically, you'd only expect to see a gap this big (or bigger) about 3% of the time by chance alone. A common threshold is 0.05 — below that, the result is usually called "statistically significant," meaning the observed difference is unlikely enough to be random noise that most people are comfortable trusting it. That threshold isn't a law of nature, though; it's a convention, and how strict to be depends on how costly a wrong call would be.

Confidence level: the other side of the same coin

Confidence level and the significance threshold are two ways of describing the same decision — a 95% confidence level corresponds to a 0.05 significance threshold (the two always add up to 100%, or 1.0). Higher confidence (99%) demands stronger evidence before calling a result significant, which means fewer false positives but also a slower path to a decision. Lower confidence (90%) reaches a verdict faster but accepts more risk of calling a fluke a real win. Neither is universally "correct" — a low-stakes test (a button color) can reasonably use 90%, while a high-stakes one (a pricing page) is safer at 99%.

The mistake that ruins more A/B tests than anything else

Peeking at results early and stopping the moment significance is first reached is, by a wide margin, the most common way real-world A/B tests go wrong. With a small sample size early in a test, significance can flicker in and out of "reached" as more data trickles in — checking daily and stopping the instant you see a favorable p-value dramatically inflates your odds of a false positive, because you're effectively giving yourself many chances to catch a lucky fluctuation instead of one clean check against a pre-set bar. The standard fix is deciding on a sample size or a fixed test duration in advance — using a sample-size calculation based on your baseline conversion rate and the minimum improvement worth detecting — and only checking the result once that threshold is reached, not continuously along the way.

Statistical power: the number people skip

Significance gets all the attention, but power is what tells you how much to trust it. Power is roughly the probability that your test would correctly detect a real difference of the size you observed, given your current sample size — low power means your sample is thin enough that even a result that crosses the significance threshold could still be somewhat unstable, and running the test longer would be worth it before fully committing. A conventional target is 80% power; below that, treat a "significant" result as an encouraging early signal rather than a settled verdict.

What significance doesn't tell you

A statistically significant result answers "is this probably real?" — it doesn't answer "is this big enough to matter?" or "will it hold up at full scale?" A test with enough traffic can detect a genuinely tiny, practically meaningless difference as significant; a large e-commerce site running millions of visitors through a test might find a 0.1% conversion lift is statistically significant while still being too small to justify the engineering effort of shipping it. Significance is a filter for ruling out noise, not a substitute for judgment about whether the winning margin is actually worth acting on.

Frequently asked questions

What's a good confidence level to use for an A/B test?

95% is the most common default and a reasonable general-purpose choice. Use 99% for high-stakes changes where a wrong call is costly, and 90% is acceptable for lower-stakes, faster-moving tests.

Why does checking my test results every day cause problems?

Significance can fluctuate in and out of "reached" with a small sample, so checking repeatedly and stopping at the first favorable result meaningfully inflates the chance of a false positive. Decide on a sample size or duration in advance and check once that's reached.

What does it mean if my p-value is 0.5?

It means that if there were truly no real difference between your variants, you'd expect to see a gap this large about half the time purely by chance — in other words, there's no meaningful evidence of a real difference yet.

Can a result be statistically significant but not actually matter?

Yes — with a large enough sample, even a very small, practically unimportant difference can reach statistical significance. Significance tells you the difference is probably real, not that it's large enough to be worth acting on.

What's the difference between significance and power?

Significance tells you whether your current result is likely real rather than noise. Power tells you how capable your current sample size is of reliably detecting a real difference in the first place — a significant result backed by low power is still worth treating cautiously.

Do I need to know statistics to run an A/B test?

Not in depth — a calculator that runs the two-proportion z-test for you and translates the result into plain language covers what most people need for everyday testing decisions.