Creating a journey concept_gq5_sqt_52b
This step is performed by the business user. This is where you create your journeys. Combine the different event, orchestration and action activities to build your multi-step cross-channel scenarios.
The journey interface allows you to easily drag and drop activities from the palette into the canvas. You can also double-click on an activity to add it in the canvas at the next step available. Each activity has a specific role and place in the process. The activities are sequenced. When an activity is finished, the flow continues and processes the next activity, and so on.
Only one namespace is allowed per journey. When you drop the first event, events with different namespaces will be grayed out. If the first event doesn’t have a namespace, then all events with a namespace will be grayed out. See this page. Also, ÃÛ¶¹ÊÓƵ Experience Platform field groups are grayed out if the journey has events without a namespace. And finally, if you use several events in the same journey, they need to use the same namespace.
When starting a new journey, elements that cannot be dropped in the canvas as the first step are hidden. This concerns all actions, the condition activity, the wait and the reaction.
Quick start creating_journey
Here are the main steps to create and publish a journey.
-
In the top menu, click the Home tab.
The list of journeys is displayed. Refer to this page for more information on the interface.
-
Click Create to create a new journey.
-
Edit the journey’s properties in the configuration pane displayed on the right side. See this page.
-
Start by drag and dropping an event activity from the palette into the canvas. You can also double-click on an activity to add it to the canvas.
-
Drag and drop your other activities and configure them. Refer to the pages Event activities, About orchestration activities and About action activities.
-
Your journey is automatically saved. Test your journey and publish it. See testing the journey and Publishing the journey.
Ending a journey ending_a_journey
A journey can end for an individual because of two reasons:
- The person arrives at the last activity of a path. This last activity can be an end activity or another activity. There is no obligation to end a path with an end activity. See this page.
- The person arrives at a condition activity (or a wait activity with a condition) and does not match any of the conditions.
The person can then re-enter the journey if re-entrance is allowed. See this page.
A journey can close because of the following reasons:
- The journey is closed manually via the Close to new entrances button.
- The journey’s end date is reached.
When a journey is closed (for any of the reasons above), it will have the status Closed. The journey will stop letting new individuals enter the journey. Persons already in the journey will finish the journey normally. After the default global timeout of 30 days, the journey will switch to the Finished status. See this section.
In case you need to stop the progress of all individuals in the journey, you can stop it. Stopping the journey will timeout all individuals in the journey.
To learn how to close or stop a journey manually, refer to this section.