Jump from one journey to another jump
The Jump action activity enables you to transfer individuals from one journey to another. This feature helps you:
- Simplify complex journey designs by dividing them into smaller, manageable parts.
- Create journeys using common and reusable journey patterns.
Why use Jump activities?
Designing customer journeys can become complicated due to multiple paths and conditions. The Jump activity simplifies journey design by allowing you to break larger journeys into smaller ones or reuse standard journey patterns. This modular approach reduces redundancy and enhances maintainability across workflows.
To use the Jump activity, add it to the origin journey and select a target journey. When individuals reach the Jump step, an internal event triggers the first event of the target journey. If the action succeeds, individuals continue progressing through the journey. This behavior aligns with other actions.
In the target journey, individuals begin progressing through the journey with the first event triggered internally by the Jump activity.
Lifecycle jump-lifecycle
To understand how the Jump activity works, consider the following example:
Suppose Journey A contains a Jump activity pointing to Journey B. Journey A is the origin journey, and Journey B is the target journey. The execution process includes the following steps:
Journey A is triggered by an external event:
- Journey A receives an external event related to an individual.
- The individual reaches the Jump step.
- The individual is transferred to Journey B and continues progressing through Journey A after the Jump step.
In Journey B, the first event is triggered internally via the Jump activity from Journey A:
- Journey B receives an internal event from Journey A.
- The individual begins progressing through Journey B.
This mechanism ensures seamless transitions between journeys and guarantees proper routing based on your design.
Best practices and limitations jump-limitations
Authoring jump-limitations-authoring
- The Jump activity is only available in journeys that use a namespace.
- The target journey must use the same namespace as the origin journey.
- You cannot jump to a journey that starts with an Audience Qualification event or Read Audience.
- You cannot include both a Jump activity and an Audience Qualification event or Read Audience in the same journey.
- You can add multiple Jump activities in a single journey. After a Jump, you can include additional activities as needed.
- You can implement multiple jump levels, such as Journey A jumping to Journey B, which then jumps to Journey C, and so on.
- Target journeys can include multiple Jump activities.
- Loop patterns are not supported. Journeys cannot link together to create infinite loops. The Jump activity configuration screen prevents this scenario.
Why are these limitations important?
These restrictions ensure logical flow and maintain integrity in journey designs, preventing issues such as infinite loops or namespace mismatches. For example, avoiding loop patterns improves performance and prevents individuals from being stuck in repetitive cycles.
Execution jump-limitations-exec
- When the Jump activity is executed, the latest version of the target journey is triggered.
- A unique individual can only exist once in the same journey. If an individual transferred from the origin journey is already in the target journey, they will not enter the target journey again. No error is reported, as this behavior is expected.
Configuring the Jump activity jump-configure
Step-by-step example:
-
Design the origin journey.
-
At any step in the journey, add a Jump activity from the ACTIONS category. Provide 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 begin with an Audience Qualification event are excluded. Target journeys that would create a loop pattern are also filtered out.
note note NOTE 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 to jump to.
The First event field is automatically populated with the name of the target journey鈥檚 first event. If the target journey includes multiple events, the Jump activity can only reference the first event.
-
In the Action parameters section, map each field of the target event to fields from the origin event or data source. This data is passed to the target journey during runtime.
-
Add subsequent activities to complete your origin journey.
note note NOTE The individual鈥檚 identity is automatically mapped. This mapping is not visible in the interface.
Your Jump activity is now configured. Once the journey is live or in test mode, individuals reaching the Jump step will be transferred to the target journey.
When a Jump activity is configured, a Jump entry icon automatically appears at the start of the target journey. This icon identifies that the journey can be triggered externally or internally via a Jump activity.
Troubleshooting jump-troubleshoot
Errors may occur if:
- The target journey no longer exists.
- The target journey is draft, closed, or stopped.
- The first event of the target journey has changed, breaking the mapping.
These issues can disrupt the individual鈥檚 progression. Regularly review journey configurations to minimize potential errors.
