You are here:
In-App Messaging FAQs
Frequently asked questions about MobilePush in-app messaging.
What’s the Difference Between an In-App Message and a Push Notification?
You can use an in-app message to communicate with a user who is using the app. A push notification displays when a user isn’t using your app. Push notifications are helpful to re-engage a user and draw them back to your app.
What’s the Difference Between an In-App Message and an Inbox Message?
If your app includes an inbox, an inbox message is sent to a user’s inbox and can stay there for a specified time period. Inbox messages open to a CloudPage and can contain personalized information. For example, an inbox message could include information about an upcoming hotel stay, a weekly grocery ad, or a coupon code. You can also tie an inbox message to a push notification to draw the user to the inbox section of the app. In contrast, an in-app message displays to the user only one time and when the user closes it, the message doesn’t show again.
When Do I Use the Different Layouts for an In-App Message?
Full-screen and modal messages are best for new features, product offerings, or other important messages. Because full-screen and modal messages require the user to dismiss or close the message, they can be disruptive to the user's experience. Use a banner for shorter messages that aren’t as high in priority. A banner message takes up less screen space, and the user can swipe it away or use a close or dismiss button.
Do I Need the MobilePush SDK to Send In-App Messages?
Yes. The MobilePush SDK version 6.3.0 or later is required for in-app messaging functionality in your app.
What’s In-App Message Priority and How Do I Know Which Message Shows First?
Priority determines which in-app message displays when more than one message is available. A priority 1 message displays first. The next time the user opens the app, the next highest priority is displayed. If no message priority is set or multiple messages have the same priority, the next message displayed is the message with the most recent last modified date for the activity.
How Is an In-App Message Displayed on a User’s Device?
When a contact enters a journey, the in-app message is sent to the person’s device. After the message is downloaded to the device, the highest priority message is displayed the next time the user opens the app.
When Do I Use the Dismiss Icon in My In-App Message?
All in-app message layouts include a dismiss icon in the top-right corner. If you don’t want to have a dismiss or close button in the in-app message, you can use the icon instead.
Where Do I Find Reporting for My In-App Messages?
To view a summary of all in-app messages, click the Push In-App Account Summary report in Analytics Builder. To get a snapshot of a specific message’s performance, choose a running journey in Journey Builder and click the in-app message activity. For more performance, engagement, and delivery details about your in-app messages, see the preconfigured dashboards in Intelligence Reports.
How Is a Message Handled When a User Has Multiple Devices?
When a user has multiple devices, each device can be registered and opted in for push notifications. For any opted-in device, a silent push notification is sent to prepare the device for the in-app message. If a device is opted out, a silent push notification isn’t sent. Instead, the opted-out device can pull available in-app messages only when the app is in the foreground. An in-app message appears only on the first device where the user accesses your app.
How Many In-App Messages Can I Send to a Device?
The app downloads up to 50 in-app messages at a time. After a message displays, it’s removed from the device, and the next message is downloaded.
If a User Shares a Device with Another Person, Do They Both See the In-App Message on That Device?
The MobilePush SDK doesn't support multiple users sharing a single device. When an in-app message is sent to a shared device, both contacts may see the message.
Can Multiple In-App Messages Be Shown During a Single Session?
Only one in-app message is shown per user session. A user session is defined as the user opening or foregrounding the app and then closing or backgrounding the app to complete the session.
Can I Set the Push Notification to Open an In-App Message?
Yes. Although you can’t link directly to an in-app message, you can make the chain of events appear seamless to the user. Set up your journey to send an in-app message activity with a priority of 1. Immediately following your in-app message activity, add a push notification activity to your journey canvas. Make sure that the active timeframe for your in-app message matches the scheduled date for your push notification. The user receives the in-app message in the background. Then the user receives the push notification. The next time the app is opened, the user sees the in-app message.
Can I Display an In-App Message at a Specific Time?
Yes. Your developer can detect when an in-app message is available for display and choose to show it later. Refer to the iOS and Android SDK documentation for more information.
Am I Billed for Messages That Users Don’t See?
Each in-app message is charged as one super message per contact, regardless of whether the user has downloaded or viewed the message. Additionally, if a device is opted in for push notifications, a silent push notification is sent before the in-app message to prime the device for the in-app message. You’re billed for each silent push notification sent, even if the user doesn’t open the in-app message. In most cases, a notification displays on only one device per contact. However, it’s possible that a user closes the app before Marketing Cloud Engagement recognizes that the in-app message was viewed.
For example, a contact has two devices, and only one is opted in for push notifications. When the contact views the in-app message on the opted-out device, you’re charged for two super messages: one for the generation of the message and the other for the silent push notification sent to the opted-in device.
