Jumping from one journey to another

The Jump action activity allows you to push individuals from one journey to another. This feature allows you to:

  • simplify the design of very complex journeys by splitting them into several ones
  • build journeys based on common and reusable journey patterns

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.

NOTE

Also refer to the Journey Orchestration tutorial video here

Lifecycle

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:

  1. Journey A receives an external event related to an individual.
  2. The individual reaches the Jump step.
  3. The individual is pushed to Journey B, and moves on to the next steps in Journey A, after the Jump step.

In journey B, the first event is triggered internally, via the Jump activity from journey A:

  1. Journey B received an internal event from Journey A.
  2. The individual starts flowing in Journey B.
NOTE

Journey B can also be triggered via an external event.

Best practices and limitations

Authoring

  • The Jump activity is only available in journeys that use a namespace.
  • You can only jump to a journey that uses the same namespace as the origin journey.
  • You cannot jump to a journey that starts with a Segment Qualification event or Read Segment.
  • You cannot have a Jump activity and a Segment Qualification event or Read Segment in the same journey.
  • You can include as many Jump activities as you need in a journey. After a Jump, you can add any activity needed.
  • You can have as many jump levels as needed. For example, Journey A jumps to journey B, which jumps to journey C, and so on.
  • The target journey can also include as many Jump activities as needed.
  • Loop patterns are not supported. There is no way to link two or more journeys together which would create an infinite loop. The Jump activity configuration screen prevents you from doing this.

Execution

  • When the Jump activity is executed, the latest version of the target journey is triggered.
  • As usual, a unique individual can only be present once in a same journey. As a result, if the individual pushed from the origin journey is already in the target journey, then the individual will not enter the target journey. No error will be reported on the Jump activity because this is a normal behavior.

Configuring the Jump activity

  1. Design your origin journey.

  2. At any step of the journey, add a Jump activity, from the ACTIONS category. Add a label and description.

  3. 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.

    NOTE

    You can click the Open target journey icon, on the right side, to open the target journey in a new tab.

  4. 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.

  5. 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.

  6. Add the next activities to finish your origin journey.

    NOTE

    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.

Troubleshooting

When the journey is published or in test mode, errors will happen if:

  • the target journey no longer exists
  • the target journey is draft, closed or stopped
  • if the first event of the target journey has changed and the mapping is broken

On this page