Configure Journey steps and branches
After configuring who can enter a Journey, add steps to define what happens to each profile and in which order.
Steps can delay progression, split profiles into branches, activate destinations, or end a path. Add only the steps required by your use case.
Add and configure a step
Click the + button at the point where you want to add a step.
Select the step type.
Configure the step in the side panel.
Save the configuration.
You can select an existing step to review or update its configuration while the Journey is editable.
Choose the right step
Wait
Progression should resume after a fixed duration.
Segment
Profiles should follow different paths based on a current profile field.
Random Split
Profiles should be distributed randomly across percentage-based variants.
Pause Until
Progression should resume when a profile condition becomes true or an event occurs.
Activate
Profiles should be sent to one or more activation targets.
Stop
A path should end explicitly.
Delay progression with Wait
Wait keeps profiles at the current point for a fixed duration.
Set a positive whole number and choose one of the following units:
hours;
days;
weeks.
The total duration cannot exceed 365 days.
For example, you can add a Wait before an Activate step when profiles should not be sent to a destination immediately after entering the Journey.
Use Wait when elapsed time is the only condition. If progression should resume as soon as a profile attribute changes or an event occurs, use Pause Until instead.
Create branches with Segment
Segment routes profiles according to the value of a field in the Customer Hub profile model.
Select a supported categorical or Boolean field, then create the groups that should have their own paths.
Each group must:
have a unique name;
contain at least one field value;
use values that are not already assigned to another group.
A Segment can contain up to 10 configured groups. DinMo also creates an Everyone else branch for profiles whose value does not belong to any configured group.
For example, you can create separate branches for different membership tiers. Profiles with any other value continue through Everyone else.
Wait for a condition with Pause Until
Pause Until keeps a profile at the current point until a condition is met.
Give the condition a clear name, then choose its source:
Profile fields
Define one or more conditions using fields from the Customer Hub profile model.
Event table
Select an event model, set the minimum number of occurrences, and optionally filter the relevant events.
For example, you can pause a profile until its lifecycle status changes or until a purchase event occurs.
Add a maximum duration
A maximum duration is optional. Enter a positive whole number in hours, days, or weeks, up to a total of 365 days.
Without a maximum duration, the step has one outgoing path. Profiles remain paused until the condition is met.
With a maximum duration, the step has a condition met path and a timed out path.
Without a maximum duration, profiles can remain in the step indefinitely. Add a maximum duration when the condition may never become true.
Conditions are checked according to the Journey processing schedule. A profile progresses the next time the Journey processes it after the condition is met or the maximum duration is reached.
Activate destinations
Activate sends Customer Hub profiles to one or more audience destinations when they reach the step. Only activation targets configured for audience synchronization are available.
Configure an Activate step
Add an Activate step.
Enter a step name. This name appears on the Journey canvas and in the run history.
Under Audience membership, choose how DinMo should manage profiles:
Sync with Journey membership adds profiles when they reach the step and removes them when their Journey instance exits or finishes.
Add only adds profiles when they reach the step. The Journey does not remove them from the destination audience.
Select an audience destination.
Configure its destination-specific settings and map fields from the Customer Hub profile model.
Select Save configuration.
Repeat these steps for every destination required in the same Activate step, then save the step.
Every selected destination must be configured before the Activate step can be saved. When an activation target already uses the Customer Hub profile model, DinMo can prefill its existing mapping; review the mapping before saving.
For example, you can add an Activate step after a Wait, Segment, or Pause Until step to send only the profiles that reach that point.
An Activate step placed directly after Start sends profiles as soon as they enter. DinMo displays a warning so you can confirm that the immediate activation is intentional.
The same activation target can be selected in several Activate steps, but DinMo flags this configuration for review because the same profile may be activated more than once.
End each path with Stop
Stop explicitly ends a path. A Stop step has no outgoing connection and a profile that reaches it has completed its current Journey occurrence.
Every path must end with Stop before the Journey can be published.
For example, add Stop after the last action in each Segment or Pause Until branch so that every possible outcome has a visible ending.
Build valid paths
DinMo supports flexible paths, including consecutive Segment or Wait steps, nested Random Split steps, and a Wait step after Pause Until.
Before publication, DinMo checks that:
every step except Start has a single parent;
every step is reachable and the graph contains no cycle;
branches cannot merge back into the same step;
every path must end with Stop;
Stop remains terminal;
an Activate step does not immediately follow another Activate step;
the Journey contains no more than 50 steps and 10 levels.
A Wait step may appear immediately before Stop. When Journey Repeat is disabled, DinMo displays a warning because this Wait only delays completion.
Use the publish checklist to distinguish blocking errors from warnings before making the Journey active.
Related pages
Last updated