Journey Map

The journey map is a visualization of journeys and in-app experiences that can be connected to create a continuous user experience. You can also create and edit from the map.

Go to Journeys. The map includes all of the following in your project:

When you select from the sidebar (or search and select), the map updates to show its components represented as cards, along with related events, outcomes, and upstream and downstream connections for your selection.

This is the focused view, which hides the sidebar and exposes the option to change the time period that applies to the data displayed in the cards.

Click   in the search bar to restore the map to its initial state.

The sidebar summaries list:


The default sort order is Last Modified, ascending. Click   /   to toggle ascending/descending.

For journeys, you can sort by Performance (journey conversion rate) or In Progress Count (the number of users currently in the journey). Click Last Modified   and make your selection.

Journey sorting behavior:

  • Draft journeys and journeys with no sent messages are ranked below journeys that sent messages but have no successful exits.
  • In-app automations, surveys, and scenes are ranked after all journeys and are unsorted.
  • If you reverse the sort order to descending, all in-app automations, surveys, and scenes are listed before journeys.

Click   Hide list and Show list   to collapse and expand the sidebar.

Map cards

Map cards display data for Last 7 Days by default. You can select a time frame, and each card will reload with the data for that period.

Journey cards

Journey cards display:

Its trigger card is on its left. For the Manual Entry trigger, the selected segment name also appears. Its outcomes appear to the right.

In-app automation, survey, and scene cards

In-app automation, survey, and scene cards display:

Its trigger card is on its left, and button click counts appear to the right.

Button click count is the total number of button clicks for the message, survey, or scene. Click the count for more information:

  • Count per button — In-app automation only. Surveys and scenes display count 0.
  • Button location — Scenes only. Hover over a button label to see location in format [screen number/total number of screens, e.g., screen 3/5.

Click   to return to the total count.

 Note

Impressions and dismissals include multiple views/dismissals by a single user. Button clicks include all buttons in a message, survey, or scene, and multiple clicks by a single user.

Card actions

Click a card in the map to see available actions:


You can also select multiple cards in the map and perform the following actions for all selected cards at once:

Hold down Shift on your keyboard and click to select cards, then click Publish all changes, if available. Click   to zoom out if you cannot see all connected elements in your journey.

If none of the selections are valid (have unpublished changes or can be started), Publish all changes does not appear. If any of the selections are invalid (do not have unpublished changes or cannot be started), Publish all changes appears but is disabled.

Quick drafts

You can create a draft by providing only a name or by selecting a Journey TemplatePrefilled journeys you can use as starting points for common messaging scenarios. They are fully editable, and an onscreen tour leads you through the editing process. . After creating the draft, the map opens with the draft in focus.

For an in-app automation, survey, or scene:

  1. Click   in the map.
  2. Select In-App Experience from the sidebar.
  3. Click In-App Automation, Survey, or Scene.
  4. Enter a name.
  5. Click Continue.

For a journey:

  1. Click   in the map.
  2. Click Start from scratch.
  3. Enter a name.
  4. Click Continue.

For a journey template:

  1. Click   in the map.
  2. Click a template type.
 Tip

  is only available in the map when you first load the page. If you already made a selection from the sidebar or map, click   in the search bar to restore the map to its initial state. You can also access the same menu by clicking   in the header and selecting Journey.

In-app automation, survey, or scene as a journey trigger

You can route users to a journey when an in-app automation, survey, or scene is displayed on a device or when they click a button in the message/survey/scene. These options appear to the right of their map cards.

For a journey, triggering when a button is clicked is equivalent to using the Custom Event TriggerAn event that initiates an automation, journey, scene, or survey. and specifying the button click event from an in-app automation, survey, or scene.

To use these options:

  1. Click When the in-app experience is displayed…, or click Button Clicks and select a button.

  2. Set up the journey:

    • Search — Enter the journey name in the search box and select from the results, then click Save to confirm overwriting the existing trigger configuration for the journey.
    • Template — Click a template type.
    • Start from scratch — Enter a name for the journey, then click Continue.

    Creating a journey from scratch or selecting a template is the same functionality as creating a quick draft.

The map will now show the journey, with either Display or the button label for their connection.

  • If you delete a button that was used to trigger a journey, the map shows In-app event for the connection, with a warning that the button click trigger was deleted from message.
  • If you archive an in-app automation that triggers a journey, the card for the journey shows a warning that its trigger is missing.