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
        • Shipping the winning variation
        • Decision making with Bayesian statistics
        • Outliers in Bayesian experiments
      • 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
  • Ship the winning variation
ExperimentationAnalyzing experimentsBayesian experiment results

Shipping the winning variation

Was this page helpful?
Previous

Decision making with Bayesian statistics

Next
Built with

This topic explains how to choose and ship a winning variation for a completed Bayesian experiment.

To learn about winning variations in frequentist experiments, read Frequentist experiment results.

For experiments using Bayesian statistics, the winning variation is the variation with the highest probability to be best that exceeds the Bayesian threshold you set when you created the experiment.

If a Bayesian experiment has collected enough data to determine a winning variation, and the winning variation is not the control, then the winning variation is highlighted in green in its results table.

If all treatment variations have a significantly low probability of beating the control, then the control is considered the winning variation. To learn more, read Decision making with Bayesian statistics.

Ship the winning variation

To stop an experiment and ship the winning variation:

  1. Navigate to the experiment’s Results tab.
  2. Click Stop. The “Ship” menu appears.
  3. Select the winning variation to ship to all contexts that match the flag’s targeting rule. A “Stop experiment” dialog appears.
  4. Enter a Reason for stopping.
  5. Click Stop experiment.

Bayesian experiments also display a Ship it button if the experiment has enough data to determine a winning variation, and that winning variation is not the control. You can use this option to stop the experiment and ship the winning variation.