# Scene reports View aggregate survey reports and individual Scene performance metrics, including engagement statistics, user paths, screen interactions, and custom events. ## Aggregate reports For aggregate information about responses to questions and NPS surveys in your Scenes, see [Surveys](https://www.airship.com/docs/guides/reports/engagement/#surveys) in *Engagement Reports*. ## Individual Scene reports To view Scene-level reports, go to **Messages**, then **[Messages Overview](https://www.airship.com/docs/reference/glossary/#messages_overview)**, and select the report icon ( ) for a Scene. The report is in the same format as [Message Reports](https://www.airship.com/docs/guides/reports/message/). The header displays the Scene name and creation date, time and time zone, as well as its status. These options are available in the header: * Stop ( ) — Changes the status of an Active Scene to Canceled. This is effectively the same as [specifying an end date](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/optional-features/#specify-start-and-end-dates), immediately applying an end date of "now." Active messages can be canceled at any time. * Play ( ) — Changes the status of a Canceled or Expired Scene to Active. See [Restart an In-App Automation or Scene](https://www.airship.com/docs/guides/messaging/manage/change-status/#restart). This is effectively a shortcut to editing the Scene and either eliminating or [specifying an end date](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/optional-features/#specify-start-and-end-dates). Expired Scenes can be restarted within a grace period of 14 days. After 14 days they can only be duplicated. * Edit ( ) — Opens the Scene for editing. Availability depends on its status. Active Scenes can be edited at any time. An Expired or Canceled Scene can be edited and its end date extended, making it active again, within a grace period of 14 days. After 14 days they can only be duplicated. * Duplicate ( ) — Creates a copy of the Scene and opens it for editing. You must complete the composer steps in order to save the new Scene. ### Performance The Performance section of a Scene report displays the following: * **Latest Message Activity** — This lists the username, date, time, and activity associated with the most recent change to the Scene. Last Message Activity 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. * **Engagement Over Time** — This chart displays daily Completed, Dismissed, and Push Opt-in counts over the last 7 days. Hover over a date to see counts per day. You can select another time frame, and the chart will reload with the data for that period. * **User Paths** — For Scenes with branching, this flow chart displays each screen and its name, Impressions count, and Dismissed counts. A flow indicator shows the path taken between screens and the percentage of users that followed the path. Click and drag to move the chart, select the plus ( ) and minus icons ( ) to zoom in and out, or select the refresh icon to restore the initial view. * **Statistics:** | Statistic | Description | | --- | --- | | **Survey Displayed** | For Scenes with questions or NPS, the total number of times the first screen with questions/NPS was displayed. | | **Survey Submitted** | For Scenes with questions or NPS, the total number of times users clicked the button or image with action [Submit Responses](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/button-actions/#submit-responses) and the rate of submission. | | **Survey Not Submitted** | For Scenes with questions or NPS, the total number of times users dismissed the Scene without tapping the button or image with action [Submit Responses](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/button-actions/#submit-responses). | | **Total Completed** | The total number of times all screens in a Scene were displayed and the rate of completion. This only appears for Scenes with more than one screen. | | **Total Dismissed** | The total number of times the Scene was dismissed before the last screen was displayed. This count is not included in reporting for Scenes with a single screen. | | **Total Impressions** | The total number of times the Scene was triggered and subsequently displayed on a device. This metric increments for repeat displays of the same Scene. See also [View impressions usage](https://www.airship.com/docs/guides/getting-started/admin/usage-payment/#view-impressions-usage) in our _View usage and manage payment_ guide. | | **Total Push Opt-ins** | The total number of users that opted in from the system prompt or app settings after tapping a button or image with action [Push Opt-in](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/button-actions/#push-opt-in). | | **Unique Device Impressions** | The total number of unique devices where the Scene was triggered and subsequently displayed. This metric does not increment for repeat displays of the same Scene. | > **Note:** Ideally, Total Impressions = Total Completed + Total Dismissed, however discrepancies can occur due to: > > * **Users currently viewing a Scene** — Users triggered the Scene but have not yet dismissed or completed it. > * **Users closed the app, or users used the Back button on Android** — These behaviors are not reported by the SDK, so the related events are not tracked or counted. ### 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](https://www.airship.com/docs/guides/experimentation/a-b-tests/scenes/), you will see performance metrics for each variant. For more information, see [Selecting the winning variant](https://www.airship.com/docs/guides/experimentation/a-b-tests/scenes/#selecting-the-winning-variant) in *Scene A/B tests*. If you included questions or an NPS survey in your A/B test, responses are included in the [Surveys](https://www.airship.com/docs/guides/reports/engagement/#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 Events](https://www.airship.com/docs/reference/glossary/#custom_event) 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, or screen configured with the action [Emit a Custom Event](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/button-actions/#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. > **Note:** As of October 7, 2025, button tap events are listed per screen in the Interactions table in [Scene detail](#scene-detail). Before that date, events were listed in the Events table in the format `button-tap-action--