- A journey’s Performance report is available after you start the journey. You will not see links to the reports until then.
- Engagement data is sent to Airship as soon as it becomes available. Often data is delayed because of connectivity issues with a user’s carrier, wifi, power, etc. You should wait at least 12 to 24 hours before acting on this data to allow for potential lags.
Go to Journeys or Messages » Messages Overview and click for a journey.
The screen has the same layout as the Journey ManagerA preview of the messages in a journey, with options for editing and testing, and for running experiments. , and the message previews show the content as it was when the journey was first started. The report contains these main elements:
(Optional) Select a time frame to update the viewable data.
Select Active audience / Control group to change the viewable data. This option only appears if you set a control group for the journey.
You can access Performance reports from additional locations:
- From the Journey ManagerA preview of the messages in a journey, with options for editing and testing, and for running experiments. , click Performance.
- From a Journey MapShows the relationships between journeys. , select a journey in the map, then click Performance.
The following data are included in the Performance report:
- The trigger used to initiate the journey (tag change, custom event, inactivity, etc.) and the total number of times it was triggered. The trigger and count are located in the banner at the top of the report.
Users may trigger the journey more than once, depending on the journey’s rule limitLimits that cap the number of times any member of your audience can trigger a journey, helping prevent you from over-notifying your audience, e.g., a maximum of 1 per day. Rule limits are set per journey and apply at the named user level. , so this count may be higher than the number of individual users who triggered the journey.
- Conversions / Reactivations
- The number of users who exited the journey by a Conversion event. If your journey does not have a Conversion outcome, this count will not appear. For journeys using the Inactivity trigger, Conversions is instead labeled Reactivations. The conversion/reactivation count is located above Filtered for each message.
- Filters and counts
- The reasons why users exited the journey, or fell out of the funnel. Filters and their counts are listed under Filtered, to the left of each message in the journey. Filters include:
- Conditions — The number of users who exited due to not meeting the message’s tag conditions, e.g., message 2 was only delivered to users with tag
- Rule limits — The number of users who exited due to exceeding a journey rule limitLimits that cap the number of times any member of your audience can trigger a journey, helping prevent you from over-notifying your audience, e.g., a maximum of 1 per day. Rule limits are set per journey and apply at the named user level. or project Journeys and Automation message limitLimits that cap the number of messages you can send within a specified time frame, preventing you from over-messaging your users. Message limits are set at the project level. .
- Rescheduled — The number of users awaiting the scheduled first message in a journey who then performed the trigger event again, resulting in rescheduling the message delivery.
- Other — The number of users who exited due to other reasons.
- Users eligible for message
- The total number of users that have met the criteria to receive the message.
- Direct engagements
- The total number of direct app opens and clicks on web notifications, and the percentage of direct engagements, calculated as the percentage of total number of sends / total number of direct engagements.