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
      • Creating experiments
      • Allocating experiment audiences
      • Randomization units
      • Variation reassignment
      • Mutually exclusive experiments
    • Managing experiments
    • Analyzing experiments
    • 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
  • Disable variation reassignment
  • Example of an experiment with variation reassignment disabled
ExperimentationExperiment configuration

Variation reassignment

Was this page helpful?
Previous

Mutually exclusive experiments

Next
Built with

Overview

This topic explains how LaunchDarkly reassigns contexts to flag variations when you change or increase traffic in an experiment.

When you make certain edits to an experiment, such as adding additional metrics or increasing traffic, LaunchDarkly creates a new experiment iteration. By default, LaunchDarkly reshuffles experiment traffic when you start a new iteration to help keep traffic balanced between variations.

If you want to keep contexts assigned to their original variation, you can disable variation reassignment for your experiment. You may want to do this when it’s important to minimize disruption to the end-user experience, such as when different variations display different versions of navigation menus or other significant user interface (UI) elements.

Preventing variation reassignment only applies when you increase the percentage of traffic in an experiment without decreasing it between iterations. For example, increasing traffic from 5% to 20% to 60% preserves existing assignments. If you decrease traffic and then increase it again, such as from 20% to 5% to 60%, LaunchDarkly reassigns contexts to different variations.

Disable variation reassignment

To disable variation reassignment for a new or existing experiment:

  1. Navigate to the experiment’s Design tab.
  2. In the “Audience allocation” section, click Advanced.
  3. Check the Prevent variation reassignment when traffic increases checkbox.

This setting only preserves assignments when you increase traffic. Decreasing traffic and then increasing it again may result in reassignment.

Traffic will be assigned to new variations if you stop an experiment

Checking the Prevent variation reassignment when traffic increases checkbox prevents variation reassignment only if you make changes to an experiment using the experiment’s Edit design button.

If you use the Stop button instead, LaunchDarkly will always reshuffle traffic into new variations when you start a new iteration, whether or not this box is checked.

Example of an experiment with variation reassignment disabled

Here is an example of running an experiment with variation reassignment disabled: you add an experiment to a flag with three variations: A, B, and C. You roll out the three variations to 6% of contexts, while the remaining 94% receives the control, variation A. The control traffic is not part of the experiment nor its analysis.

Here is a visualization of the starting traffic allocation, with the control group on the right:

An experiment audience with 6% in the experiment and 94% in the control group.

An experiment audience with 6% in the experiment and 94% in the control group.

Next, you increase your experiment to 30% of traffic. This creates a new iteration of the experiment. In the new iteration, the 6% that were receiving variations A, B, and C, continue to receive those variations, but are no longer included in the experiment nor its analysis. New traffic is used for the 30% allocated to the experiment.

Here is an example of the modified allocation, with the control group on the right and the original experiment audience on the left:

An experiment audience with 6% no longer in the experiment, 30% in the experiment, and 64% in the control group.

An experiment audience with 6% no longer in the experiment, 30% in the experiment, and 64% in the control group.