About Journeys

Go to Journeys in the dashboard to:

• Create and edit the individual components of a journey — a SequenceA 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. Sequences can be connected to each other and to other messaging components to create continuous user experiences in a Journey. , SurveyQuestion-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. , SceneMulti-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. , or In-App AutomationMessages 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. .
• Connect components together to form a journey.
• View performance information for an individual component and a mapped view of its triggers, events, outcomes, and upstream and downstream connections.

The journey map

Search for a sequence, survey, scene, or in-app automation, or click Show list   and select from the list.

The selected item is represented as a card, along with a map of its triggers, events, outcomes, and upstream and downstream connections. The map displays data for Last 7 Days by default. You can select a time frame, and map will reload with the data for that period.

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

Sequence data

Data displayed in sequence cards:

• 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 sequence.
  • Conversions — The rate of conversion, calculated by the number of users who exited the sequence by a conversion event divided by the total number of times the sequence was triggered. Conversions are labeled Reactivations for sequences using the Inactivity trigger.
  • Conversion trend — For sequences with a control group, the difference between the BaselineThe benchmark conversion rate of a sequence’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: Sequence Control Groups.

The trigger for a sequence appears to its left. Date Attribute, Recurring Schedule, and Specific Date and Time triggers will not appear if the specified timing is outside of the selected time frame in the map. The outcomes for a sequence appear to its right.

In-app automation, survey, and scene data

Data displayed in in-app automation, survey, and scene cards:

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

The trigger appears to its left, and button click counts appear to its 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.

Actions

Click a card in the map to see available actions:

• Edit — Opens the Sequence ManagerA preview of the messages in a sequence, 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: sequence Performance reportA report that compares audience behavior to a sequence’s goal. It displays performance metrics and a link to the message report for each message in the sequence. , in-app automation message report, About Surveys: Reporting, About Scenes: Reporting. Available only if started/active.
• Start — Makes a draft active. This is the same as clicking   Start or clicking Finish in the In-App Automation, Survey, and Scene composers. Available only if it can be started. Otherwise, click Edit and complete the composer steps.
• Publish changes — Sequences only:
  • Started, with unpublished changes — Applies the changes.
  • Paused, with unpublished changes — Applies the changes and makes the sequence active. This is the same as clicking   Start from the Sequence ManagerA preview of the messages in a sequence, 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.
• Sequence — Draft — Same as Start described above.
• Sequence — Started, with unpublished changes — Same as Publish changes described above.
• Sequence — Paused, with or without unpublished changes — Applies the changes, if any, and makes the sequence active. This is the same as clicking   Start from the Sequence ManagerA preview of the messages in a sequence, 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 sequence.

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.

Sidebar list

Click Show list   and   Hide list to expand and collapse the list of all journey components in your project and a summary for each.

Data displayed in summaries:

• Name
• Last modified date, time, and time zone
• Trigger — Sequences only
• Number of messages — For in-app automation, surveys, and scenes, the number will always be 1.
• Status (Active, Paused, or Draft) — Sequences only. This feature is in development for in-app automation, surveys, and scenes. See Messages OverviewA view of all your project’s messages, 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 sequences, you can sort by Performance (sequence conversion rate) or In Progress Count (the number of users currently in the sequence). Click Last Modified   and make your selection.

Sequence sorting behavior:

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