In-App messaging in Mapp Engage gives you multiple opportunities to connect with your audiences. In addition to the standard Web In-App feature, Mapp also offers Native In-App messaging.
The In-App feature helps you custom-tailor messages to your app users. You can design the appearance of the message with templates or custom-tailor the HTML code.
These messages can be sent immediately, on a specific day and time, or upon a triggering event. Messages can be sent to all app users or specific target groups.
In-App can be used along with Mobile Push Messaging.
Deliver specific content to your customer in real-time.
Engage users at defined points within the app flow.
Welcome new customers to the app as they log in.
Create full-screen and banner messages with templates or in HTML.
Engage customers with notifications of achievements for games and contests.
Make recommendations about the shopping cart.
Engage contacts with new content.
Limit the number of times a message displays for a customer over a specified time.
Track message impressions and clicks.
In-App Message Flow
Differences between Web and Native In-App
The differences between Web In-App and Native In-App are mostly technical. However, they result in different user experiences.
- Messages are rendered by native Android / iOS system components. This means that:
- they display faster, and
- offer a more attractive look and feel thanks to using native Android / iOS font.
- Native exchanges much less data with the server, which saves the recipient's Internet bandwidth. Thanks to an image caching system, images are downloaded only once and can be displayed multiple times.
- Web In-App is a more flexible form of In-App messaging. You can create these messages with almost any content and it will be displayed.
- Takes longer to display.
Is displayed in a mini web browser and therefore does not offer as natural a look and feel as native In-App.
The message creation flow is the same for both types of In-App messages, you just have to select the template you want to use. For more information, see In-App Message (window).
Components of In-App Messaging Communication
Each In-App message requires three primary components: an event, a target audience, and a message.
The event causes an action in In-App. When an event occurs, a message is delivered to the user in real-time.
The target audience contains the criteria for customers to receive the message. You create target audiences in the In-App feature or in Whiteboard NEW. Customers who match the criteria of your target audience are eligible to receive messages.
The message contains the content that you send to the customer. When you create a message, you then link the message to an event and a target audience.
When an app sends an event to In-App for the first time, the event is created in the In-App feature. The event must exist in In-App before you link the event to a message.
Explore In-App Messages