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
      • Get started with engineering insights
      • Project overview
      • Project metrics
        • Deployments
        • Releases
        • Lead time
        • Flag health
        • Experimentation rate
    • 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
    • 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 summary
  • Experimentation rate
  • Flag changes
ReleasesEngineering insightsProject metrics

Experimentation rate

Was this page helpful?
Previous

Release management tools

Next
Built with
Engineering insights is not available in LaunchDarkly's European Union (EU) instance
To learn more, read LaunchDarkly in the European Union (EU).

Overview

This topic explains how to use the Experimentation rate page in engineering insights.

Experiments let you measure the effect of flags on end users by tracking metrics your team cares about. You can measure things like page views, clicks, load time, infrastructure costs, and more. By connecting metrics you create to flags in your LaunchDarkly environment, you can measure the changes in your customers’ behavior based on what flags they evaluate. This helps you make more informed decisions, so the features your development team ships align with your business objectives. To learn more, read Experimentation.

The Experimentation rate page displays the number of flag changes that are associated with an experiment.

Experimentation summary

The Experimentation summary includes the following information:

  • Percentage of flag changes with experiments
  • Total number of changes with experiments
  • Total number of changes

The Experimentation summary.

The Experimentation summary.

Use the selection menus to narrow your view to a specific LaunchDarkly project or environment, or one or more applications. You can also change the selected time range to the last 1, 2, 4, or 12 weeks, or a custom range.

Experimentation rate

The Experimentation rate chart tracks the number of flag changes with and without experiments by date.

The Experimentation rate chart.

The Experimentation rate chart.

Flag changes

The flag changes list displays the following information:

  • The flag name. Click on the flag name to view the full flag details in the Flags list.
  • The date of the flag change.
  • The name of the member who made the flag change.
  • Which experiment the flag change is associated with. Click on the experiment name to view the associated experiment iteration.
  • The kinds of changes made.

You can filter by flag changes with or without experiments, and search by flag key or experiment name.

The Experimentation flag changes list.

The Experimentation flag changes list.