# Traffic allocation

In Flagship, traffic allocation depends on a combination of a [Murmurhash algorithm](https://en.wikipedia.org/wiki/MurmurHash) and a [variationGroupId](https://developers.flagship.io/docs/glossary#variation-group-id). Each visitorId sent to the API (through POST request or thanks to the SDK) will be processed by this algorithm and, depending on the results, the visitor will be assigned to a specific variation.

The API uses the same bucket-style as the [bucketing](https://developers.flagship.io/docs/bucketing) feature.\
Depending on the percentage of traffic you configured in the platform, visitors will be assigned to a specific bucket.\
It is the same principle for dynamic allocation. The only difference is that the allocation changes depending on report results. However, a user who has already been assigned to a variation will still see the same variation. Dynamic allocation redirects only new visitors to the best performing variation.\
[Learn more about dynamic allocation](https://flagship.zendesk.com/hc/en-us/articles/360017551060).

**Need additional information?**

Submit your request at <product.feedback@abtasty.com>

Always happy to help!


---

# Agent Instructions: 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/flagship-deprecated/steps-configuration/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.
