Journey automation
Journeys automate multi-step, triggered flows — the difference between a one-off campaign and an always-on lifecycle program.
The visual builder
Compose a journey from nodes:
| Node | Purpose |
|---|---|
| Trigger | What enrols a player (an event, a segment, a schedule). |
| Wait | Delay for a duration or until a time. |
| Condition | Branch on nested AND/OR/NOT logic over player state. |
| A/B split | Randomly split the flow to compare variants. |
| Send | Send a message on a channel. |
| Action | Mutate player state (e.g. tag, status). |
| Goal | Mark a conversion to measure against. |
| Exit | Leave the journey. |
The builder validates the graph, auto-lays-out nodes, and gives a minimap for large flows. A worker engine drains journey runs and advances each enrolled player through the graph.
Playbook library
Journeys → New offers ready-made journeys that clone a prebuilt graph into a draft you can edit:
- Welcome
- First-deposit conversion
- Win-back
- VIP onboarding
- Abandoned deposit
- Re-engagement
Start from a playbook and adapt it, or build from scratch.
Enrolling players
A journey can be triggered by an event (e.g. registration), by segment
membership, or on a schedule. You can also enrol or un-enrol a set of players
explicitly.
Measuring
Per-node analytics show how players flow through the graph — entries, waits, branch splits, sends, and goal conversions — so you can see where a journey converts or drops off.