Send Mobile In-App Messages

The Messaging and Mobile A/B testing features are not available for purchase and will be deprecated from the product on January 1st, 2022. Read more information on the Mixpanel blog.

Mixpanel allows you to create and send richer messages that appear while your iOS app is running. If you are using our in-app messages product, follow these steps:

  1. Include the latest version of the Mixpanel iOS library or Android library in your app.
  2. Make sure you are identifying your users in the app. You must also create a profile for a user to send an in-app to them.
  3. Create an in-app message on the Messages tab of the Mixpanel website.

Mobile in-app messages will send once per user, but users with multiple devices may receive the notification multiple times. 

Mixpanel can also send web in-app messages.


The Mixpanel Android library automatically checks for a message when your app loads or resumes from the background.
If an unseen message is available for the current user, it displays immediately in an overlay view.

Creating a Mobile In-App Message

In Mixpanel you can contact your users directly through your app with in-app messages.

Select Mobile from the pop-up window to see this form:


Customize Display of an In-App Message

To select the size of your message, choose either "Fullscreen" or "Mini". To select the color of you message, choose either "Light", "Dark", or "Custom".


Insert an image into your message and write your message directly into the preview image.

You can also choose to add an A/B test to your push notification by selecting ADD AN A/B TEST.

Save a draft of your message at any time in this process by clicking the Save button at the top of the page.


You can view all of your saved drafts by clicking on the Drafts tab of the main Messages page.


Using Profile Properties

Similar to emails, in-app messages replace content wrapped in {{}}.

For example, if you add a Location property to your user profiles, you can send messages like this:

Come and visit us at our {{ user[‘Location’] }} office.

A user with a profile property Location: Asheville will get this message:

Come and visit us at our Asheville office.
If some of your profiles have a value, but others don't, you can use a fallback value:
Come and visit us at our {{ user['Location'] | default:'nearest' }} office!

Profiles without a Location property will receive this message:

Come and visit us at our nearest office!

Targeting Users

After submitting the form for your message design and content, you will then need to define the targeting criteria for the users who will receive the message. Learn more about filtering by events, properties, and cohorts in this article. You can also target users based on prior messaging or target messages with calendar dates. 

Event-Triggered In-App Messages

Install the latest SDKs

You will need to install the following versions or higher to access this functionality:

If you would prefer to keep the old functionality, refer to the Scheduling section below.

After submitting the form for your message design and content, as well as your targeting criteria, you can choose the event trigger option on the delivery settings page to send an in-app message when a user triggers a specific event.

For example, you can send a message saying “Congratulations” when a user triggers an event such as a “level-up” in a game.

This feature is only compatible with events captured by Mixpanel’s client-side SDKs (Android, iOS - Objective-C, and iOS - Swift). The event-triggering event must be from the same SDK as the message for the message to be sent. For example, if you're sending a mobile in-app message on Android, the triggering event can't come from a Javascript event. An in-app message won't show on any mobile device since the event is exclusive to the Javascript SDK.

Check the box beside Display messages when users perform… and then select the trigger event.


You can filter the message by an event property. This will cause the in-app message to send when the trigger event is performed and the trigger event has a particular property tied to it.


Note that:

  • The in-app message only sends the first time the event is triggered (no recurrence).
  • You can only use one event and one event property.

Schedule an In-App Message

By default, mobile in-app messages shows immediately when your app loads. Note that users will receive an in-app message more than once if they use multiple devices.

However, it is possible to customize this behavior and control exactly when an in-app message appears.

If, for example, you have a game and would like to show a message when a user accomplishes a goal, you must turn off the automatic showing of messages by setting showNotificationOnActive to NO and call showNotificationWithID at the appropriate point in your app.

// In application:didFinishLaunchingWithOptions:
Mixpanel *mixpanel = [Mixpanel sharedInstanceWithToken:
// Turn this off so the message doesn't pop up automatically.
mixpanel.showNotificationOnActive = NO;

- (void)playerFinishedLevel
    [mixpanel showNotificationWithID:INAPP_NOTIFICATION_ID];

If you don't want to specify the message ID, you can use showNotification, which shows the first available in-app message targeted at the identified user, if there is one.

Messages are never shown twice to the same user, so you don't have to check if the user already saw the message before calling showNotificationWithID.

If you don't want Mixpanel to check for new in-app messages when your app becomes active, you can turn it off by setting checkForNotificationsOnActive to NO.

This action sets in-app messages not to show automatically, and that the network request to retrieve the messages will occur only when you call showNotification or showNotificationWithID.

Preview In-App Message For Users With Older Mixpanel SDKs

If you choose to create a backup theme to be sent to users who have not yet upgraded to the latest version of your app, you can see a preview of the message by hovering on the icon next to the Backup Theme dropdown.


Did this answer your question?



Article is closed for comments.