Leanplum's user guides and developer documentation.

Leanplum Documentation

Leanplum's user guides, SDK setup, API docs, and more resources are here to help you get the most out of A/B testing, Campaigns, Messaging, and Analytics.

In-app message prioritization

If a user triggers multiple in-app messages at the same time, priority levels allow you to choose which message is most important to display.

Without in-app message prioritization, a user who triggers multiple in-app messages off the same "Display When" event will see one of the messages at random.

How it works 📩

When a user qualifies for and triggers multiple in-app messages at the same time (based on the "Display When" event), our SDK will deliver the message with the highest priority level and mute all other messages. Muted messages are not displayed, so they will not have View events tracked.

If the triggered messages have the exact same priority level, then only one of the messages will show at random.

📘

How targets affect prioritization

Leanplum checks message priority after the message "Targets" and "Display When" settings are evaluated. This means that each user will see the message with the highest priority of all the messages that they qualify for. For example, one user may fit the target group for a priority 1 message, while another user only fits the target for your priority 3 message.

Setting message priority 🔢

Go to the top right of your in-app message's Display when setting to set the message's priority level. Priority can be set from 1 (highest) to 999 (lowest). If not specified (left as "None"), messages are assigned a default priority of 1000 (the lowest priority).

Examples

Let's say we have the following in-app messages activated, all of which are set to display when “User starts or resumes app." Each has been assigned a priority of 1, 2, or 3.

  • Daily Deal (priority 2)
  • Reminder Message (priority 3)
  • Global Promotion (priority 2)
  • New User Tip (priority 1)

A user could meet the targeting requirements for none of the messages, all of the messages, or some of the messages. For our example, here are four possible scenarios a user could fall into:

  • Scenario 1: The user is eligible for all four messages. This user will receive the message at the highest priority level — in this case, the New User Tip (priority 1).
  • Scenario 2: The user is eligible for the Reminder Message (priority 3), the Global Promotion (priority 2), and the Daily Deal (priority 2). This user will receive either the Global Promotion message or the Daily Deal message (selected at random).
  • Scenario 3: The user is eligible for only one message — the Reminder Message. This user will only receive the Reminder Message (priority 3).
  • Scenario 4: The user is not eligible for any of the messages. No message will show.

How to access this feature

Reach out to your customer success manager if you are interested in activating this feature.

IAM prioritization is supported on Leanplum Android SDK 1.2.25 and higher and Leanplum iOS SDK 1.3.12 and higher. If your end user is still using a version of the app with an older SDK version, then the priority field will be ignored, and all messages will be treated as if they have the same priority level (only one will show at random).

Updated about a month ago


In-app message prioritization


Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.