For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
Sign inTry it free
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
DocsGuidesSDKsIntegrationsAPI docsTutorialsFlagship blog
  • Get started
    • Overview
    • Onboarding
    • Get started
    • Launch Insights
    • LaunchDarkly architecture
    • LaunchDarkly vocabulary
  • AgentControl
    • AgentControl
    • Manage AgentControl
  • Feature flags
    • Create flags
    • Target with flags
    • Flag templates
    • Manage flags
    • Code references
    • Contexts
    • Segments
  • Releases
    • Releasing features with LaunchDarkly
    • Release policies
    • Percentage rollouts
    • Progressive rollouts
    • Guarded rollouts
    • Feature monitoring
    • Release pipelines
    • Engineering insights
    • Release management tools
    • Applications and app versions
    • Change history
    • Restoring previous flag versions
  • Observability
    • Observability
    • Session replay
    • Error monitoring
    • Logs
    • Traces
    • Observability metrics
    • Product analytics events
    • LLM observability
    • Alerts
    • Dashboards
    • Service map
    • Vega for auto-remediation
    • Observability MCP server
    • Search specification
    • Observability settings
    • Observability integrations
  • Experimentation
    • Experimentation
    • Experiment metric types
    • Experiment configuration
    • Managing experiments
    • Analyzing experiments
      • Experiment results data
      • Bayesian experiment results
      • Frequentist experiment results
      • Filtering experiment results
    • Multi-armed bandits
    • Holdouts
  • Metrics and events
    • Metrics in LaunchDarkly
    • Creating metrics
    • Metric groups
    • Events
    • Autogenerated metrics
  • Warehouse native
    • Warehouse native metrics
    • Setting up external warehouses
    • Creating experiments using warehouse native metrics
  • Infrastructure
    • Connect apps and services to LaunchDarkly
    • LaunchDarkly in China and Pakistan
    • LaunchDarkly in the European Union (EU)
    • LaunchDarkly in federal environments
    • Public IP list
  • Your account
    • Projects
    • Views
    • Environments
    • Tags
    • Teams
    • Members
    • Roles
    • Account security
    • Feature previews
    • Billing and usage
    • Changelog
Sign inTry it free
LogoLogo
On this page
  • Overview
  • Bayesian and frequentist analysis
  • CUPED
  • Multiple comparisons correction
  • Sequential testing
  • Sample ratio mismatch (SRM) detection
  • Stratified sampling
  • Related topics
Experimentation

Analyzing experiments

Was this page helpful?
Previous

Experiment results data

Next
Built with

Overview

This topic explains the experiment analysis options available in LaunchDarkly.

Bayesian and frequentist analysis

LaunchDarkly offers two different approaches for analyzing your experiment: Bayesian and frequentist. Within the frequentist approach, you can choose a traditional fixed-horizon analysis or a sequential analysis.

To learn more, read the following guides:

  • Choosing a statistical methodology
  • Statistical methodology for Bayesian experiments
  • Statistical methodology for frequentist experiments

CUPED

Controlled-experiment using pre-experiment data (CUPED) is a statistical method that uses data collected before an experiment begins to reduce variance in experiment results. Applying CUPED to experiment results makes it easier to detect differences between variations.

To learn more, read Covariate adjustment and CUPED methodology.

Multiple comparisons correction

Multiple comparisons correction (MCC) helps reduce false positives in frequentist experiment results.

To learn more, read the following topics:

  • To learn how to apply MCC to a new experiment, read Creating experiments.
  • To learn how to remove MCC from an existing experiment, read Statistics information
  • To learn about our MCC methodology, read Multiple comparisons correction.

Sequential testing

Sequential testing lets you make decisions about frequentist results without needing to calculate a sample size first.

To learn more, read the following topics:

  • To learn how to apply sequential testing to a new experiment, read Creating experiments.
  • To learn more about when to use sequential testing, read Fixed-horizon versus sequential.

Sample ratio mismatch (SRM) detection

In an experiment, the sample ratio is the ratio between end users in each of your experiment variations. An SRM is a mismatch between the number of users expected and the actual number of users included in each variation. SRM detection alerts you to any issues with your JavaScript-based SDK setups.

To learn more, read Sample ratio mismatch.

Stratified sampling

Stratified sampling helps eliminate covariate imbalance and reduce false positives and false negatives in your experiment results.

To learn more, read the following topics:

  • To learn how to apply stratified sampling to a new experiment, read Creating experiments.
  • To learn how it works, read Stratified sampling.

Related topics

To learn how to interpret the results of your experiments, read the following topics:

  • Experiments results data
  • Bayesian experiment results
  • Frequentist experiment results.