> ## Documentation Index
> Fetch the complete documentation index at: https://docs.reelevant.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Split (A/B Testing)

> Divide traffic into multiple branches based on population share percentages

<img src="https://mintcdn.com/reelevant/amH2YHA9709Bju3v/images/workflows/node-split.png?fit=max&auto=format&n=amH2YHA9709Bju3v&q=85&s=ef11182a34e68688a80a915104b603bd" alt="Split node configuration panel showing group distribution with percentage slider" width="1024" height="768" data-path="images/workflows/node-split.png" />

## Overview

Split nodes divide traffic into multiple branches based on **population share percentages**. This is used for A/B testing or multivariate testing.

## Configuration

* **Variant count** — Add two or more groups using the **Add** button. Groups are automatically labelled A, B, C, and so on.
* **Population share** — Use the slider to set the percentage of traffic each group receives. The total across all groups always equals 100%.
* **Remove** — Click the delete button on any group row to remove it (minimum two groups required).

## Example

| Group     | Population Share |
| --------- | ---------------- |
| Variant A | 50%              |
| Variant B | 30%              |
| Control   | 20%              |

## How It Works

When a user triggers the workflow, the split node randomly assigns them to one of the groups based on the configured percentages. The assignment is deterministic per user — the same user will always follow the same branch.

## Best Practices

* Always include a **control group** (e.g., 10-20%) to measure the impact of personalization.
* Run tests for a sufficient duration to achieve statistical significance before drawing conclusions.
* Use [branch categories](/product-guide/workflows/branches) to tag split branches for analytics.