Mobile In-App Messaging in Engage Studio delivers a personalized experience while a customer is actively using a mobile app. Use it for contextual offers, onboarding, announcements, and interactive campaign content without relying on a Push notification.
This overview explains the available experiences and links to the setup, campaign creation, Hosted Pages, SDK, and measurement guides.
Mobile In-App Messaging is currently in beta. Message types, APIs, payloads, and native SDK behavior may change before general availability.
Mobile In-App Messaging is the Engage Studio capability that returns a targeted message when an event occurs in a mobile app. Realtime Personalization 2.0 evaluates the audience and delivery conditions; the Engage Mobile SDK displays the returned experience.
Use Mobile In-App Messaging when the next action depends on the customer's current screen, event, or profile context.
| Message type | What it displays | Typical use cases |
|---|---|---|
| Modal | A centered message over the current app screen. | Coupons, important announcements, onboarding prompts. |
| Banner | A message anchored to the top or bottom of the screen. | Lightweight promotions and contextual reminders. |
| Hosted Pages | A URL-based web experience displayed full-screen inside the app. | Coupons, stamp cards, lotteries, surveys, forms, and interactive campaign pages. |
A Hosted Pages experience is not a persistent Content Card or Inbox item. It is also different from Engage Studio's standalone Landing Page Delivery capability.
- A customer reaches a tracked screen or performs a tracked action.
- The app sends an event through the Engage Mobile SDK.
- Realtime Personalization evaluates the audience and delivery conditions.
- The Personalization response contains a matching Modal, Banner, or Hosted Pages.
- The Engage Mobile SDK renders the experience.
- The SDK records supported customer interactions.
If no campaign matches, the SDK does not display anything. This is a normal result, not an error.
For the exact response parsing, filtering, and deterministic message selection behavior, see Handle P13N Responses and Select a Message in the SDK reference.
| Goal | Guide |
|---|---|
| Prepare RT 2.0 and the app integration | Set Up Mobile In-App Messaging |
| Create and launch a campaign | Create a Mobile In-App Message |
| Compare Modal, Banner, and Hosted Pages settings | Message Types and Appearance |
| Configure a URL-based full-screen experience | Hosted Pages |
| Integrate the iOS preview SDK | iOS SDK Integration |
| Integrate the Android preview SDK | Android SDK Integration |
| Reference SDK APIs and event definitions | Engage Mobile SDK API and Event Reference |
| Choose supported trigger events and fields | Mobile In-App Events and Fields |
The native Engage Mobile SDK is the beta integration path for retrieving and rendering Mobile In-App experiences. The app remains responsible for notification permissions, Push receipt, Deep Link routing, and app-specific actions.
- Mobile In-App Messaging is in beta.
- A Hosted Pages experience is a transient full-screen experience, not a persistent Content Card or Inbox feed.
- The preview native SDK displays one message at a time.
- Frequency, targeting, priority, and suppression decisions are handled by Realtime Personalization; the SDK does not provide a local campaign queue.
- Native SDK package distribution and version compatibility are subject to change before general availability.