Main Information

The Main information step defines the foundation of your A/B test server-side campaign.

This is where you configure the core settings that determine how your campaign will run, be identified, and be organized within Feature Experimentation and Rollout (FE&R).

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.

Configuration

Campaign type

A/B Test - used to compare multiple variations of a feature for a specific audience.

In FE&R, A/B test campaigns are powered by feature flags and evaluated through the SDK or Decision API.

Environment

Select the environment in which your campaign will run.

Examples:

• Production

• Staging

• QA

The selected environment determines where the campaign is executed and which users are impacted.

Learn more about managing environments

Bucket attribution

Bucket attribution ensures that users remain consistently assigned to the same variation across sessions.

This is critical in server-side experimentation to:

• Avoid re-bucketing

• Ensure experiment consistency

• Maintain reliable results

You can select one or multiple buckets depending on your setup.

Learn more about bucket attribution

Name

Give your campaign a clear and descriptive name.

Example:

• Homepage CTA – Color Test

• Checkout Flow – Step Reduction

A good naming convention helps teams quickly understand the purpose of the campaign.

Description

Use the description to document your hypothesis and context.

We recommend using the following structure:

If we apply [change] to [audience], then it will impact [behavior] and improve [KPI].

Example:

If we simplify the checkout flow for mobile users, then it will reduce friction and increase conversion rate.

Folder

Assign the campaign to a folder. Folders help you organize campaigns by team, product, feature, business unit...

This is especially important for governance and scalability in large organizations.

Learn more about managing folders

Custom ID (optional)

The Custom ID is an optional identifier that can be used for:

• External reporting alignment

• Internal tracking

• API integrations

Example:

• checkout_ab_test_q1

• pricing_experiment_v2

Next step

Once your main information is configured, proceed to: Variations