This page gives marketers a complete overview of how to plan, configure, and use in-app messages in Mapp Engage.
Overview
What is In-App Messaging?
In-app messages allow you to communicate with users while they are actively using your mobile app. Messages can appear instantly or be stored in the user’s message center (Inbox), depending on the selected message type.
You can use in-app messaging to welcome new users, highlight new features, promote offers, or respond to specific actions in the app — all without requiring push permission.
Why use In-App Messaging?
Reach users directly in the app — in real time or via inbox
Engage users contextually based on in-app behavior
Support user onboarding, feature promotion, and re-engagement
Add interactive, branded messages without push opt-in
Key Capabilities in Mapp Engage
Define event-based triggers for message delivery
Target specific user segments
Choose between flexible Web or fast Native formats
Customize message layout, visuals, and actions
Track views, interactions, and delivery results
Message Types and Formats
In-app messages differ in when they are shown and how they are displayed in the app.
You’ll select both the message type and the format during the message configuration process.
Message Types
Type | Behavior |
|---|---|
In-App | Shown immediately when trigger conditions are met |
In-App + Inbox | Shown in-app and stored in the message center (Inbox) |
Inbox | Stored in the message center only |
Message Formats
Format | How it works |
|---|---|
Web | Rendered in a WebView. Offers full design flexibility via HTML and can be updated at any time from the UI. |
Native | Uses fixed SDK templates (e.g. banner or fullscreen). Loads faster and blends smoothly with the app UI. |
Message Setup Workflow
Before You Start
Make sure the following elements are ready before you begin creating a message:
Target Segment: In-app messages can only be sent to all contacts or predefined segments. Groups are not supported. If you want to target a specific audience, create a segment first.
Trigger Event: In-app messages are activated by app events (e.g. screen view, button tap). These events must be tracked by the SDK. If an event is not available, the message will not be triggered.
Message Configuration Overview
Each in-app message includes the following components:
Targeting & Triggering
Target Segment: Who should receive the message
Trigger: The app event that activates the message
Content & Display
Layout: Choose between banner, fullscreen, or custom
Content: Text, images, and calls to action
Button Actions: Define what happens on user interaction (e.g. open a link or app screen)
Delivery Settings
Frequency: How often a message can be shown to the same user
Expiration: Defines how long the message stays active
Looking for a structured learning path?
Learn step by step in our Academy Course: Mapp Engage - SMS, Push & In-App.
For Developers
To use in-app messaging, your app must be integrated with Mapp’s Mobile SDK.
For a full breakdown of how messages are triggered, processed, and tracked, see Delivery Logic & SDK Tracking for Developers.
.png)