Journey Map

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

• JourneysA series of messages that is initiated by a trigger. Airship sends messages in the series based on your timing settings, and you can also set conditions that determine its continuation. Journeys can be connected to other journeys and to in-app experiences to create continuous user experiences.
• In-App AutomationsMessages that are cached on users’ devices and displayed when your users meet certain conditions within your app, such as viewing a particular screen or opening the app a certain number of times.
• SurveysQuestion-and-answer experiences used to collect and aggregate feedback or generate a net promoter score. They are cached on users’ devices and displayed when your users meet certain conditions within your app, such as viewing a particular screen or opening the app a certain number of times.
• ScenesMulti-screen experiences that are cached on users’ devices and displayed when your users meet certain conditions within your app, such as viewing a particular screen or opening the app a certain number of times.

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.

Sidebar

The sidebar summaries list:

• Name
• Last modified date, time, and time zone
• Trigger — Journeys only
• Number of messages — For in-app automation, surveys, and scenes the number will always be 1.
• Status (Active, Paused, or Draft) — Journeys only. This feature is in development for in-app automation, surveys, and scenes. See Messages OverviewA view of all your project’s messages, journeys, and A/B tests, with options for editing their settings, content, status, and more. for accurate status.

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:

• Name
• Status
  • Draft — The card is greyed-out, labeled Draft in grey, and does not display statistics.
  • Started — The card is not greyed-out, is labeled Active in green, and displays statistics.
  • Paused — The card is not greyed-out, is labeled Paused in orange, and displays statistics.
  • Completed — The card is not greyed-out, is labeled Completed in red, and displays statistics.
• Statistics
  • In Progress — The sum of Users eligible for message counts for all messages in the journey.
  • Conversions — The rate of conversion, calculated by the number of users who exited the journey by a conversion event divided by the total number of times the journey was triggered. Conversions are labeled Reactivations for journeys using the Inactivity trigger.
  • Conversion trend — For journeys with a control group, the difference between the BaselineThe benchmark conversion rate of a journey’s control group. It represents the conversion rate you would expect to see without messaging, and it is used to calculate the lift rate. and current conversion rates for the selected time frame. It appears in green for a positive trend and red for a negative trend. Click the trend to see the Lift RateThe percent increase or decrease in the active audience conversion rate against the baseline. , baseline, and the date the baseline was set. See: Journey Control Groups.

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:

• Name
• Status — This feature is in development. See Messages OverviewA view of all your project’s messages, journeys, and A/B tests, with options for editing their settings, content, status, and more. for accurate status.
• Statistics
  • Impressions — The total number of views by your audience.
  • Dismissals — The total number of times your audience closed the message, survey, or scene without engagement, e.g., following a link, clicking a button.

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.

Card actions

Click a card in the map to see available actions:

• Manage — Opens the Journey ManagerA preview of the messages in a journey, with options for editing and testing, and for running experiments. , or opens the composer to the last step edited for an in-app automation, survey, or scene.
• Performance — Opens the individual (not aggregate) report. See: journey Performance reportA report that compares audience behavior to a journey’s goal. It displays performance metrics and a link to the message report for each message in the journey. , in-app automation message report, About Surveys: Reporting, About Scenes: Reporting. Available only if started/active.
• Focus — Reloads the map with the focused card at center.
• Start — Makes a draft active. This is the same as clicking Start journey or clicking Finish in the In-App Automation, Survey, and Scene composers. Available only if it can be started. Otherwise, click Manage and complete the composer steps.
• Publish changes — Journeys only:
  • Started, with unpublished changes — Applies the changes.
  • Paused, with unpublished changes — Applies the changes and makes the journey active. This is the same as clicking Start journey from the Journey ManagerA preview of the messages in a journey, with options for editing and testing, and for running experiments. .

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

• In-app automation, survey, scene — Same as Start described in card actions above.
• Journey — Draft — Same as Start described above.
• Journey — Started, with unpublished changes — Same as Publish changes described above.
• Journey — Paused, with or without unpublished changes — Applies the changes, if any, and makes the journey active. This is the same as clicking Start journey from the Journey ManagerA preview of the messages in a journey, with options for editing and testing, and for running experiments. .

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.

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.