Flow Control

While designing the campaign you can use several triggers to control the flow of the journey.

Delays

With a Delay trigger you can add wait times, either for a fixed duration or based on an attribute, anywhere in the journey. You can also include engage time optimization or dayparting to control when a user can flow through the trigger.

To add a Delay trigger, click + and select Delay from the Flow Control options.

Split journey

With a Decision Split trigger, you can split a branch into 2 or more branches.

• When you add a decision trigger to your journey, the trigger splits the journey into two branches by default: Path 1 and Everything Else.
• You can add additional paths with corresponding criteria as required.
• A Decision Split trigger cannot be added as a sibling to other triggers. For example, if you have an email trigger, the Decision Split trigger cannot added as sibling trigger to the email trigger.
• Paths are evaluated from left to right.
  • Users who meet criteria for Path 1, will take that route.
  • Users who don't qualify for Path 1 but meet the criteria for Path 2 will take that route. 
  • Users who don't qualify for Path 1 or Path 2, but meet the criteria for Path 3 will take that route, and so on.
  • Users who don't match the criteria for any of the paths, will flow through the Everything Else path.
• You cannot specify any criteria for the Everything Else path because users who don't match the criteria for any of the other paths will flow through the Everything Else path.
• Similar to other triggers, you can rename the paths and the Everything Else trigger and add descriptions.
• If you delete a Decision Split trigger, all paths for that trigger are deleted. All triggers in the branched paths are also deleted.
• If you delete a particular branch, the entire branch, including all triggers in the branch, is deleted.

To split the journey, click + and select Decision Split from the Flow Control options. Click + to split into more branches.

Merge branches

Merging reduces the amount of time required to build your campaign journey by reducing duplication and hence also reduces human error.

• When a campaign is rerouted to a specific point in the journey, it does not re-evaluate the filters/conditions in the parent node. The campaign just assumes that all the criteria have been met and the journey continues from that point onward, evaluating all subsequent criteria moving forward.
• Maximum Iterations specifies the maximum number of times the platform can reroute a campaign for a customer. This ensures that the platform does not get into an endless loop between steps and proceeds with the next steps of the campaign for your customers.

To merge a journey, click + and select Merge Journey from the Flow Control options. Configure the Destination. You can loop back to the Start of the Journey or merge to a point after a particular trigger.

Exit the journey

You can add an Exit Journey trigger that moves a customer out of the campaign journey based on the conditions you specify. For example, for a re-engagement campaign, you can set an Exit trigger where a user exits the campaign if they visited your site and made a purchase.

To add an Exit Journey trigger, click + and select Exit Journey from the Flow Control options.