App Screens

Display in-app experiences when a user views a specific screen in your app.

First, add an app screen in your project settings. Then you can configure a SceneMulti-screen experiences 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. Scenes can include survey questions or be presented as a story. , SurveyQuestion-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. , or 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. to display when that screen is viewed.

Requirements

The screen must already exist in your app. Ask your developer for the screen name as registered in your app code. You will enter the screen name in the Unique ID field when adding the screen to your project. See platform guide: Mobile Screen Tracking.

Adding an app screen to your project

  1. Go to Settings » Channels » Mobile Apps and click Manage for App Screens.
  2. Click New App Screen and enter:
    • Unique ID — The screen name from your app code.
    • Description — Extra information to help you identify this screen from the list of all app screens in your project.
  3. Click Submit.

Editing or deleting an app screen

  1. Go to Settings » Channels » Mobile Apps and click Manage for App Screens.
  2. Click   to delete, or click   to edit, then click Save.

Using app screens with in-app experiences

The Screenview trigger causes an in-app automation, scene, or survey to appear when your audience views a screen a specified number of times. See: In-app experience triggers: Screenview.

You can also set conditions that determine whether or not an in-app experience displays after a trigger event occurs. The message does not display until your conditions are met. See: In-app experience display conditions: Viewing a specific app screen.