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.

Most campaigns are designed to drive some specific behavior, like making a purchase or getting users to return to your app. The Goal tab is where you choose your goals and conversion settings for every campaign.

Goal categories

The Goal category helps you organize your campaigns in the overview table. When setting up your campaign, choose a category that aligns best with your end goal for this specific campaign.

Goal

Description

Examples

Notify

Make a general announcement.

  • New feature announcements
  • Technical alerts (such as scheduled downtime)
  • Email newsletters
  • Simple greetings

Onboard

Onboard new users to your app.

  • Drip campaign to explain features of the app
  • In-app product walkthrough
  • Reminder for users who didn’t complete the registration process

Engage

Increase app usage.

  • Promotion of new content such as movies or music
  • Announcements for a daily tournament
  • Notification of new dating matches or nearby restaurants

Monetize

Drive purchases.

  • Shopping cart abandonment campaigns
  • Sales or limited-time promotions
  • Promotion of paid features to free users

Re-Engage

Get lapsed users back into the app.

  • Special offers for users who have not recently used app
  • Communicating new app features to users who have not recently logged in
  • Reminders about music a user favorited for users who have not recently used app

Other

Drive other behavior, unrelated to purchases or re-engagement.

  • Campaign to drive push notifications opt-in
  • Email subscriptions, etc.
  • Campaign to increase social sharing about the product
  • Drive more app store ratings
  • Survey to collect NPS score from users

📘

Filter by Goal Category in the Campaign Overview page

To view all campaigns that share a similar goal, you can filter by Goal Category by clicking the settings icon at the top right corner of the screen.

Conversion events

The conversion event is the user behavior you want your campaign to drive. If the user converts, you know the campaign was successful. For example, if your campaign's goal is to "monetize," then your conversion event could be when a user completes your Purchase Event.

Users can convert at any point during the campaign or Attribution window. Your campaign's analytics tracks every conversion event metric.

Possible Conversion events include:

  • User first starts app, User starts or resumes app
  • User triggers event, User triggers event when parameter value is X
  • User advances to state, State triggers when parameter value is X
  • User attribute changes, User attribute changes to X value, User attribute change from X to Y value
  • Custom events that you track in Leanplum

When a user completes the conversion event, they are exited from the campaign and don't receive any further actions. (However, users can re-enter the campaign if they complete the entry trigger again.)

Attribution window

When a user receives the last action they're eligible for in a campaign, the Attribution window determines how long afterward you can count their activity toward your campaign's conversion metrics.

Users cannot re-enter the campaign again until the Attribution window ends for them.

The Attribution window begins when a user receives the final action or message for them in the campaign (i.e., there are no more messages or actions that particular user can receive).

It could be a user's final action for any reason:

  • They reached the last action in the entire campaign.
  • The user's target status disqualified them from all remaining messages.
  • They missed a previous action. (To receive an action, a user must have received all preceding actions in a chain.)

The Attribution window ends

  • When a user performs your Conversion event in a single conversion campaign.
  • When the user reaches an Exit action.
  • When the user has no additional actions scheduled and the Attribution window expires.

📘

Users can re-enter a campaign multiple times, but only after they finish both the campaign and the Attribution window. To prevent campaign re-entry, you can set an Entry Limit of one entry per user.

Examples
We'll assume there's a 7-day Attribution Window:

  • A user receives the last action in the campaign, and 3 days later they complete the conversion event. This user counts towards your campaign’s conversion metrics.

  • A user receives the last action in the campaign, then 8 days later they perform the conversion event. This user does not count as a conversion in your campaign's analytics.

  • A user receives the first action in the campaign but doesn’t qualify for any of the following actions. That user has 7 days from the first action (their last interaction with the campaign) to perform the conversion event and count as a campaign conversion.

  • A user receives a message from your campaign on Tuesday, then the Campaign's End date passes on Thursday. The user has until the following Tuesday (seven days after their last campaign interaction) to convert and count towards your campaign's conversion metric.

Updated 3 months ago


Goal


Suggested Edits are limited on API Reference Pages

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