Lifecycle Automation with Journey: From Segment to Measurable Outcome

What is Journey?

Journey is the module that automates the player lifecycle through a flow you draw. Segmentation answers "who"; Journey answers "when, in what order, and how will we measure the result".

It is one of the most important features of the Professional package, and it is not merely a campaign tool: it is an operations engine.

Four node types

A flow is built from four kinds of node:

• Trigger — the event that starts the flow (first deposit, losing streak, inactivity, segment change)
• Condition — the branching point (segment, amount threshold, channel consent, the previous step's outcome)
• Action — the work performed (granting a bonus, sending a message, tagging, creating a task)
• AI decision — a node where the next step is left to the model

Together these four cover everything from a simple welcome series to a multi-stage win-back structure.

Governance lives in the engine, not in the flow

This is Journey's critical difference: frequency caps, quiet hours and channel consent are not redrawn in every flow. They live inside the engine.

The last row is the one most often overlooked. Every bonus trigger is written with a unique key, so even if the same event is processed twice, the player receives the bonus once.

No control group, no result

Journey flows are built with a target event and a control group. The target event is the behaviour that counts as success (a second deposit, a return, completed wagering). The control group is the part of the same segment deliberately kept out of the flow.

Without those two, the sentence you are left with is: "we ran the campaign and deposits went up." That sentence proves nothing, because deposits may have risen regardless.

The sentence a control group produces is different: "the group that entered the flow made this many more second deposits than the group that did not." That sentence is enough to make a budget decision.

Four typical flows

1. Welcome series — a staged flow after the first deposit, aimed at the second
2. At-risk win-back — early intervention for a high-value player drifting away
3. Dormant reactivation — a personalised offer for long-inactive accounts
4. VIP protection — prioritised contact when behaviour shifts in the Champions segment

All four are built the same way: the segment triggers, the condition branches, the action executes, the control group measures.

How it relates to the other modules

Journey does not work alone. Segmentation triggers the flow, the Bonus Engine defines the reward, Omnichannel delivers the message on the right channel, and Atlas carries the player's historical context into the flow. Because they all run on the same data model, the outcome is visible in one panel.

Explore the segmentation module →

Bonus Engine module page →

Which package?

Journey is one of the features of the Professional package. Combined with predictive segmentation in the Enterprise package, flows can be triggered before a player changes segment.

See pricing →