If you have a mobile application for your users, In-app Messages are a way of displaying banners to them within the app. The feature uses the same principle as pop-up web layers that are displayed to your website visitors.
In order for In-App Messages to work, Mobile SDKs must be implemented (Android v2.7.0 / iOS v2.6.0).
To create an in-app message go to
In-app messages >
+ New in-app message
You can edit the design of the in-app message in the right column. There is no limit on the number of characters or words that you can use in an in-app message.
If you want to delete any component, for example, a button or a header, you only need to delete its text and the whole component will be deleted along with it.
You can currently only choose from 4 pre-existing templates for in-app messages. No HTML is allowed.
To see how the message looks for a specific customer/segment of customers or for Android or iOS devices click on
Preview and select the specific segment customers or the kind of the desired kind of device.
When setting up how will the In-App Messages interact with your customers, you will be faced with implementing Buttons into them. These offer you two choices:
- Deep link - navigates your customer from the In-App Message onto specified link
- Cancel - navigates your customer away from the In-App Message, thus quitting it
If you want to AB test your in-app message, you first need to enable the AB testing in the top right corner. After that, you can go to the
A/B TEST tab next to
DESIGN and use it as explained in the AB Testing article.
You can find the
SETTINGS next to the
A/B TEST tab.
Apart from the
Show on and
Priority (which does not exist in web layers), the settings in in-app messages work in the same way as in web layers. Therefore, the two will be explained here and the rest in the Web layers article.
Choose on what particular event should the message be shown. For example, the message can pop-up immediately when the app loads if you choose the event
If multiple messages are supposed to be shown to a particular customer for the same event, they will only see the message with the highest priority (highest number). The message with lower priority would remain in the backlog and if it eventually becomes the message with the highest priority relative to remaining messages then it would be shown to the customer on a particular event.
Specifies the time delay (in milliseconds) between the moments when the message is triggered and when it is actually displayed to the customer.
Specifies the time (in milliseconds) after which an in-app message is automatically hidden in case the customer does not interact with it.
You can compare the conversion and click rates by going into the
Evaluate tab where you can see a dashboard with measurements of the effectiveness of the sent in-app messages.
Each in-app message shown to a customer is tracked as a
banner event with the same attributes as in any web layer. However, with in-app messages, an additional
type attribute is tracked:
The type of the web layer shown.
You can decide to only target the customers with the highest likelihood of conversion. By using Predictions you create a customer segment with the highest probability of completing a certain action like purchase or interaction. These segments can thereafter be used in in-app messages.
You can personalize the content of your in-app messages for every individual customer. This is possible thanks to the unified single customer view where you can use all the customer data collected through multiple different channels. You could, for example, check which customers have not opened your newsletter with personalized products, and display to them that same selection of products in the app instead.
Due to personalisation being enabled, you can also use product recommendation models within in-app messages to show recommended products.
This feature allows you to clone In-App messages to other projects you have access to. Read more about Cloneable Data Mapping in our Data Manager article.
Updated 25 days ago