> 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/flagship-deprecated/steps-configuration/dynamic-allocation.md). # Dynamic allocation ## 📖 Definition Dynamic allocation (also called Multi-Arm bandit) is a method used to divert new traffic to the best performing variation depending on the results of each variation. It is based on the Thomson algorithm. ⚙️ Configuration\\ If one variation is performing better than the others, that is to say, if one variation has more unique conversions on the KPI you configured, new traffic will progressively be sent to that variation. Dynamic allocation is only available for A/B Tests.\ Dynamic allocation only works for new users (for an application)/visitors (for a website). If a user is assigned to a variation and returns to the website, they will still see the same variation, even if this variation is under-performing. The allocation of a recurring visitor doesn’t change over time.\ Dynamic allocation only takes into account unique conversions ## 💡 Use case The Dynamic Allocation algorithm is particularly suited to websites/applications with a lot of traffic. As soon as your A/B Test has at least one conversion **for each variation** on the selected KPI, the algorithm starts running and your users will progressively be redirected to the best performing variation. **Need additional information?** Submit your request at Always happy to help! --- # 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.abtasty.com/flagship-deprecated/steps-configuration/dynamic-allocation.md?ask=&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.