The alternative hypothesis (H₁ or Hₐ) in A/B testing is the claim that a real, non-random difference exists between the control and the variant on the target metric. It is the hypothesis you are trying to gather evidence for. When statistical significance is reached and the null hypothesis is rejected, the alternative hypothesis is accepted — meaning the data supports the conclusion that the observed difference reflects a genuine effect of the change being tested.
Types of Alternative Hypotheses
Alternative hypotheses can be directional or non-directional:
-
Two-tailed (non-directional): The variant conversion rate differs from the control in either direction (better or worse). Most A/B tests use two-tailed tests.
- H₁: Variant CR ≠ Control CR
-
One-tailed (directional): The variant conversion rate is specifically higher (or lower) than the control. Used only when you have strong prior evidence about direction.
- H₁: Variant CR > Control CR
One-tailed tests require a smaller sample size to reach the same significance level, but they are only valid when the direction of improvement is genuinely predictable — using them opportunistically inflates false positive rates.
Why the Alternative Hypothesis Matters for Ecommerce
The alternative hypothesis is where your business logic lives. A well-written H₁ connects the CRO hypothesis to a real customer behavior change: "Adding a free-shipping threshold progress bar will increase average order value because customers will add items to qualify for free delivery." Specificity in the alternative hypothesis prevents teams from retrofitting a narrative onto ambiguous results after the test ends. It also forces clarity about what "better" means — is the alternative hypothesis about conversion rate, AOV, RPV, or checkout completion rate? The answer shapes the entire test design.
Real-World Example
The Man Company's CRO team designed an experiment on their subscription product page. Their alternative hypothesis: "Displaying a per-unit cost comparison (₹X/day vs. ₹X one-time) will increase subscription plan selection rate compared to showing only total price." The null hypothesis was that plan selection rate would be the same. After 24 days, the per-unit display variant showed an 18% higher subscription selection rate at 97% confidence. H₁ was accepted: the framing change had a real, measurable effect on the metric specified in the hypothesis before the test started.
How to Write Strong Alternative Hypotheses
- Be specific about the metric: "will increase add-to-cart rate" is better than "will improve performance."
- Tie the hypothesis to a customer behavior mechanism: explain why the change should produce the effect.
- Commit to directionality honestly: use a two-tailed test unless you genuinely have strong prior evidence for a specific direction.
- State H₁ in the test brief before any data is collected — this prevents post-hoc rationalization of results.
- Separate the business hypothesis ("we think showing reviews increases trust") from the statistical hypothesis (H₁: variant CR > control CR) — both matter, but they serve different purposes.
Alternative Hypothesis in A/B Testing
In A/B testing, the alternative hypothesis is accepted when the p-value falls below the pre-set alpha threshold. Critically, accepting H₁ does not prove it is true in an absolute sense — it means the data provides sufficient evidence to reject the assumption of no effect. The strength of that evidence is quantified by the confidence level and the observed effect size.
Run smarter A/B tests with CustomFit.ai — 14-day free trial, no credit card required.