> 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/traffic-allocation.md).

# Traffic Allocation

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

Use the **Traffic allocation** step to define how the campaign traffic is split between the **Original** and your **variation**.

In Feature Experimentation and Rollout, this step uses a **standard traffic allocation** for A/B tests. You decide what percentage of the campaign traffic goes to the variation, while the remaining tracked traffic stays on the Original.

### How it works

The page is divided into two main areas:

* **Global traffic:** where you define how much traffic is allocated to variations, how much remains on the Original, and how much is left as untracked traffic
* **Traffic distribution by variation:** which shows a visual summary of the current split

For a simple A/B test with one variation:

* the traffic allocated to the variation is taken from the total campaign traffic
* the remaining tracked traffic is allocated to the Original
* untracked traffic is not included in the test results

If untracked traffic is set to `0%`, all campaign traffic is tracked and split between the Original and the variation.

### Configure the traffic allocation step

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

1. In **Global traffic**, set **Traffic allocated to variations**.
2. Review the **Original** value, which adjusts based on the remaining tracked traffic.
3. In **Variations Traffic**, review the allocation for your variation.
4. Check the chart in **Traffic distribution by variation** to confirm the final split.
5. Click **Save**.

### Recommended setup for an A/B test

For a standard A/B test with one Original and one variation, the recommended setup is:

* `50%` for the Original
* `50%` for the variation
* `0%` untracked traffic

An even split is usually the simplest setup for comparing performance between the two versions.

### Important details

* **Untracked traffic** sees the Original version but is not counted in the test reporting.
* Lowering tracked traffic also lowers the size of the test sample.
* If you change the traffic allocation while the campaign is live, only new visitors are affected by the new split.
* To keep reporting easier to interpret, it is best to avoid changing the allocation during the campaign unless necessary.


---

# 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/traffic-allocation.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.