Experimentation prerequisites

Overview

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:

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.