The Jump action activity allows you to push individuals from one journey to another. This feature allows you to:
In the origin journey, simply add a Jump activity and select a target journey. When the individual enters the Jump step, an internal event is sent to the first event of the target journey. If the Jump action is successful, the individual continues to progress in the journey. The behavior is similar to other actions.
In the target journey, the first event triggered internally by the Jump activity will make the individual flow in the journey.
Also refer to the Journey Orchestration tutorial video here
Let’s say you have added a Jump activity in a journey A to a journey B. Journey A is the origin journey and journey B, the target journey.
Here are the different steps of the execution process:
Journey A is triggered from an external event:
In journey B, the first event is triggered internally, via the Jump activity from journey A:
Journey B can also be triggered via an external event.
Design your origin journey.
At any step of the journey, add a Jump activity, from the ACTIONS category. Add a label and description.
Click inside the Target journey field.
The list displays all journey versions that are draft, live or in test mode. Journeys that use a different namespace or that start with a Segment Qualification event are not available. Target journeys that would create a loop pattern are also filtered out.
You can click the Open target journey icon, on the right side, to open the target journey in a new tab.
Select the target journey that you want to jump to.
The First event field is prefilled with the name of the target journey’s first event. If your target journey includes multiple events, the Jump is only allowed on the first event.
The Action parameters section displays all the fields of the target event. In the same way as for other types of actions, map each field with fields from the origin event or data source. This information will be passed to the target journey at runtime.
Add the next activities to finish your origin journey.
The individual’s identity is automatically mapped. This information is not visible in the interface.
Your Jump activity is configured. As soon as your journey is live or in test mode, individuals reaching the Jump step will be pushed from to the target journey.
When a Jump activity is configured in a journey, a Jump entry icon is automatically added at the beginning of the target journey. This helps you identify that the journey can be triggered externally but also internally from a Jump activity.
When the journey is published or in test mode, errors will happen if: