Ab Test Setup

A/B Test Setup

You are an expert in experimentation and A/B testing. Your goal is to help design tests that produce statistically valid, actionable results.

Initial Assessment

Check for product marketing context first: If .claude/product-marketing-context.md exists, read it before asking questions. Use that context and only ask for information not already covered or specific to this task.

Before designing a test, understand:

1. Test Context - What are you trying to improve? What change are you considering? 2. Current State - Baseline conversion rate? Current traffic volume? 3. Constraints - Technical complexity? Timeline? Tools available?

---

Core Principles

1. Start with a Hypothesis

• Not just "let's see what happens"
• Specific prediction of outcome
• Based on reasoning or data

2. Test One Thing

• Single variable per test
• Otherwise you don't know what worked

3. Statistical Rigor

• Pre-determine sample size
• Don't peek and stop early
• Commit to the methodology

4. Measure What Matters

• Primary metric tied to business value
• Secondary metrics for context
• Guardrail metrics to prevent harm

---

Hypothesis Framework

Structure

Because [observation/data],
we believe [change]
will cause [expected outcome]
for [audience].
We'll know this is true when [metrics].

Example

Weak: "Changing the button color might increase clicks."

Strong: "Because users report difficulty finding the CTA (per heatmaps and feedback), we believe making the button larger and using contrasting color will increase CTA clicks by 15%+ for new visitors. We'll measure click-through rate from page view to signup start."

---

Test Types

---

Sample Size

Calculate It (bundled tool)

Use this skill's own calculator — don't eyeball it:

python3 scripts/sample_size_calculator.py --baseline 0.05 --mde 0.20            # human-readable
python3 scripts/sample_size_calculator.py --baseline 0.05 --mde 0.20 --json    # for pipelines
python3 scripts/sample_size_calculator.py --baseline 0.05 --mde 0.20 --daily-traffic 2000  # adds test-duration estimate

Paste sample_size_per_variation and the duration estimate directly into the test plan's "Sample size + duration" row before any test is approved to run.

Quick Reference

Generated by sample_size_calculator.py (two-proportion z-test, α=0.05 two-tailed, 80% power; relative MDE):

Cross-check calculators (should agree with the script within rounding):

• Evan Miller's
• Optimizely's

For detailed sample size tables and duration calculations: See references/sample-size-guide.md

---

Metrics Selection

Primary Metric

• Single metric that matters most
• Directly tied to hypothesis
• What you'll use to call the test

Secondary Metrics

• Support primary metric interpretation
• Explain why/how the change worked

Guardrail Metrics

• Things that shouldn't get worse
• Stop test if significantly negative

Example: Pricing Page Test

• Primary: Plan selection rate
• Secondary: Time on page, plan distribution
• Guardrail: Support tickets, refund rate

---

Designing Variants

What to Vary

Best Practices

• Single, meaningful change
• Bold enough to make a difference
• True to the hypothesis

---

Traffic Allocation

Considerations:

• Consistency: Users see same variant on return
• Balanced exposure across time of day/week

---

Implementation

Client-Side

• JavaScript modifies page after load
• Quick to implement, can cause flicker
• Tools: PostHog, Optimizely, VWO

Server-Side

• Variant determined before render
• No flicker, requires dev work
• Tools: PostHog, LaunchDarkly, Split

---

Running the Test

Pre-Launch Checklist

• [ ] Hypothesis documented
• [ ] Primary metric defined
• [ ] Sample size calculated
• [ ] Variants implemented correctly
• [ ] Tracking verified
• [ ] QA completed on all variants

During the Test

DO:

• Monitor for technical issues
• Check segment quality
• Document external factors

DON'T:

• Peek at results and stop early
• Make changes to variants
• Add traffic from new sources

The Peeking Problem

Looking at results before reaching sample size and stopping early leads to false positives and wrong decisions. Pre-commit to sample size and trust the process.

---

Analyzing Results

Statistical Significance

• 95% confidence = p-value < 0.05
• Means <5% chance result is random
• Not a guarantee—just a threshold

Analysis Checklist

1. Reach sample size? If not, result is preliminary 2. Statistically significant? Check confidence intervals 3. Effect size meaningful? Compare to MDE, project impact 4. Secondary metrics consistent? Support the primary? 5. Guardrail concerns? Anything get worse? 6. Segment differences? Mobile vs. desktop? New vs. returning?

Interpreting Results

---

Documentation

Document every test with:

• Hypothesis
• Variants (with screenshots)
• Results (sample, metrics, significance)
• Decision and learnings

For templates: See references/test-templates.md

---

Common Mistakes

Test Design

• Testing too small a change (undetectable)
• Testing too many things (can't isolate)
• No clear hypothesis

Execution

• Stopping early
• Changing things mid-test
• Not checking implementation

Analysis

• Ignoring confidence intervals
• Cherry-picking segments
• Over-interpreting inconclusive results

---

Task-Specific Questions

1. What's your current conversion rate? 2. How much traffic does this page get? 3. What change are you considering and why? 4. What's the smallest improvement worth detecting? 5. What tools do you have for testing? 6. Have you tested this area before?

---

Proactive Triggers

Proactively offer A/B test design when:

1. Conversion rate mentioned — User shares a conversion rate and asks how to improve it; suggest designing a test rather than guessing at solutions. 2. Copy or design decision is unclear — When two variants of a headline, CTA, or layout are being debated, propose testing instead of opinionating. 3. Campaign underperformance — User reports a landing page or email performing below expectations; offer a structured test plan. 4. Pricing page discussion — Any mention of pricing page changes should trigger an offer to design a pricing test with guardrail metrics. 5. Post-launch review — After a feature or campaign goes live, propose follow-up experiments to optimize the result.

---

Output Artifacts

---

Communication

All outputs should meet the quality standard: clear hypothesis, pre-registered metrics, and documented decisions. Avoid presenting inconclusive results as wins. Every test should produce a learning, even if the variant loses. Reference marketing-context for product and audience framing before designing experiments.

---

Related Skills

• page-cro — USE when you need ideas for what to test; NOT when you already have a hypothesis and just need test design.
• analytics-tracking — USE to set up measurement infrastructure before running tests; NOT as a substitute for defining primary metrics upfront.
• campaign-analytics — USE after tests conclude to fold results into broader campaign attribution; NOT during the test itself.
• pricing-strategy — USE when test results affect pricing decisions; NOT to replace a controlled test with pure strategic reasoning.
• marketing-context — USE as foundation before any test design to ensure hypotheses align with ICP and positioning; always load first.

Sample Size Guide

Reference for calculating sample sizes and test duration.

Sample Size Fundamentals

Required Inputs

1. Baseline conversion rate: Your current rate 2. Minimum detectable effect (MDE): Smallest change worth detecting 3. Statistical significance level: Usually 95% (α = 0.05) 4. Statistical power: Usually 80% (β = 0.20)

What These Mean

Baseline conversion rate: If your page converts at 5%, that's your baseline.

MDE (Minimum Detectable Effect): The smallest improvement you care about detecting. Set this based on:

• Business impact (is a 5% lift meaningful?)
• Implementation cost (worth the effort?)
• Realistic expectations (what have past tests shown?)

Statistical significance (95%): Means there's less than 5% chance the observed difference is due to random chance.

Statistical power (80%): Means if there's a real effect of size MDE, you have 80% chance of detecting it.

---

Sample Size Quick Reference Tables

Conversion Rate: 1%

Conversion Rate: 3%

Conversion Rate: 5%

Conversion Rate: 10%

Conversion Rate: 20%

---

Duration Calculator

Formula

Duration (days) = (Sample per variant × Number of variants) / (Daily traffic × % exposed)

Examples

Scenario 1: High-traffic page

• Need: 10,000 per variant (2 variants = 20,000 total)
• Daily traffic: 5,000 visitors
• 100% exposed to test
• Duration: 20,000 / 5,000 = 4 days

Scenario 2: Medium-traffic page

• Need: 30,000 per variant (60,000 total)
• Daily traffic: 2,000 visitors
• 100% exposed
• Duration: 60,000 / 2,000 = 30 days

Scenario 3: Low-traffic with partial exposure

• Need: 15,000 per variant (30,000 total)
• Daily traffic: 500 visitors
• 50% exposed to test
• Effective daily: 250
• Duration: 30,000 / 250 = 120 days (too long!)

Minimum Duration Rules

Even with sufficient sample size, run tests for at least:

• 1 full week: To capture day-of-week variation
• 2 business cycles: If B2B (weekday vs. weekend patterns)
• Through paydays: If e-commerce (beginning/end of month)

Maximum Duration Guidelines

Avoid running tests longer than 4-8 weeks:

• Novelty effects wear off
• External factors intervene
• Opportunity cost of other tests

---

Online Calculators

Recommended Tools

Evan Miller's Calculator https://www.evanmiller.org/ab-testing/sample-size.html

• Simple interface
• Bookmark-worthy

Optimizely's Calculator https://www.optimizely.com/sample-size-calculator/

• Business-friendly language
• Duration estimates

AB Test Guide Calculator https://www.abtestguide.com/calc/

• Includes Bayesian option
• Multiple test types

VWO Duration Calculator https://vwo.com/tools/ab-test-duration-calculator/

• Duration-focused
• Good for planning

---

Adjusting for Multiple Variants

With more than 2 variants (A/B/n tests), you need more sample:

Why? More comparisons increase chance of false positives. You're comparing:

• A vs B
• A vs C
• B vs C (sometimes)

Apply Bonferroni correction or use tools that handle this automatically.

---

Common Sample Size Mistakes

1. Underpowered tests

Problem: Not enough sample to detect realistic effects Fix: Be realistic about MDE, get more traffic, or don't test

2. Overpowered tests

Problem: Waiting for sample size when you already have significance Fix: This is actually fine—you committed to sample size, honor it

3. Wrong baseline rate

Problem: Using wrong conversion rate for calculation Fix: Use the specific metric and page, not site-wide averages

4. Ignoring segments

Problem: Calculating for full traffic, then analyzing segments Fix: If you plan segment analysis, calculate sample for smallest segment

5. Testing too many things

Problem: Dividing traffic too many ways Fix: Prioritize ruthlessly, run fewer concurrent tests

---

When Sample Size Requirements Are Too High

Options when you can't get enough traffic:

1. Increase MDE: Accept only detecting larger effects (20%+ lift) 2. Lower confidence: Use 90% instead of 95% (risky, document it) 3. Reduce variants: Test only the most promising variant 4. Combine traffic: Test across multiple similar pages 5. Test upstream: Test earlier in funnel where traffic is higher 6. Don't test: Make decision based on qualitative data instead 7. Longer test: Accept longer duration (weeks/months)

---

Sequential Testing

If you must check results before reaching sample size:

What is it?

Statistical method that adjusts for multiple looks at data.

When to use

• High-risk changes
• Need to stop bad variants early
• Time-sensitive decisions

Tools that support it

• Optimizely (Stats Accelerator)
• VWO (SmartStats)
• PostHog (Bayesian approach)

Tradeoff

• More flexibility to stop early
• Slightly larger sample size requirement
• More complex analysis

---

Quick Decision Framework

Can I run this test?

Daily traffic to page: _____
Baseline conversion rate: _____
MDE I care about: _____

Sample needed per variant: _____ (from tables above)
Days to run: Sample / Daily traffic = _____

If days > 60: Consider alternatives
If days > 30: Acceptable for high-impact tests
If days < 14: Likely feasible
If days < 7: Easy to run, consider running longer anyway

A/B Test Templates Reference

Templates for planning, documenting, and analyzing experiments.

Test Plan Template

# A/B Test: [Name]

## Overview
- **Owner**: [Name]
- **Test ID**: [ID in testing tool]
- **Page/Feature**: [What's being tested]
- **Planned dates**: [Start] - [End]

## Hypothesis

Because [observation/data],
we believe [change]
will cause [expected outcome]
for [audience].
We'll know this is true when [metrics].

## Test Design

| Element | Details |
|---------|---------|
| Test type | A/B / A/B/n / MVT |
| Duration | X weeks |
| Sample size | X per variant |
| Traffic allocation | 50/50 |
| Tool | [Tool name] |
| Implementation | Client-side / Server-side |

## Variants

### Control (A)
[Screenshot]
- Current experience
- [Key details about current state]

### Variant (B)
[Screenshot or mockup]
- [Specific change #1]
- [Specific change #2]
- Rationale: [Why we think this will win]

## Metrics

### Primary
- **Metric**: [metric name]
- **Definition**: [how it's calculated]
- **Current baseline**: [X%]
- **Minimum detectable effect**: [X%]

### Secondary
- [Metric 1]: [what it tells us]
- [Metric 2]: [what it tells us]
- [Metric 3]: [what it tells us]

### Guardrails
- [Metric that shouldn't get worse]
- [Another safety metric]

## Segment Analysis Plan
- Mobile vs. desktop
- New vs. returning visitors
- Traffic source
- [Other relevant segments]

## Success Criteria
- Winner: [Primary metric improves by X% with 95% confidence]
- Loser: [Primary metric decreases significantly]
- Inconclusive: [What we'll do if no significant result]

## Pre-Launch Checklist
- [ ] Hypothesis documented and reviewed
- [ ] Primary metric defined and trackable
- [ ] Sample size calculated
- [ ] Test duration estimated
- [ ] Variants implemented correctly
- [ ] Tracking verified in all variants
- [ ] QA completed on all variants
- [ ] Stakeholders informed
- [ ] Calendar hold for analysis date

---

Results Documentation Template

# A/B Test Results: [Name]

## Summary
| Element | Value |
|---------|-------|
| Test ID | [ID] |
| Dates | [Start] - [End] |
| Duration | X days |
| Result | Winner / Loser / Inconclusive |
| Decision | [What we're doing] |

## Hypothesis (Reminder)
[Copy from test plan]

## Results

### Sample Size
| Variant | Target | Actual | % of target |
|---------|--------|--------|-------------|
| Control | X | Y | Z% |
| Variant | X | Y | Z% |

### Primary Metric: [Metric Name]
| Variant | Value | 95% CI | vs. Control |
|---------|-------|--------|-------------|
| Control | X% | [X%, Y%] | — |
| Variant | X% | [X%, Y%] | +X% |

**Statistical significance**: p = X.XX (95% = sig / not sig)
**Practical significance**: [Is this lift meaningful for the business?]

### Secondary Metrics

| Metric | Control | Variant | Change | Significant? |
|--------|---------|---------|--------|--------------|
| [Metric 1] | X | Y | +Z% | Yes/No |
| [Metric 2] | X | Y | +Z% | Yes/No |

### Guardrail Metrics

| Metric | Control | Variant | Change | Concern? |
|--------|---------|---------|--------|----------|
| [Metric 1] | X | Y | +Z% | Yes/No |

### Segment Analysis

**Mobile vs. Desktop**
| Segment | Control | Variant | Lift |
|---------|---------|---------|------|
| Mobile | X% | Y% | +Z% |
| Desktop | X% | Y% | +Z% |

**New vs. Returning**
| Segment | Control | Variant | Lift |
|---------|---------|---------|------|
| New | X% | Y% | +Z% |
| Returning | X% | Y% | +Z% |

## Interpretation

### What happened?
[Explanation of results in plain language]

### Why do we think this happened?
[Analysis and reasoning]

### Caveats
[Any limitations, external factors, or concerns]

## Decision

**Winner**: [Control / Variant]

**Action**: [Implement variant / Keep control / Re-test]

**Timeline**: [When changes will be implemented]

## Learnings

### What we learned
- [Key insight 1]
- [Key insight 2]

### What to test next
- [Follow-up test idea 1]
- [Follow-up test idea 2]

### Impact
- **Projected lift**: [X% improvement in Y metric]
- **Business impact**: [Revenue, conversions, etc.]

---

Test Repository Entry Template

For tracking all tests in a central location:

| Test ID | Name | Page | Dates | Primary Metric | Result | Lift | Link |
|---------|------|------|-------|----------------|--------|------|------|
| 001 | Hero headline test | Homepage | 1/1-1/15 | CTR | Winner | +12% | [Link] |
| 002 | Pricing table layout | Pricing | 1/10-1/31 | Plan selection | Loser | -5% | [Link] |
| 003 | Signup form fields | Signup | 2/1-2/14 | Completion | Inconclusive | +2% | [Link] |

---

Quick Test Brief Template

For simple tests that don't need full documentation:

## [Test Name]

**What**: [One sentence description]
**Why**: [One sentence hypothesis]
**Metric**: [Primary metric]
**Duration**: [X weeks]
**Result**: [TBD / Winner / Loser / Inconclusive]
**Learnings**: [Key takeaway]

---

Stakeholder Update Template

## A/B Test Update: [Name]

**Status**: Running / Complete
**Days remaining**: X (or complete)
**Current sample**: X% of target

### Preliminary observations
[What we're seeing - without making decisions yet]

### Next steps
[What happens next]

### Timeline
- [Date]: Analysis complete
- [Date]: Decision and recommendation
- [Date]: Implementation (if winner)

---

Experiment Prioritization Scorecard

For deciding which tests to run:

Scoring: 1-5 (5 = best)

---

Hypothesis Bank Template

For collecting test ideas:

| ID | Page/Area | Observation | Hypothesis | Potential Impact | Status |
|----|-----------|-------------|------------|------------------|--------|
| H1 | Homepage | Low scroll depth | Shorter hero will increase scroll | High | Testing |
| H2 | Pricing | Users compare plans | Comparison table will help | Medium | Backlog |
| H3 | Signup | Drop-off at email | Social login will increase completion | Medium | Backlog |