Branching for Scenes

Whether you’re guiding a user through onboarding, feature education, or a promotional flow, you can create flexible, real-time experiences from a single SceneA single or multi-screen in-app experience cached on users’ devices and displayed when users meet certain conditions in your app or website, such as viewing a particular screen or when a Custom Event occurs. They can be presented in fullscreen, modal, or embedded format using the default swipe/click mode or as a Story. Scenes can also contain survey questions. configuration. A user’s interactions and responses on the current screen determine which screen appears next.

About branching

Branching is essentially a decision tree, and its logic uses conditional if/then/else statements. You define rules where if a user performs one or more actions, then which screen to go to based on the action, and an else alternative if none of those actions were taken. You can add multiple if conditions for each rule and multiple rules per statement.

Implementing branching in your Scenes offers several benefits:

• More interactive experiences — Create adaptive flows that change based on user interactions to make your in-app content more customized and engaging.
• Reduced drop-offs — Present specific content to streamline the user experience and decrease abandonment rates.
• Improved data collection — Ask follow-up questions in surveys for more accurate, in-depth data and increased submission rates.
• Better ROI on campaigns — Drive more targeted interactions for more effective campaigns.

Configuring branching

While configuring Scene content, select the branching icon in the left sidebar, and your screens will appear in a map view. From there, set branching logic to create paths between screens. Each screen is represented as a card, and each card displays the screen name and icons for the components that can be used for setting branching logic:

• Selected NPS survey score
• Answer to single or multiple choice question
• When a button or image configured with an action is clicked/tapped

In addition to setting logic rules to create paths, you can and also add, duplicate, and remove screens from the map. As you design, you can test the logic using the Interactive mode preview tool. To see a summary of a path with the option to remove it, select the connecting line between screens:

Additional updates for Scenes

We also made some updates for design flexibility, organization, and understanding Scene performance:

• More screens — Each Scene now supports up to 20 screens.

• Custom screen names —  When editing screens, select the three dots icon () for a screen in the list, then Rename, and then enter a custom name. This updates the name as is appears in the list of screens and the branching map.

• User path reporting — Message reports for Scenes now include a flow chart that displays a visual representation of the user progression between screens and metrics associated with each screen and branch.

Requirements and documentation

Scenes are an AXP feature. Branching requires SDKs iOS 19.6+ and Android 19.9+.

Go to the Scene branching docs for all the details. To upgrade your SDK versions, follow our guides:

• Android SDK migration guides 
• iOS SDK migration guides