Scene behavior is not available when the action is Next, Previous, or No Action. The actions Dismiss Message, Preference Center, and Deep Link have Scene behavior options **Dismiss** and **Dismiss and cancel Repeat** only. | | **Action: Reporting label** | Optional. A label to differentiate clicks/taps for the button in reporting.
By default, clicks/taps on elements with a configured action are reported using the In-app button tap event in the format button-tap-<button_action>--<button label>, where <button label> is the visible text on the element. When you enter your own reporting label, it replaces that text in the event name.
For example, if you enter Cat socks55 for the Submit Responses action, the event in reporting is button-tap-submit_feedback--Cat socks55.
Reporting labels support [Handlebars](https://www.airship.com/docs/reference/glossary/#handlebars).
| {class="table-col-1-20"} For the Button Group element, set the **Layout** if there are two buttons total. This determines if buttons appear separate, joined, or stacked. Three or more buttons are automatically stacked. In the sidebar, first select a [button style configured in your brand guidelines](https://www.airship.com/docs/guides/messaging/features/brand-guidelines/#text-button-and-input-styles), and then configure the design properties. ## Container Create a Container for other content elements. By default, screen elements are stacked vertically, and you can drag them into your preferred order. When you place elements in a Container, you can arrange them vertically or horizontally. Containers also support nesting, so you can do things like place images side by side. Immediately after selecting **Container**, select an element to add to that container. Use the breadcrumbs above the content elements to navigate between nested containers and back to the root screen. To fix a container at the bottom of a screen, see [Add content elements](https://www.airship.com/docs/guides/messaging/editors/scenes/screens/#add-content-elements). Containers do not support [NPS](#nps). In the sidebar, configure **Background color** and **Background media** using the [same steps as the screen background](https://www.airship.com/docs/guides/messaging/editors/scenes/screens/#set-background-color-and-media). ## Custom View Embed a [Custom View](https://www.airship.com/docs/reference/glossary/#custom_view) into a screen. Since the actual content of a native view is unknown by the device preview, the preview displays a placeholder. Set for the Custom View element: | Field or setting | Description | | --- | --- | | **Name** | The view name as registered in your mobile app or website code. | | **Content description** | Optional. Text to be announced by assistive technology such as screen readers. | | **Properties** | Optional. Key-value pairs to pass to the device for reference by your app's code. Property values support [Handlebars](https://www.airship.com/docs/reference/glossary/#handlebars). | {class="table-col-1-20"} ## Email **Email collection:** [iOS SDK 18.13+](/docs/docs/developer/sdk-integration/apple/ios-changelog/#18.13.0) [Android SDK 18.5+](/docs/docs/developer/sdk-integration/android/changelog/#18.5.0)Selecting text requires: [iOS SDK 19.8+](/docs/docs/developer/sdk-integration/apple/ios-changelog/#19.8.0) [Android SDK 19.10+](/docs/docs/developer/sdk-integration/android/changelog/#19.10.0) | | **Reporting label** | Required. This text appears as the Survey Question for question type `email` in [Performance Analytics](https://www.airship.com/docs/reference/glossary/#pa). | | **Submission type** | Required. Determines whether the email address will be only collected as data or also registered as a channel and opted in to transactional messaging.
For channel registration, you can also opt users in to commercial messaging. Enable **Double opt-in** to trigger an [Automation](https://www.airship.com/docs/reference/glossary/#automation) or [Sequence](https://www.airship.com/docs/reference/glossary/#sequence) using the [Double Opt-In trigger](https://www.airship.com/docs/guides/messaging/messages/sequences/triggers/#double-opt-in). Adding event property key-value pairs for double opt-in is optional but recommended to trigger a specific Automation or Sequence. | | **Required** | Optional. Makes entering an email address a requirement for making the Submit Responses button or image active. Check the box to enable. | {class="table-col-1-20"} In the sidebar, first select an [input style configured in your brand guidelines](https://www.airship.com/docs/guides/messaging/features/brand-guidelines/#text-button-and-input-styles), and then configure the design properties. ## List {#list-content} Add a bulleted list where the bullet is an image you provide. After configuring the first list item, select **Add another** for more. Set for each list item: | Field or setting | Description | | --- | --- | | **Media** | Required. The URL of an image to use as the bullet. URLs must be HTTPS and accessible by your mobile audience.
If your Airship plan includes CDN support, you can also upload media or select from previous uploads in your project’s media library. See Insert media in message content in Media library.
| | **Text** | Required. The text that follows the bullet. | | **Alternative text** | Optional. Text to be announced by assistive technology such as screen readers. Alternative text, also known as alt text, is a textual description of an image or video that is used when a person cannot see or access the visual image to help them understand its meaning. | {class="table-col-1-20"} In the sidebar, first select a [text style configured in your brand guidelines](https://www.airship.com/docs/guides/messaging/features/brand-guidelines/#text-button-and-input-styles), and then configure the design properties. ## Media Add an image or video. 10 media elements maximum per screen. Set for the Media element: | Field or setting | Description | | --- | --- | | **URL or Upload** | Required. The URL of the image or video to display. URLs must be HTTPS and accessible by your mobile audience.If your Airship plan includes CDN support, you can also upload media or select from previous uploads in your project’s media library. See Insert media in message content in Media library.
Video displays in landscape mode and does not start until a user selects the Play button. (Orientation and behavior are different for [background video](https://www.airship.com/docs/guides/messaging/editors/scenes/screens/#set-background-color-and-media).) Video is not supported in [Story mode](https://www.airship.com/docs/guides/messaging/editors/scenes/behaviors/). | | **Alternative text** | Optional. Text to be announced by assistive technology such as screen readers. Alternative text, also known as alt text, is a textual description of an image or video that is used when a person cannot see or access the visual image to help them understand its meaning. | | **Add action** | Optional. The behavior that occurs when a user taps/clicks the image. The option appears after providing a URL or upload. Not supported for video. The click/tap can also add or remove a [tag](https://www.airship.com/docs/reference/glossary/#tag), emit a [custom event](https://www.airship.com/docs/reference/glossary/#custom_event), and/or opt a user in to or out of a [Subscription List](https://www.airship.com/docs/reference/glossary/#subscription_list). Follow the steps in [Actions for in-app experiences](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/button-actions/). [iOS SDK 18.12+](/docs/docs/developer/sdk-integration/apple/ios-changelog/#18.12.0) [Android SDK 18.4+](/docs/docs/developer/sdk-integration/android/changelog/#18.4.0) | | **Action: Scene behavior** | Optional, appears only when an action is set. Determines how the Scene behaves when a user taps the image: **No action**, **Next screen**, **Previous screen**, **Dismiss** (closes the Scene), or **Dismiss and cancel Repeat** (closes the Scene and overrides the [Repeat setting](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/optional-features/#repeat-this-message)).
Scene behavior is not available when the action is Next, Previous, or No Action. The actions Dismiss Message, Preference Center, and Deep Link have Scene behavior options **Dismiss** and **Dismiss and cancel Repeat** only. | | **Action: Reporting label** | Required. A label to differentiate clicks/taps for the image in reporting.
By default, clicks/taps on elements with a configured action are reported using the In-app button tap event in the format button-tap-<button_action>--<button label>, where <button label> is the visible text on the element. When you enter your own reporting label, it replaces that text in the event name.
For example, if you enter Cat socks55 for the Submit Responses action, the event in reporting is button-tap-submit_feedback--Cat socks55.
Reporting labels support [Handlebars](https://www.airship.com/docs/reference/glossary/#handlebars).
| {class="table-col-1-20"} ## NPS Add a [Net Promoter Score (NPS)](https://en.wikipedia.org/wiki/Net_promoter_score) survey. The survey presents a question with a 0-10 answer scale that measures how likely users are to recommend your brand or product. Use it to gauge overall sentiment (relational NPS) or feedback on a specific experience like booking a flight (transactional NPS). Scenes support a single NPS survey. You must also configure a [Button](#button-or-button-group) or [Media](#media) (image only) using the [Submit Responses action](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/button-actions/#submit-responses). NPS is not supported in [Story mode](https://www.airship.com/docs/guides/messaging/editors/scenes/behaviors/). The device preview only displays settings for the unselected state, so you should verify the appearance of the selected state by testing on an actual device. Set for the NPS element: | Field or setting | Description | | --- | --- | | **Question** | Required. The question that should be answered by the user. The question text also functions as the content description, which is announced by assistive technology such as screen readers. | | **Labels** | Required. A description of each end of the 0-10 scale. For example, "Not at all likely" and "Very likely." | | **Required** | Optional. Makes answering the question a requirement for making the Submit Responses button or image active. Check the box to enable. | {class="table-col-1-20"} In the sidebar, first select a [text style configured in your brand guidelines](https://www.airship.com/docs/guides/messaging/features/brand-guidelines/#text-button-and-input-styles), and then configure the design properties. ## Question Add a question with a field where users can enter their own answers, or add a single or multiple choice question with answers users can select. Scenes support up to 10 questions. You must also configure a [Button](#button-or-button-group) or [Media](#media) (image only) using the [Submit Responses action](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/button-actions/#submit-responses). Questions are not supported in [Story mode](https://www.airship.com/docs/guides/messaging/editors/scenes/behaviors/). Set for the Question element: | Field or setting | Description | | --- | --- | | **Question type** | Required. **Open** questions are followed by a text field where users can enter a response. **Single Choice** questions are followed by radio buttons for selecting one of multiple answers you provide. **Multiple Choice** questions are followed by check boxes for selecting one or more answers you provide. | | **Question** | Required. The question that should be answered by the user. The question text also functions as the content description, which is announced by assistive technology such as screen readers. In [Performance Analytics](https://www.airship.com/docs/reference/glossary/#pa), it appears as the Survey Question. | | **Required** | Optional. Makes answering the question a requirement for making the Submit Responses button or image active. Check the box to enable. | | **Answers** | Required for single and multiple choice questions. The options a user can select to answer the question. To reorder answers, hover over an answer, select and hold the drag handle icon (), then drag and drop to a new position. | | **Store as attribute** | Optional, for single choice questions only. Enables storing answers as text or number [attributes](https://www.airship.com/docs/reference/glossary/#attribute). To use this feature, you must first [add the attributes to your project](https://www.airship.com/docs/guides/audience/attributes/adding/). See the steps following this table. | | **Randomize order** | Optional for single and multiple choice questions. Presents the answers in random order when the Scene is viewed in the app. If you reordered the answers by dragging and dropping, that order is ignored when you enable randomized order. Check the box to enable. | {class="table-col-1-20"} To configure storing as attribute: 1. Toggle to enable. 1. Search for and select an attribute. 1. Enter a value next to each answer. The value must match the attribute type (text or number). If empty, the response is not stored as an attribute. You cannot use the same attribute in multiple questions in a single Scene. The design properties for the question and answers are in separate sections. In the sidebar, first select a [text or input style configured in your brand guidelines](https://www.airship.com/docs/guides/messaging/features/brand-guidelines/#text-button-and-input-styles), and then configure the design properties. ## SMS [iOS SDK 19.6+](/docs/docs/developer/sdk-integration/apple/ios-changelog/#19.6.0) [Android SDK 19.9+](/docs/docs/developer/sdk-integration/android/changelog/#19.9.0) Add a field to register a submitted phone number as a channel or only collect it as data. Channel registration requires selecting a [sender ID](https://www.airship.com/docs/reference/glossary/#sender_id) to associate with the channels. Collection requires selecting which countries can submit phone numbers. The selected countries, or the country code associated with the sender ID, are listed in a dropdown menu and represented by the country’s flag. If more than one country is available for the field, the user must select one before entering their phone number. You must also configure a [Button](#button-or-button-group) or [Media](#media) (image only) using the [Submit Responses action](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/button-actions/#submit-responses). Use a [Text element](#text) to add a title for the field and provide disclosures. See also [Providing disclosures and other required information](https://www.airship.com/docs/guides/messaging/editors/scenes/screens/#providing-disclosures-and-other-required-information). * **Validation** — Phone numbers are validated when the Submit Responses and Validate Form actions occur. For valid formats, see [Validate Form](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/button-actions/#validate-form) in *Actions for in-app experiences*. * **Collection** — Collected phone numbers are available in [Performance Analytics](https://www.airship.com/docs/reference/glossary/#pa). * **Registration** — Registering a phone number as a channel automatically triggers the [double opt-in](https://www.airship.com/docs/reference/glossary/#double_opt_in) process, and the phone number is associated with the [Contact](https://www.airship.com/docs/reference/glossary/#contact) viewing the Scene. See [Register SMS Users](https://www.airship.com/docs/developer/api-integrations/sms/getting-started/#register-sms-users) in *Getting Started* and [Double Opt-In](https://www.airship.com/docs/developer/api-integrations/sms/opt-in-out-handling/#double-opt-in) in *Opt-In/Out Handling* in the SMS platform documentation. Registration using this field is handled the same as other SMS registration methods. For example, they appear in [Contact Management](https://www.airship.com/docs/guides/audience/contact-management/) and emit the same [Real-Time Data Streaming](https://www.airship.com/docs/reference/glossary/#rtds) events. > **Important:** When collecting phone numbers, record the collection or opt-in date for compliance purposes. Customers are responsible for providing their End Users with clear notice about how their phone numbers will be used, in line with specific use cases and regulatory requirements in the Customer's jurisdiction. Set for the SMS element: | Field or setting | Description | | --- | --- | | **Placeholder** | Optional. This text appears in the field before a user selects the field. It should describe the expected input. For example, "Phone number" or "Please enter your phone number". | | **Accessibility description** | Required. Text announced by assistive technology such as screen readers when a user focuses on the field. Enter a description, or associate an existing [Text element](#text) used as the field's label.Selecting text requires: [iOS SDK 19.8+](/docs/docs/developer/sdk-integration/apple/ios-changelog/#19.8.0) [Android SDK 19.10+](/docs/docs/developer/sdk-integration/android/changelog/#19.10.0) | | **Reporting label** | Required. This text appears as the Survey Question for question type `sms` in [Performance Analytics](https://www.airship.com/docs/reference/glossary/#pa). | | **Submission type** | Required. Determines whether the phone number is only collected as data or also registered as a channel. For channel registration, select at least one [sender ID](https://www.airship.com/docs/reference/glossary/#sender_id) to associate with the channels, one ID per country. For collection, select which countries can submit phone numbers. | | **Required** | Optional. Makes entering a phone number a requirement for making the Submit Responses button or image active. Check the box to enable. | {class="table-col-1-20"} In the sidebar, first select an [input style configured in your brand guidelines](https://www.airship.com/docs/guides/messaging/features/brand-guidelines/#text-button-and-input-styles), and then configure the design properties. ## Text Add a string of text. Scenes support up to 15 Text elements per screen. When using a Text element as the label for an input field, set it as the field's accessibility description. See **Accessibility description** in [Email](#email), [SMS](#sms), and [Text Input](#text-input). Set for the Text element: | Field or setting | Description | | --- | --- | | **Text** | Required. The text to display. | | **Add action** | Optional. Makes the text function as a link. The link can be a web URL, [Adaptive Link](https://www.airship.com/docs/reference/glossary/#adaptive_link), or Deep Link. Follow the steps for [Web Page](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/button-actions/#web-page), [Adaptive Link](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/button-actions/#adaptive-link), or [Deep Link](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/button-actions/#deep-link) in *Actions for in-app experiences*. | | **Action: Scene behavior** | Optional, appears only when an action is set. Determines how the Scene behaves when a user taps the text link: **No action**, **Next screen**, **Previous screen**, **Dismiss** (closes the Scene), or **Dismiss and cancel Repeat** (closes the Scene and overrides the [Repeat setting](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/optional-features/#repeat-this-message)).
Scene behavior is not available when the action is Next, Previous, or No Action. The actions Dismiss Message, Preference Center, and Deep Link have Scene behavior options **Dismiss** and **Dismiss and cancel Repeat** only. | | **Action: Reporting label** | Optional. A label to differentiate clicks/taps for the text link in reporting.
By default, clicks/taps on elements with a configured action are reported using the In-app button tap event in the format button-tap-<button_action>--<button label>, where <button label> is the visible text on the element. When you enter your own reporting label, it replaces that text in the event name.
For example, if you enter Cat socks55 for the Submit Responses action, the event in reporting is button-tap-submit_feedback--Cat socks55.
Reporting labels support [Handlebars](https://www.airship.com/docs/reference/glossary/#handlebars).
| {class="table-col-1-20"} > **Tip:** You can add a link to your privacy terms in a text footer using the Web Page action. Privacy terms can help users understand your data collection practices. In the sidebar, first select a [text style configured in your brand guidelines](https://www.airship.com/docs/guides/messaging/features/brand-guidelines/#text-button-and-input-styles), and then configure the design properties. ## Text Input Add a single-line text input field. You must also configure a [Button](#button-or-button-group) or [Media](#media) (image only) using the [Submit Responses action](https://www.airship.com/docs/guides/messaging/in-app-experiences/configuration/button-actions/#submit-responses). Use a [Text element](#text) to add a title for the field. Set for the Text Input element: | Field or setting | Description | | --- | --- | | **Placeholder** | Optional. This text appears in the field before a user selects the field. It should describe the expected input. For example, "Favorite film" or "Please enter your favorite film". | | **Accessibility description** | Required. Text announced by assistive technology such as screen readers when a user focuses on the field. Enter a description, or associate an existing [Text element](#text) used as the field's label.Selecting text requires: [iOS SDK 19.8+](/docs/docs/developer/sdk-integration/apple/ios-changelog/#19.8.0) [Android SDK 19.10+](/docs/docs/developer/sdk-integration/android/changelog/#19.10.0) | | **Reporting label** | Required. This text appears as the Survey Question in [Performance Analytics](https://www.airship.com/docs/reference/glossary/#pa). | | **Required** | Optional. Makes entering text a requirement for making the Submit Responses button or image active. Check the box to enable. | | **Store as Attribute** | Optional. Enables storing input as a text [attribute](https://www.airship.com/docs/reference/glossary/#attribute). To use this feature, you must first [add the attribute to your project](https://www.airship.com/docs/guides/audience/attributes/adding/). Toggle to enable, then search for and select an attribute. | {class="table-col-1-20"} In the sidebar, first select an [input style configured in your brand guidelines](https://www.airship.com/docs/guides/messaging/features/brand-guidelines/#text-button-and-input-styles), and then configure the design properties.