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
      • Experimentation prerequisites
      • Quickstart for Experimentation
      • Experimentation and metric events
    • 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
  • SDK requirements
  • SDK version number
  • SDK configuration
  • Relay Proxy
  • Role permissions
ExperimentationExperimentation

Experimentation prerequisites

Was this page helpful?
Previous

Quickstart for Experimentation

Next
Built with

This topic explains the prerequisites required to use LaunchDarkly Experimentation. Before you begin, your SDKs must meet the minimum version requirements and be configured to send events, and you must have the required permissions in LaunchDarkly. If you use the Relay Proxy, it must also meet the minimum version requirements and be configured to send events.

These prerequisites are explained in detail below.

SDK requirements

Your SDKs must meet the following requirements.

SDK version number

You must be using the listed version number or higher for the following SDKs:

Click to expand a table listing required client-side SDK versions

Client-side SDKs:

SDKVersion
.NET (client-side)2.0.0
Android3.1.0
C++ (client-side)2.4.8
ElectronAll versions
Flutter0.2.0
iOSAll versions
JavaScript2.6.0
Node.js (client-side)All versions
React Native5.0.0
React WebAll versions
RokuAll versions
VueAll versions
Click to expand a table listing required server-side SDK versions

Server-side SDKs:

SDKVersion
.NET (server-side)6.1.0
Apex1.1.0
C/C++ (server-side)2.4.0
Erlang1.2.0
Go5.4.0
Haskell2.2.0
Java5.5.0
Lua1.0
Node.js (server-side)6.1.0
PHP4.1.0
Python7.2.0
Ruby6.2.0
Rust1.0.0-beta.1
Click to expand a table listing required AI SDK versions

AI SDKs:

SDKVersion
.NET AI SDK0.1
Go AI SDK0.1
Node.js (server-side) AI SDK0.1
Python AI SDK0.1
Ruby AI SDK0.1
Click to expand a table listing required edge SDK versions

Edge SDKs:

SDKVersion
Cloudflare2.3.0
Vercel1.2.0

If you use holdouts and are using a client-side SDK, your minimum SDK versions may differ from those listed above. To find the minimum required version for holdouts, read Supported features.

SDK configuration

You must configure your SDKs to do the following:

  • Send events to LaunchDarkly: If you have disabled sending events for testing purposes, you must re-enable it.
    • For client-side, server-side, and edge SDKs, the all flags feature sends events for some SDKs, but not others. For SDKs that do not send events with the all flags feature, you must call the variation method instead. If you call the variation method, you must use the right variation type.
    • For AI SDKs, the AI metrics feature sends events.

To learn more about the events SDKs send to LaunchDarkly, read Analytics events.

Relay Proxy

If you use the LaunchDarkly Relay Proxy, it must be at least version 8, and you must configure it to send events.

If you use holdouts and are using a client-side SDK, the minimum required version of Relay Proxy is 8.10. To learn more, read Configuring an SDK to use the Relay Proxy.

Role permissions

To start, stop, and edit experiments, you must have an Admin, Owner, or Writer base role, or a custom role with the following permissions for the specific environments you plan to run experiments in.

Experiment actions include:

  • createExperiment
  • updateExperiment
  • updateExperimentArchived

Feature flag actions include:

  • createFlag
  • updateOn
  • updateFallthrough
  • updateRules

Holdout actions include:

  • addExperimentToHoldout
  • createHoldout
  • removeExperimentFromHoldout
  • updateHoldoutDescription
  • updateHoldoutMethodology
  • updateHoldoutName
  • updateHoldoutStatus
  • updateHoldoutRandomizationUnit

To learn more, read Member role concepts.