You are here:
In-App Message Display Controls
You have several options to orchestrate the display of your In-App Messages.
Display Trigger
Within the In-App Message activity in Journey Builder, define the user action that triggers message display.
- Use this control to define when or where the message displays to the user.
- For example, display a message when the user views a specific screen or buys a specific item.
Display Priority
Within the In-App Activity in Journey Builder, define the priority of your messages.
- Use this feature to control the order that the messages appear in, even if they have the same display trigger.
- For example, you have two different Purchase messages. The message that you set as Priority 1 appears when the user makes a purchase.
Display Delay
Within the In-App Message activity in Journey Builder, define how long to wait before displaying the message after the user meets all of the display criteria.
- Use this feature to create a smoother user experience in your app. Instead of immediately showing a message when a user performs a particular action, delay the display.
- For example, if the user views a particular screen, which triggers the message, wait 2 seconds and then display the message.
Display Limits
Within MobilePush Administration, define the maximum number of In-App Messages that can appear to a user in a single app session. When multiple messages are allowed within a single session, you can also set the minimum time interval before displaying another message. These settings apply at the device level.
- Many active in-app campaigns can run at one time. A user can qualify for many and so can see many messages in a single session. Use this feature to avoid spamming users.
- For example, a user can qualify for messages based on purchase, screen view, and shared content. If you set the Display Limit to two messages, the third action doesn’t trigger message display.
- For example, when multiple messages are allowed in a single session with a Display Limit
time period, the MobilePush SDK doesn’t evaluate for potential triggers during that time.
- The user opens the app and a message appears.
- The SDK waits 30 seconds before evaluating other message displays.
- If the user views the specific page 20 seconds after opening the app, the message doesn’t appear and is eligible to appear later.
- If the user views the specific page after the 30-second limit, the message appears.
Note Display Limit enforcement is on a best-effort basis. On the next app open, Marketing Cloud Engagement syncs with the SDK to retrieve limits. If the message is set to appear immediately upon app open, the user sees the message if the sync isn’t completed.
