Experiments – Run tests and validate ideas with PostHog

Experiments

Test changes with statistical significance

Experiments is one of the tools that makes your product self-driving: the evaluation that proves a change actually worked. Built to natively work with product analytics, session replay, feature flags, and surveys.

Get started - free

Install with AI in a single prompt

Paste into your terminal or code editor and make AI do the work.

Learn more

MCP•Watch a demo•Talk to a human

What does it do?

Experiments let you run A/B, A/B/n, holdout, fake door, and redirect tests with statistical significance. Create an experiment (which creates a feature flag), pick primary and secondary metrics, target cohorts or geographies, then launch variants. Bayesian and frequentist engines tell you what won – and you can watch session replays for each variant when you need the why.

Who is it for?

Experiments is used across teams depending on your role.

Role

Use cases

Product Engineers

Ship a change behind a flag, run an A/B test, and roll out the winner without a separate release pipeline

Product Managers

Validate onboarding, pricing, or UI changes with primary and secondary metrics before committing

Growth Engineers

Target cohorts or geographies, run multivariate tests, and watch session replays for each variant

Data Scientists

Run Bayesian or frequentist analysis with shared metrics, holdouts, and warehouse-backed metrics

B2B product teams

Run group-level experiments so everyone at a company sees the same variant

How do I use it?

There are a few ways to explore Experiments.

Run experiments from your editor

Create A/B tests, check statistical significance, and manage the full experiment lifecycle from Cursor, Claude Code, VS Code, or any MCP-compatible agent.

Create experiments alongside your code

Set up an A/B test for a feature you're building without leaving your editor.

Check results before shipping

Ask "what are the results of the checkout experiment?" to decide whether to merge.

Manage experiment lifecycle

Update targeting, adjust traffic splits, or archive completed experiments.

Validate implementation

Check that you correctly configured your feature flag before launching an experiment.

Install the PostHog MCP