Random Split node reference
Use a Random Split to send visitors down different paths. See how equal groups work, how assignments persist, and what changes when you add or remove a group.
A Random Split sends visitors down different paths without checking an audience rule. Choose Split in the insertion menu to add one. Each group gets an equal share of the random-number range used to assign visitors.
When to use it
Use a Random Split when you want visitors to see different sequences of steps, regardless of their answers or segments.
For example, WorkForge (opens in a new tab) could put a planning question in Group 1 and a collaboration question in Group 2. Both paths could then rejoin at a shared form or offer.
If the path should depend on what you know about someone, use a Condition or Router instead. A random group isn't an audience segment.
Settings
A new node starts with two empty branches named Group 1 and Group 2.
| If you'd like to… | What to know |
|---|---|
| Add a group | Add another random split adds an empty branch. |
| Change a group's name | Names come from each group's position. You can't give them custom labels. |
| Change the traffic split | Every group gets an equal share. There are no custom percentage weights. |
| Reorder groups | The editor doesn't offer drag reordering. |
| Remove an empty group | The editor removes it immediately. |
| Remove a group with steps | The editor asks you to confirm deleting the populated path. Canceling keeps the group and its steps. |
The chart icon beside each group doesn't currently open a score editor here. To award points on a branch, put a Set Data node inside it.
How visitors move through it
RightMessage uses a persistent random number for each visitor. It divides the number's range by the current number of groups, then follows the visitor's assigned branch. It doesn't choose a new number on every page view.
With two groups, each gets half the range. With three, each gets one third. Small samples won't necessarily have exactly equal visitor counts.
After a branch finishes, visitors can continue to shared steps below the split. A form, offer, message, redirect, or exit can end the selected path, depending on that node's behavior.
In WorkForge's example, either question can lead to a shared form. If each group needs a different offer, the offer belongs inside that group's path. That offer ends the route. The visitor won't continue into the other group or see a second offer after the split.
Things to know
Changing groups can change assignments
Adding or removing groups changes the boundaries of each group's random-number range. An existing visitor can move to a different group after that change. Clearing browser state can also change their assignment.
Group labels describe positions, not permanent audiences. If you remove Group 1, later labels move to different paths. Review every path after adding or removing groups, and don't compare counts across that change as if membership stayed the same.
Before publishing, make sure every branch is complete. Use fresh visitor states to try different assignments. Use the same remembered visitor to check that reloading doesn't reroll the split.
A Random Split isn't a managed A/B test
This node doesn't create a test lifecycle, confidence report, or winner-promotion workflow. Use whole-flow A/B testing when you need those controls.
The separate A/B Test item in the insertion menu is marked coming soon. It isn't available to add to the canvas. Live whole-flow A/B testing is a different control.