A Multi-path Branch splits the Workflow into multiple paths at a single decision point. Each branch has its own condition, and users follow the first branch they qualify for. Anyone who doesn't match any branch follows the default "else" path.

Use it when you need more than two paths — for example, sending different follow-ups to NPS detractors, passives, and promoters, or routing users to different onboarding sequences based on their role.

How evaluation works

When a user reaches a Multi-path Branch, the Workflow evaluates branches from left to right on the canvas (top to bottom in the settings panel). The user proceeds down the first branch they match. If they match multiple branches, they still only follow the first one. If they match none, they follow the "else" path.

Add a Multi-path Branch to the canvas

1. Click any + button on the Workflow canvas.
2. Under Logic, select Multi-path Branch.

3. Choose what to condition branches on: User Property or Segment.

4. Add branches and define a condition for each one. Click + Add branch to create additional paths.
5. Add content to each branch by clicking the + button below any branch on the canvas.

Branches reflect their conditions directly on the canvas, so you can see the routing logic at a glance.

Reorder and manage branches

Drag and drop branches in the settings panel to change their evaluation order. Put more specific conditions first and broader conditions later, since users follow the first match.

If you change the attribute type (for example, switching from Segment to User Property), the messages and logic on each branch are preserved but the condition values are cleared. You'll need to re-enter them.

A/B/C testing with Multi-path Branch

Use the Audience Randomizer user property to create randomized branches for experiments with more than two variants. Set up one branch per variant plus a default holdout or control branch, and make sure the ranges cover 1–100 without gaps.

For example, an even three-way split:

• Branch 1: Audience Randomizer is between 1 and 33
• Branch 2: Audience Randomizer is between 34 and 66
• Else (control): covers 67–100 automatically

Keep targeting identical across variants aside from the randomization rule so that the only variable is the content each group sees.

Best practices

• Prefer Multi-path over nested True/False branches. A single Multi-path node is easier to read and maintain than a chain of binary splits.
• Keep conditions mutually exclusive when possible. This avoids confusion about which branch a user follows.
• Use descriptive branch labels. Name branches after the outcome ("Promoters," "Free tier," "iOS users") rather than the condition logic.
• Review the else path. Make sure the default path has appropriate content or is intentionally empty.

Converging paths

You can connect multiple branches back to a shared node after the branch. This lets you run different message sequences per branch but then continue with a unified Workflow for everyone — for example, sending tailored onboarding emails per role, then funneling all users into the same activation check.

If users aren't entering the expected branch

• Check evaluation order. The intended branch may be below a broader branch that's catching users first. Drag it higher in the settings panel.
• Confirm the user's property value or segment membership in Studio matches what the branch condition expects.
• If too many users land in the else path, the branch conditions may be too narrow. Broaden them or add an extra branch with relaxed criteria before the default.

If Flows aren't appearing after a branch

• Verify the Flow's URL targeting, triggering, and frequency settings.
• Confirm the user is logged into your app and meets the Flow's trigger criteria.
• Check whether a Maximum wait is set on the Flow node so users can progress if they don't see it.