Choose a delivery method

When you compose a message, one of the most important things is to decide when to deliver it to your users. Leanplum provides a variety of methods for message delivery.

 

Let’s go through the delivery options based on the most common use cases. Keep in mind that regardless of the delivery type, each message will only be delivered to users that fit the target you’ve set. 

Delivery Type

Use Case

Immediate

“I want to send a message right away”

Scheduled

“I want to send a message on October 2nd, 2017”

Triggered

“I want to send users a message after they do something specific in the app”

Triggered locally

“I want to send users a push notification after they enter a geofence”

Manual

“I want to bypass Leanplum’s automated delivery options and use a server-to-server call to trigger a message”

Note: These delivery methods are not uniformly available for all types of message in Leanplum. Push notifications, for example, are the only message type that can be triggered locally. In-app messages cannot be scheduled, sent immediately, or manually; they can only be triggered by a user’s activity in your app.

Immediate

Available for push notifications, email, app inbox messages and webhooks.

Sends the message when you click “Send Now”. Some messages may take up to 15mins for us to process and send to your users.

Scheduled

Available for push notifications, email, app inbox messages and webhooks.

You can also schedule delivery at a specific date and time. You can choose between four possible timing/timezone options:

  1. Optimal time: Leanplum will send the message to each user during the time of day that they tend to be most active within your app.
  2. User’s timezone: Users will receive the message at the time entered in their own timezone.
  3. Pacific time: Users will receive the message at the time entered in Pacific Standard time.
  4. UTC time: Users will receive the message at the time entered in UTC time.

 

Note: If you set Quiet Hours and the message delivery time falls into those hours, the message will be sent as soon as the Quiet Hours period has ended (e.g., if your Quiet Hours end at 6am and a message was scheduled for 5:45am, it will be sent at 6:01am).

Find more information on choosing a delivery time for scheduled push notifications, click here.

Triggered

Available for all message types in Leanplum; triggered options appear under “Display when” for in-app messages.

You can trigger a message based on user activity instead of scheduling it at a fixed time. This can be a powerful way to reach a user at the right time, since delivery will be relative to their activity in your app.

Available triggers are based on events tracked by our SDK and custom events and states you track with our SDK. Options include:

  • User first starts app
  • 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.
  • 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).

Delay

An option to delay the message delivery by a certain number of seconds, minutes, or days after the trigger occurs.  

Exclusions

You can exclude certain users from receiving a triggered message. The options are the exact same as the trigger options (User starts app, User triggers event, etc.).

For example, you can create an onboarding message that will be delivered to users 5 days after the user first starts app unless the user completes their profile (user triggers event > profileComplete).
deliveryExclusion.png

Limits

You can limit the number of times a triggered message is sent to the same user. This ensures that even if the user meets the delivery criteria multiple times, they will not receive the message more than you intend.

Triggered Locally

Available for push notifications only.

Used to trigger push notifications using geofences. You can send a push notification to a user when:

  • User enters region
  • User exits region

To use this feature, your app must include the Leanplum SDK Location library. For more info, see Message users when they enter or exit a geofence region.

Manual

Available for push notifications, email, app inbox messages and webhooks.

You can choose to deliver the message manually via our API.


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