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
    • Multi-armed bandits
      • Creating multi-armed-bandits
      • Editing and archiving multi-armed bandits
      • Multi-armed bandit results
    • 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
  • Methodology
  • The Multi-armed bandits list
Experimentation

Multi-armed bandits

Was this page helpful?
Previous

Creating multi-armed bandits

Next
Built with

Overview

This section contains documentation on multi-armed bandits (MABs), which are a type of experiment that uses a decision-making algorithm that dynamically allocates traffic to the best-performing variation of a flag based on a metric you choose.

Unlike traditional A/B experiments, which split traffic between variations and waits for performance results, MABs continuously evaluate variation performance and automatically shift traffic toward the best performing variation. MABs are useful when fast feedback loops are important, such as optimizing calls to action, pricing strategies, or onboarding flows.

A multi-armed bandit probability density chart.

A multi-armed bandit probability density chart.

To learn how to create and read the results for MABs, read Creating multi-armed bandits and Multi-armed bandit results.

Methodology

LaunchDarkly’s multi-armed bandit implementation uses Thompson Sampling. Thompson Sampling is a Bayesian algorithm that balances exploration, which gathers data by allocating traffic across variations, and exploitation, which shifts more traffic toward the better-performing variation.

Thompson Sampling works by estimating posterior distributions for the mean of each variation. Then, LaunchDarkly estimates the probability that each variation is the best using the Monte Carlo method. Next, LaunchDarkly updates the MAB’s traffic allocation so each variation receives traffic equal to its probability to be best. You choose how often LaunchDarkly updates traffic allocation when you create the MAB.

To learn more about Thompson Sampling, read A Tutorial on Thompson Sampling.

The Multi-armed bandits list

You can view information about your new, running, and stopped multi-armed bandits on the Multi-armed bandits list.

The Multi-armed bandits list includes the following information about each multi-armed bandit:

  • Name: The name of the multi-armed bandit
  • Status: Not started, running, or stopped. Hover over the status to view more information.
  • Duration: How long the multi-armed bandit has been running.
  • Started: The date and time that you started the multi-armed bandit.
  • Stopped: The date and time that you stopped the multi-armed bandit. If this column is blank, the multi-armed bandit has either not been started or is still running.
  • Metrics used: Any primary or secondary metrics and any metric groups used in the multi-armed bandit. Hover over the metric name to view a full list of all metrics used.
  • Maintainer: The member who created the multi-armed bandit.

You can show or hide any of these columns by clicking the Display menu at the top of the list, and selecting or deselecting the appropriate column.

Click the three-dot overflow menu for a multi-armed bandit to copy the multi-armed bandit key, copy a direct link to the multi-armed bandit, or archive the multi-armed bandit.

Click on a MAB name from the list to open the multi-armed bandit. You can then:

  • Edit the MAB design
  • View MAB results
  • Stop the MAB or start a new iteration
  • Leave comments about the MAB on the Discussion tab in the right sidebar
  • View MAB data over set periods of time from the Iterations tab