Scene reports

To view a Scene report, go to Messages, then Messages Overview, and select the report icon () for a Scene. The report is in the same format as Message Reports. The header displays the Scene name, when it was created, and its status.

Performance

Under Performance, Latest Message Activity states the username, date, time, and activity associated with the most recent change to the Scene. The data is available for 90 days after Scene creation. For Scenes with more than one activity, select Show all to open a modal window that displays all activity.

Individual subsections provide information about Goal attribution, statistics, engagement data, and user paths for the Scene.

Goal Attribution

Under Goal Attribution, search for a GoalSelected events that generate a set of performance reports. Goal event attribution appears in message reports. You can also use Goals for measurement in Holdout Experiments and feature flag A/B tests. to see if its events are attributed to the Scene. Goal events that occur after a Scene impression, within a specified expiration window, are counted as conversions.

For example, if the expiration window is set to 24 hours and a user sees a Scene on Monday at 10 AM, any Goal events that occur by Tuesday at 10 AM are attributed to that Scene impression. Shorter windows capture immediate conversions, and longer windows capture delayed conversions.

The report displays the conversion rate, the number of devices converted, and conversions over time. By default, it groups data by channelA device or address registered with Airship to receive messages, such as a mobile app, web browser, email address, or SMS number. It stores opt-in status, device-specific information, and metadata used for targeting. Each channel has a unique channel ID. ID over the last seven days, with an expiration window of two days. For expired or canceled Scenes, the default time range spans from Scene creation to Scene end.

Customize the report using these controls:

• Channel ID / Named User — Toggle to display data at either the device or user level. The Devices Converted metric label changes to Users Converted when Named User is selected.
• Time Range — Set the reporting period.
• Event Expiration — Set the maximum time after a Scene impression during which a Goal event counts as a conversion. Enter a number of minutes, hours, or days, up to 30 days.

Statistics

Individual cards display the following engagement metrics:

In an ideal case, Total Impressions equals Total Completed plus Total Dismissed. Discrepancies can occur in these situations:

• A user triggered the Scene but has not yet dismissed or completed it.
• A user closed the app or used the Back button on Android. These behaviors are not reported by the SDK, so the related events are not tracked or counted.

Additional statistics appear for Scenes that contain the Question or NPS content elements:

Engagement Over Time

The Engagement Over Time chart displays daily Completed, Dismissed, and Push Opt-in counts over the last seven days. Hover over a date to see counts per day. Select another time frame, and the chart will reload with the data for that period.

User Paths

For content with branching, the User Paths flow chart displays each screen and its name, plus the number of impressions and dismissals. A flow indicator shows the path taken between screens and the percentage of users that followed the path.

Scene detail

The Scene Detail section of a Scene report displays the same information shown in the Review step of the Scene composer, plus:

• Screen impressions — This is the total number of times the screen was displayed
• Interactions — The Interactions table lists click/tap counts for each screen.
• Screen dismissals — For Scenes with multiple screens, view a count of the times a screen was dismissed. Select the arrows to page through the previews of each screen. The counts update for the currently previewed screen.

If you are currently running an A/B test, you will see performance metrics for each variant. For more information, see Selecting the winning variant in Scene A/B tests.

If you included questions or an NPS survey in your content, responses are included in the Surveys aggregate report. Select the link in Scene Detail to go to that report.

Events

The Events section of a Scene report displays a list of events directly and indirectly attributed to the Scene. The section is only displayed if you have custom eventsAn event you define to track an action in your app, on your website, or in an external system. Examples are a sign-up, a video watch, or a wish list addition. enabled. Select Download CSV to export the data.

The following data appears in the Events table:

• Event Name — Human-readable name assigned to a particular custom event
• Notification Attribution — Displays whether your event was directly or indirectly attributed to the Scene
• Count — The number of instances of this event
• Value — The value (monetary or otherwise) generated by the event
• Average Value — Value divided by Count
• % of Total Count — Count divided by the Total Count, which is listed on the bottom row

If the Scene has a button, image, text link, or screen configured with the action Emit a custom event, Notification Attribution for the event works as follows:

• Direct — A user opened the app by tapping a push and emitted the custom event by tapping a button/image/screen in the Scene.
• Indirect — A user opened the app sometime after a push was sent and emitted the custom event by tapping on a button/image/screen in the Scene.
• Unattributed — No push was sent, and a user emitted the custom event by tapping a button/image/screen in the Scene.

The following events are accessible via Real-Time Data StreamingA service that delivers user-level events in real time to your backend or third-party systems using the Data Streaming API. and Performance AnalyticsA customizable marketing intelligence tool that provides access to reports and graphs based on engagement data.:

• Scene displayed
• Scene completed
• Scene incomplete

If your Scene contains questions and/or the Email Input element, these events are also included:

• Survey displayed
• Survey submitted
• Survey not submitted
• In-app form result (for Email submissions only)