Scenes can be used for a variety of custom experiences that you define. For example:
- Welcome messages — Communicate the value of your app and highlight key features.
- Push opt-in prompts — Explain the value of your notifications to drive opt-in rates.
- App reviews — Prompt users to rate your app after positive experiences.
- Registration/login — Drive registrations and logins to your loyalty program or account.
- NPS (Net Promoter Score) — Display an NPS survey to gauge how likely your users are to recommend your app.
- Customer service rating — Display a customer service satisfaction survey after they end a support chat.
- Purchase confirmation — Display a survey after they complete a purchase to get feedback on your checkout process.
- General feedback — Display a survey in response to a button click.
- Account closure — Display a survey at the end of an account closing asking why they closed their account.
Appearance and behavior
Scenes are cached on users’ devices upon receipt of a background push. When background push is disabled for your project, or for users opted out of background app refresh, our SDK downloads and refreshes Scenes during the next app open.
They appear regardless of a user’s opt-in/out status for notifications and remain on screen until the user interacts with them, either by swiping or tapping through all screens or dismissing the Scene.
For Scenes with multiple screens, dots appear at the bottom, indicating the number of screens. You can set colors for their active and inactive states, hide them, and disable the swipe requirement to require interacting with buttons and prevent swiping between screens.
Scenes can be customized for device Light and Dark modes by creating Color SetsA named pair of hexadecimal color values supporting device Light and Dark modes. Color sets can be selected for any color field in a scene and when configuring the default appearance of Surveys, Scenes, and In-app Automations. Dark mode is supported for Scenes only. and assigning them when configuring color fields for various design settings, like background, text, or the dismiss button.
Screens and design
All projects contain two preset view styles, Modal and Fullscreen, and you can create custom view styles.
A modal view is smaller than the full width of the screen, superimposed on the app with a translucent background, indicating that the interruption is temporary. It takes over the user’s screen, compelling the user to interact with it
Fullscreen Scenes have the same design as modal but use the entire screen. You can set fullscreen Scenes to extend to the full height and width of a device or display only within the area of your app’s interface that is not covered by physical or UI elements, such as a status bar or notch.
Each screen can contain these elements:
- List — A bulleted list where the bullet is an image you provide
- Question — Open text, single choice, or multiple choice
- Media — An image or video
- NPS — A survey based on the net promoter score metric, which measures how likely it is that your users would recommend your brand or product to a friend or colleague
- Button group — One to five buttons
For buttons and text links, in addition to an ActionA configurable behavior that occurs when a user interacts with your message, e.g., opening a web page. , you can determine how the Scene behaves when the button or link is tapped. Use cases for setting Scene behavior for buttons:
Give the option
Don't ask me again. How to set it up: For a Scene configured to repeat, label a button
Don't ask me againand set the Scene behavior to Dismiss and cancel repeat.
Close the Scene in the background while the system opt-in prompt is in the foreground. How to set it up: For a button configured with the action Subscription List Opt In/Out or Push Opt-in, set the Scene behavior to Dismiss.
Advance to the next screen after opting in, without requiring a swipe. How to set it up: For a button a button configured with the action Subscription List Opt In/Out or Push Opt-in, set the Scene behavior to Next screen.
For all configuration details and options, see Configure Scene content.
You can set appearance and behavior defaults for Scenes. In addition to setting default colors for the background, dismiss button, and indicators, you can name and define multiple view, text, and button styles that you can select when configuring individual Scenes. Projects contain preset styles that you can rename, customize, and remove, and you can add more. When configuring Scene content, you have the option to override the defaults.
A preview of your message updates as you design its content. You can use built-in tools to create a more accurate representation of how your content may appear to users.
See Preview tools in Configure Scene content.
Story modeiOS SDK 17+Android SDK 17+
The default behavior of a Scene requires the user to swipe between screens. Story mode enables automatic transitions to the next screen without requiring swiping.
When configuring Story mode, you set how long each screen is displayed (1-60 seconds) and determine what happens after the story ends:
- Loop — The Scene replays indefinitely.
- Display last screen — The last screen of the Scene continues to display.
- Dismiss — The Scene closes.
When viewing a story, a progress bar indicates the number of screens and their remaining duration. The user can:
- Tap the right side of a screen to go to the next screen and tap the left side to go to the previous screen
- Tap and hold anywhere on the screen to pause
- Swipe down or tap the Dismiss (X) button to close
The progress bar appears in the device preview after you enable Story mode. You can also customize its color.
Story mode does not support:
- Scrolling — Make sure to design screens for small device dimensions to eliminate the appearance of a non-functional scroll bar.
- Questions or NPS
In addition to configuring when the Scene will display and its appearance and content, you can also set optional features:
- Start and end dates
- Message priority
- Ignore channel message limits
- Campaign categories
- Override default missed behavior action
- Custom keys
When creating a Scene, you can start from scratch or select a template for your use case. Each template has various screens with content placeholders supporting the template purpose. The same design options are available if you choose to create a Scene from scratch.
Use cases and images for Scene templates:
|Onboard new users to your app
|Alert users that the latest version of your app is now available.
|Inform users that their subscription has ended or that it is time to upgrade.
|Educate users about specific features to encourage them to try them out.
|Net Promoter Score (NPS)
|A survey based on the net promoter score metric, which measures how likely it is that your users would recommend your brand or product to a friend or colleague. This can be used to measure their overall sentiment about your brand or product (known as relational NPS) or about a specific experience or transaction, such as booking a flight (known as transactional NPS). After selecting a template, you customize the questions and design. You also have the option to create a confirmation screen that appears when a user submits the survey.
|A general purpose survey with multiple question options to collect a wide range of user feedback. After selecting a template, you customize the questions and design. You also have the option to create a confirmation screen that appears when a user submits the survey.
Scene status is either Active, Expired, Canceled, or Pending. When you first create a Scene it is Active. It remains active until either:
It expires according to its end date.
You stop it. Stopped Scenes are considered canceled.
- Active Scenes can be edited or canceled 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.
A recently created or edited Scene has the status Pending for a few seconds until it completes processing and becomes Active.
See Change status.
Background push invokes any typical background actions your app takes when it is woken. For some apps, this behavior can be too much to handle. Because of this, background push is disabled by default for use with Scenes.
If you are confident with you app’s ability to handle a larger number of background push notifications, for best results, we highly recommend enabling background push for Scenes. Without the use of background push, your app will not receive necessary updates of Scenes until the next time the app is opened.
Here are some examples of what can happen if background push is not enabled:
New Scenes may not be available on the device before the user generates the event that triggers the Scene display.
Updates to or cancellations of Scenes may not get applied in time, so your app may display the wrong version of a Scene or display a Scene that should not have been displayed.
Please note that while background push is not guaranteed to solve all of the issues above, it does give the SDK the best opportunity to update the Scene list before the app is open, making it more likely that your user sees the correct Scene.
If your Scene contains an NPS survey, Airship automatically generates AttributesMetadata that you can use for audience segmentation. Attributes differ from tags in that when evaluating users with attributes, Airship uses operators, e.g., equals, less than/greater than, contains, before/after, to determine whether or not to target a user. Supported attribute types are TEXT, NUMBER, and DATE. based on the following data:
- NPS Score is the score submitted by the user: 0-10.
- NPS Category is one of three categories based on the NPS Score. Ratings 9 and 10 have category Promoter, 7 and 8 are Passive, and 6 or lower are Detractor.
See also: Segmenting your audience.
We provide aggregate information about responses to questions and NPS surveys in your Scenes. See Surveys in Engagement Reports.
Performance reports are available for individual Scenes in the same format as Message Reports. From Messages OverviewA view of all your project’s messages, with options for editing their settings, content, status, and more. , select the report icon () for a Scene to open its report.
The header displays the Scene name and creation date, time and time zone, as well as its status. Options in the header:
Stop () — Changes the status of an Active Scene to Canceled. This is effectively the same as specifying an end date, 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, Scene, or survey. This is effectively a shortcut to editing the Scene and either eliminating or specifying an end date. 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.
The Performance section of a Scene report displays:
Latest Message Activity — 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.
- Scene Displayed — The total number of times at least the first screen of the Scene was displayed.
- Scene 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.
- Scene Dismissed — The total number of times the Scene was dismissed before the last screen was displayed.
- 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 with action 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 with action Submit Responses.
- Total Push Opt-in — The total number of users that opted in from the system prompt or app settings after tapping a button with action Push Opt-in.
Ideally, Scene Displayed = Scene Completed + Scene Dismissed, however there may be discrepancies 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.
Engagement Over Time — A chart displaying 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.
The Scene Detail section of a Scene report displays the same information shown in the Review step of the Scene composer and counts for screen displays and dismissals. Select the arrows to page through the previews of each screen.
If you included questions or an NPS survey in your A/B test, responses are includes in the Surveys aggregate report. Select the link in Scene Detail to go to that report.
The Events section of a Scene report displays a list of events directly and indirectly attributed to the Scene. Select Download CSV to export the data.
The Events section is only displayed if you have Custom EventsEvents that indicate that a user performed a predefined action, such as adding an item to a shopping cart, viewing a screen, or clicking an Unsubscribe button. Custom events can trigger automation, including Sequences, Scenes, and Surveys. You can code them into your app or website, or send them to Airship from an external source using the custom event API. Custom events contain properties that you can use to personalize messages. enabled.
- 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 (listed on the bottom row).
Reported events are also accessible via Real-Time Data StreamingA service that delivers engagement events in real time via the Data Streaming API or an Airship partner integration. and Performance AnalyticsA customizable marketing intelligence tool that provides access to reports and graphs based on engagement data. . These events include:
- Scene displayed
- Scene completed
- Scene incomplete
- Button clicked (each button is a separate event)
If your Scene contains questions, these events are included:
- Survey displayed
- Survey submitted
- Survey not submitted
Message limits cap the number of messages you can send within a specified time frame, preventing you from over-messaging your users. They are set at the project level. The limit for Scenes, 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. , and 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. are combined. See Message Limits.
RequirementsiOS SDK 16.2+Android SDK 16.2+
Some individual features require later SDKs. They are noted with their descriptions in Configure Scene content.
Questions and NPS surveys in Scenes require analytics be enabled in the SDK. Analytics are enabled by default, and disabling them renders certain features, nonfunctional. See the Analytics and Reporting section of the SDK documentation for information about enabling analytics.