> For the complete documentation index, see [llms.txt](https://docs.abtasty.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.abtasty.com/feature-experimentation-and-rollout/campaign-creation/how-to-create-server-side-a-b-tests.md).

# A/B Test Campaign

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](https://app.gitbook.com/s/BWu23t7Qv6wLLh6Hl5b4/sdks/js-sdk/archived-versions/archived-js-v40x/archived-js-v40x-installation))

{% hint style="warning" %}
**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.
{% endhint %}

### Campaign Creation Flow

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

{% stepper %}
{% step %}

### Main Informations

Define the campaign type, environment, and core configuration.
{% endstep %}

{% step %}

### Variations

Configure the different variations using feature flags.
{% endstep %}

{% step %}

### Goals

Select the KPIs used to evaluate performance.
{% endstep %}

{% step %}

### Targeting

Define which users are eligible for the campaign.
{% endstep %}

{% step %}

### Traffic Allocation

Decide how traffic is distributed across variations.
{% endstep %}

{% step %}

### Advanced Options

Configure additional settings such as risk management options.
{% endstep %}

{% step %}

### Overview

Review the full configuration before launching the campaign.
{% endstep %}
{% endstepper %}

***

### 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.abtasty.com/feature-experimentation-and-rollout/campaign-creation/how-to-create-server-side-a-b-tests.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.