Skip to content

Commit 89289f9

Browse files
committed
clarification
1 parent b71ca84 commit 89289f9

File tree

1 file changed

+9
-9
lines changed

1 file changed

+9
-9
lines changed

src/engage/journeys/event-triggered-journeys-steps.md

Lines changed: 9 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -173,34 +173,34 @@ You can use a Data split to branch profiles based on traits or audience membersh
173173

174174
This setup helps tailor journey experiences using reliable, preexisting data. Because the Data split step evaluates conditions instantly, it works best with traits or audience membership that Segment has already computed before the profile enters the step.
175175

176-
## Randomized Split
176+
## Randomized Split (V2)
177177

178178
The **Randomized Split** step lets you experiment with and test the performance of different journey paths. You can add up to five branches, assign each one a percentage, and Segment will randomly send users down one of the branches based on the configured distribution.
179179

180180
This step is useful for A/B testing, holdout groups, and comparing different channels or messaging strategies within a single journey.
181181

182182
For example, you might create a randomized split that sends 40% of users to an email campaign, 40% to an SMS campaign, and 20% to a control group. Once users move through the split, you can evaluate which approach performed best.
183183

184-
### How randomized split works
184+
### How Randomized Split works
185185

186186
When a profile reaches the Randomized Split step:
187187

188188
1. Segment randomly assigns the profile to one of the branches based on the defined percentages.
189189
2. The profile immediately moves down the assigned path.
190190
3. By default, if a user re-enters the journey later, they’re assigned a new random branch. You can optionally choose to keep them in the same branch each time they re-enter.
191191

192-
Each journey instance (epoch) is evaluated independently. This means a user could be assigned to different branches across multiple entries, unless you enable consistent assignment.
192+
Segment evaluates each journey instance independently. This means a user could be assigned to different branches across multiple entries, unless you enable consistent assignment.
193193

194194
### Configuration options
195195

196196
You can configure a Randomized Split step with the following options:
197197

198-
| Setting | Description |
199-
|---------------------------------|-----------------------------------------------------------------------------|
200-
| Branches | Add up to five branches. Each branch must be assigned a percentage. |
201-
| Distribution percentages | Define what portion of users should go down each branch. Total must be 100%. |
202-
| Branch naming | Branches are labeled alphabetically (e.g., Branch A, Branch B). |
203-
| Consistent branch assignment | Optionally ensure a user always enters the same branch on re-entry. |
198+
| Setting | Description |
199+
| ---------------------------- | ---------------------------------------------------------------------------- |
200+
| Branches | Add up to five branches. Each branch must be assigned a percentage. |
201+
| Distribution percentages | Define what portion of users should go down each branch. Total must be 100%. |
202+
| Branch naming | Branches are labeled alphabetically (for example, Branch A, Branch B). |
203+
| Consistent branch assignment | Optionally ensure a user always enters the same branch on re-entry. |
204204

205205
Segment blocks publishing if the percentages don’t add up to 100%, or if any percentage is left blank.
206206

0 commit comments

Comments
 (0)