> 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/main-information.md).

# Main Information

<figure><img src="/files/SawGJmKb960H4m85nsKc" alt=""><figcaption></figcaption></figure>

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

{% 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 %}

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

{% hint style="info" %}
*Learn more about* [*managing environments*](https://app.gitbook.com/o/iFKI1JaxSfPoiGt4tT2k/s/6Yw9IRJ6KbbucQPwZUCZ/~/edit/~/changes/471/feature-experimentation-and-rollout/sdk-and-environments/managing-environments)
{% endhint %}

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

{% hint style="info" %}
*Learn more about* [*bucket attribution*](https://app.gitbook.com/o/iFKI1JaxSfPoiGt4tT2k/s/6Yw9IRJ6KbbucQPwZUCZ/~/edit/~/changes/471/feature-experimentation-and-rollout/sdk-and-environments/managing-environments)
{% endhint %}

**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...&#x20;

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

{% hint style="info" %}
*Learn more about* [*managing folders*](https://app.gitbook.com/o/iFKI1JaxSfPoiGt4tT2k/s/6Yw9IRJ6KbbucQPwZUCZ/~/edit/~/changes/471/feature-experimentation-and-rollout/managing-folders-in-fe-and-r)
{% endhint %}

**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](/feature-experimentation-and-rollout/campaign-creation/how-to-create-server-side-a-b-tests/variations.md)


---

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

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

The question should be specific, self-contained, and written in natural language.
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.