HomeUser GuideDeveloper GuideChangelog

Triggered delivery

Suggest Edits

With triggered delivery, targeted users enter the campaign only when they complete a specific action — such as tapping a button or completing a purchase.

Users must complete the selected trigger(s) in order to enter the campaign. This type of behavior-based delivery can be more effective at driving engagement than scheduled one-time blasts.

To send behavior-based campaigns:

  1. Select the Triggered delivery option
  2. Specify Delivery trigger - the event(s) that trigger(s) the delivery of the Campaign. There are several trigger event options to choose from in the dropdown.
  3. Select Deliver delay (in Single-message campaigns only)
    Example: [1] [days] [exact time] [After user triggers this campaign]
  4. Specify campaign Start
    1. Select the Start immediately after publish option to start the campaign immediately after Start Campaign confirmation button is clicked
      or
    2. Select the Start on [Date] [Time] option to schedule campaign start on a specific date and time (default)
  5. Specify campaign End (optional)
    1. Finish campaign manually is selected by default. That means that you can later decide when to finish the campaign on your own by clicking the End Campaign button.
    2. Select the Finish on [Date] [Time] option to schedule campaign end on a specific date and time

📘

End Date

If your campaign involves triggered in-app messages or variables, you may want to set an end date and time to prevent users from triggering messages that are no longer relevant (like after a sale is already over).

Trigger Event Options

EventDescription
User first starts appWhen a user opens the app and initializes Leanplum for the first time.
User starts app
When a user opens the app and initializes Leanplum.
User starts or resumes app
When a user opens the app or brings it up from the background.
User triggers event When a user does a specific event. (Can be one of your custom events, or a Campaign's Enter or Exit event.)
User triggers event with parameterWhen a user triggers an event with a parameter value that contains, is greater than, or is less than a certain value.
The parameter name must be an exact match - it is case sensitive. The parameter value is case insensitive - it will match both "My Value" and "my value".
User advances to stateWhen a user advances to a particular state.
User advances to state with parameterWhen a user advances to a state with a parameter value that contains, is greater than, or is less than a certain value.
The parameter name must be an exact match - it is case sensitive. The parameter value is case insensitive - it will match both "My Value" and "my value".
User attribute changesWhen a user attribute changes to any value or to a particular value.
User enters custom regionWhen a user travels into a specific geographic area. (Go to Custom Regions to define your regions.)
User exits custom regionWhen a user travels outside of a predefined geographic region.

Updated over 2 years ago

Next