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
  • Overview
  • Experimentation outlier handling
ExperimentationAnalyzing experimentsBayesian experiment results

Outliers in Bayesian experiments

Was this page helpful?
Previous

Frequentist experiment results

Next
Built with

Overview

This topic explains how LaunchDarkly Experimentation handles outliers in its Bayesian experiment analyses.

An outlier is a data point that has a value much higher or much lower than the other points in its data set. Outliers are typically caused by unusual or illogical behavior from someone included in an experiment. If handled incorrectly, an outlier can negatively impact your experiment results by skewing the analysis and making it more difficult to make informed decisions.

For example, imagine you are running an experiment comparing sales revenue for a product when you offer a 10% discount, versus when you offer no discount. Most people buy just one or two of your product at a time, so it’s easy to compare sales volume between the discounted treatment variation and non-discounted control variation. Now imagine that a customer buys 1,500 of your product at full price to distribute to students at the school they work for. This data point is now an outlier, as it is very unusual customer behavior. If not handled correctly, the outlier could make it seem like the full-price variation of your product was more popular than the discounted variation, when this wasn’t true for most customers.

Experimentation outlier handling

Bayesian experiments in LaunchDarkly handle outliers using Bayesian statistics’ built-in handling method. The method uses an experiment’s control variation to create strong priors. This means that, for every experiment, LaunchDarkly includes prior beliefs about your data gathered from the control variation to formulate an expected range of outcomes. This expected range of outcomes is called the posterior distribution. Because LaunchDarkly uses real end-user behavior to create these posterior distributions, the distributions have a small credible interval with low variance. Therefore, any outliers in the variations you’re experimenting on do not have a strong effect on the distribution.

To learn more about prior beliefs in Bayesian statistics, read Frequentist and Bayesian modeling.