> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/ab-test/create-and-configure/traffic-allocation.md).

# Traffic Allocation

{% hint style="warning" %}
Traffic allocation is available in all environments.

* Traffic allocation set in the Production Environment applies only to the Production Environment.
* Traffic allocation set in the Development Environment applies only to the Development Environment.
  {% endhint %}

{% hint style="info" %}
Why use the traffic allocation feature?

To minimize the impact of unexpected bugs or unintended customer experience issues, you can use the traffic allocation feature to start an A/B Test with a small percentage of traffic and gradually increase it.
{% endhint %}

Traffic Allocation is a feature that configures how many users out of all users should be exposed to the A/B Test.

You can configure it when starting an A/B Test in the **`Production Environment`**, and after starting, by clicking the **`Traffic Allocation`** button in the upper right of the A/B Test detail page.

![Traffic allocation at test start](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-d44ad6ba18a5f6441a38ad852729047b2b85a269%2F7823a3f-traffic-alloc-1_8d0f7ac8c8ea4a46.png?alt=media)

![Traffic allocation after test start](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-8eeacde13797accfcf0add14fcfb1af8787858cc%2Fb9d748d-traffic-alloc-2_3032a56c931dea0f.png?alt=media)

## 1. Enter the desired traffic percentage

Clicking the button displays a popup where you can change the Traffic Allocation setting. Enter the traffic percentage in the text box in the middle area of the popup.

The traffic percentage to allocate to the A/B Test can only be entered as an integer between 0(%) and 100(%), and **you cannot change it to a value lower than the previously configured value**.

![If the previous value was 50, you must enter a value greater than or equal to 50.](https://143363954-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FyAVlNQhS253reum0Ce94%2Fuploads%2Fgit-blob-ff375ed21f80b12995888cbaa9ab5cdbe9941030%2Fd977ffb-traffic-alloc-3_9f64ba414e329ce1.png?alt=media)

## 2. Apply the setting

Click the **`Allocate`** button in the lower right to apply the changed traffic allocation percentage.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hackle.io/en/ab-test/create-and-configure/traffic-allocation.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
