A/B Test Campaign

An A/B test campaign in Feature Experimentation and Rollout (FE&R) allows you to compare multiple backend-driven variations of a feature and measure their impact on your business KPIs.

In a server-side context, experiments are powered by feature flags. Variations are defined by different flag values and evaluated through the SDK or Decision API.

Before you start

Before creating an A/B test campaign, make sure you have:

• The required permissions to create and manage campaigns
• A flag configured
• Relevant context keys defined for targeting
• The FE&R SDK properly installed (FE&R SDK installation)

Permissions required

Creating or editing a campaign requires appropriate permissions on the folder and environment.

Only users with sufficient rights (User or Admin role on the folder) can create or modify campaigns.

Campaign Creation Flow

Creating a server-side A/B test campaign follows a structured 7-step flow:

1

Main Informations

Define the campaign type, environment, and core configuration.

2

Variations

Configure the different variations using feature flags.

3

Goals

Select the KPIs used to evaluate performance.

4

Targeting

Define which users are eligible for the campaign.

5

Traffic Allocation

Decide how traffic is distributed across variations.

6

Advanced Options

Configure additional settings such as risk management options.

7

Overview

Review the full configuration before launching the campaign.

---

Activation

Once your campaign is fully configured and validated, you can activate it from the campaign header or from the dashboard.

Changing the campaign status from Draft to Live will start the experiment and begin data collection.