> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/orchestration/how-to-use-the-random-split-feature.md).
# How to use the Random Split feature?
The Random Split feature allows for multi-branch automations.
With the Random Split feature, divide users into random groups to run tests, optimize your journey or set up a control group logic. Let's go through the steps together :sparkles:
{% stepper %}
{% step %}
## Add a trigger event and a Random Split
Select your trigger event, then add a Random Split at any step of the omnichannel trigger automation.
To do so, simply click on the **+** button and select **Random Split:**
{% endstep %}
{% step %}
## Customize the branches
Customize the branches as you wish!
Click on the **+** button again to add messages, delays, exit events or another split:
{% endstep %}
{% step %}
## Adjust the percentages
Create from 2 to 4 branches and adjust the percentage of users for each of them. Just keep in mind that the sum of branches must always be 100%.
{% hint style="warning" %}
The algorithm for randomization is **efficient for high volumes** but less so for very low volumes. If 30 people receive the automation and the automation has 3 branches (33%, 33%, 34%), you might not have exactly 10 people by branch.
{% endhint %}
🔍 With this feature, automations can get a lot bigger: to get a better overview, use the **mini-map** at the bottom-left corner of your screen to navigate and zoom in and out in the automation:
{% endstep %}
{% endstepper %}
You are now ready to create your own journey using the Random Split feature :rocket:
---
# 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://doc.batch.com/guides-and-best-practices/orchestration/how-to-use-the-random-split-feature.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.
