Send an in-app message

To get started, go to the Messaging dashboard and click Create Message. Click the In-App Message dropdown, then choose an in-app template.

Choosing a template

There are several in-app message templates to choose from, including Alert, Center Popup, Confirm, Interstitial, Push Pre-Permission, and Web Interstitial. Each template has unique options and features, or you can create a custom template. Select one of the template options to see a preview of your message on the on-screen device at the left side of the composer. See In-app message templates and customization for more on templates. 

Compose the message

In the Compose section, add your Title and Message. For some In-App messages, you can change the font color of these elements.

Personalized message copy

All messages can include dynamic elements, such as user attributes and event parameters, in the message copy, allowing you to deliver messages tailored to each unique person using your app. For more information on how to configure dynamic copy, click here


Customize the design

The look and feel of the Center Popup, Push Pre-Permission, and Interstitial in-app messages can be changed directly from the Leanplum Message Composer. Just click the section you want to edit to make changes to the color, text, or images in your message. 

See In-app message templates for more details on the specific options for each template.

Background image size

Our SDK does a lot of work behind the scenes to fit your uploaded image to the in-app message template on a wide array of devices. For Center Pop-up and Push Pre-Permission messages, that means fitting the entire image to the message template itself (the pop-up) with some shrinking or stretching. For Interstitials, however, it means fitting the image to the size of the device's screen. In this case, the image may be cropped to fit the user's screen.

To prevent cropping, we recommend using segments with your Interstitial background image to target different devices (and therefore screen sizes). This way, you can get the image to display perfectly on both iPhone and iPhone Plus, for example. 

To add a segment to your background image setting:

  1. Hover over the background image label
  2. Click the +
  3. Create a segment by selecting Technology > Device model from the dropdown menu
  4. Enter in the device you want to target for this image file (e.g. "iPhone 7")

Set button actions

Accept and Cancel actions are what happens when the user clicks the "Accept" or "Cancel" buttons. You can edit the names of these buttons by editing the Accept and Cancel text in the Composer (replace "Cancel" with "No thanks" for example).

The default button action is "No Action" which simply dismisses the In-App message. You can also set the button action to direct users to another in-app message, or to a web or deeplink URL using the "Open URL" action. 

Set in-app message delivery

In-app messages, unlike email or push notifications, cannot be sent immediately. When you setup an in-app message, you need to set the "Display when" criteria, which will determine when the message will be displayed.

You can think of these like setting an achievement or event. When a user reaches a certain point, or commits a certain action, they'll get the message. For example, in-app messages can be set to display when a user does something you've defined in our SDK (an Event), enters or exits a geolocation, or advances to a location (a State) in your app.  

Note: You can only use Events and States that you have explicitly tracked via our SDK for "Display when" criteria. You cannot trigger an in-app message based on something on your server.

Available in-app message triggers:

  • User starts app
  • User starts or resumes app
  • User triggers event. Two options:
    1. triggers: Send the message when the event occurs, regardless of parameter values
    2. triggers when parameter: Send the message when the event occurs AND an event parameter is a certain value.
      Note on parameters:
      When in-app messages are associated with multiple different parameters of the same event, only one of those messages can be displayed at the time of the trigger event. See in-app message FAQ for more.
  • User advances to state. Two options:
    1. triggers: Send the message when the State changes, regardless of parameter values
    2. triggers when parameter: Send the message when the State change occurs AND a State parameter is a certain value.
  • User attribute changes. Three options:
    1. changes: Send the message when a certain attribute changes, regardless of what it changes to, or from.
    2. changes to: Send the message only when a user attribute changes to a certain value.
    3. changes from/to: Send the message only when a user changes from a certain value (A) to another specified value (B).
  • User enters region
  • User exits region 

Set Limits

You can limit how frequently, or how often, a message is displayed. See how to limit the frequency of in-app messages.


Was this article helpful?
Have more questions? Submit a request