Events tracked automatically in Leanplum

Leanplum offers a range of messaging channels, and each message type generates default events you can use as trigger events, Analytics filters, metrics, and more. See below for details on all the default events tracked for messages and A/B tests.

For events that aren't tracked by default, developers can create custom events with a Leanplum.track call. Check out our developer docs for more information on tracking custom events.

You can also create visual events using a developer device and the Leanplum dashboard. See Visual Events for the full instructions.

Events tracked by default

To see formulas for how event-based metrics are calculated, like "Unique occurrences of event," see event glossary.

Push notifications
Event name Definition Timing
Sent number of push messages sent to users' devices Tracked when message is sent from server to user's device
Open number of push notifications tapped/opened Tracked when user taps notification
Bounce number of messages we were unable to deliver (due to a bad token or other delivery issues) Tracked after message send attempt fails
Held back message was eligible for delivery, but was held back because the message was disabled for that user's A/B test group Tracked at time message would have been sent, if it weren't disabled for the test group

 

Note: Webhook messages will only have a sent metric — no open or bounce metrics.

Calculated metrics

Metric Definition
Open per sent Occurrences of open divided by occurrences of sent (displayed as a percentage)
Bounce per sent Occurrences of bounce divided by occurrences of sent

 

In-app messages

Alert, Center Pop-up, Confirm, Interstitial, Push-ask-to-ask, and Newsfeed messages include some or all of these metrics by default, depending on the in-app message type.

Event name Definition Timing
View number of messages sent and displayed on users' devices Tracked when user sees message/ triggers the in-app to fire
Accept number of times "Accept" button was selected Tracked when users select the "Yes" button on a Confirm message
Held back message was eligible for delivery, but was held back because the message was disabled for that user's A/B test group Tracked at time message would have been sent, if it weren't disabled for the test group

 

Calculated metrics

Metric Definition
Accept per view number of accepts divided by number of views

 

Rich in-app messages

These templates (Banner, Rich Interstitial, Star Rating) must be activated by your CSM before they are available in your dashboard. Once you are whitelisted for Rich in-app messages, these messages track the following events.

Select Banner number of times banner was tapped Tracked when users tap banner message
Select button 1

number of times users selected button 1 (Rich interstitial only)

Tracked when users select button 1
Select button 2 number of times users selected button 2 (Rich interstitial only) Tracked when users select button 2
Submit number of times users selected Submit (Star rating only) Tracked when users select Submit
View number of messages displayed on user devices Tracked when message appears
Held back message was eligible for delivery, but was held back because the message was disabled for that user's A/B test group Tracked at time message would have been sent, if it weren't disabled for the test group

 

Calculated metrics

Metric Definition
Select button 1 per view number of selects divided by number of views 
Select button 2 per view number of selects divided by number of views

To see formulas for how event-based metrics are calculated, like "Unique occurrences of event," see event glossary.

Chained in-app messages and push notifications

Push notifications and some in-app messages have open actions. If you set the open action to open another message (sometimes referred to as "chaining" or "nesting" messages) the default events tracked for the Accept, decline, or open options will also be chained together along with the names of each message.

Event name Definition Timing
<Message 1 title> Accept, <Message 2 title> Accept 
(message names will appear instead of placeholders)
first and second messages accepted  Tracked after all chained messages are responded to
<Message 1 title> Accept, <Message 2 title> Cancel first message accepted, second canceled.  
<Message 1 title> Event,
<Message 2 title> Event etc.
   

 

Email

Email messages track some or all of the following metrics depending on configuration. 

Event name Definition Timing
Sent number of emails sent to a valid email address Tracked when email is sent
Open the total number of open occurrences — counts multiple opens of a single email by each user Tracked each time an email is opened
Unique open number of users who opened the email  
Click Number of clicks to the provided URL (typically the call to action button) Tracked when a link in the email is clicked on
Unique click Number of users who clicked the URL  
Dropped Number of sends that are bounces, unsubscribes, spam reports, or invalid email addresses Tracked when unsubscribe, bounce, or spam report occurs
Bounce number of confirmed failed sends Tracked when send fails
Unsubscribe number of unsubscribes generated by the email or campaign  Tracked when user unsubscribes using link at bottom of email
Held back message was eligible for delivery, but was held back because the message was disabled for that user's A/B test group Tracked at time message would have been sent, if it weren't disabled for the test group

 

Calculated metrics

Metric Definition
Open per sent  open occurrences divided by sent occurences
Unique open rate unique opens divided by sent occurrences (if users open a message more than once, this value may be more accurate than Open per sent)
Unique click rate Unique clicks divided by number of emails sent
Bounce per sent number of bounces divided by number of sends
Unsubscribe per sent number of unsubscribes divided by number of sends

Note that for emails, it's possible to have more opens than sends. This is because an email can be opened multiple times by a single user. The same goes for clicks — an email can have multiple different links, and users can click each link multiple times.

Campaigns

To track events for each individual message in a campaign, look at the analytics for the individual messages.

Event name Definition Timing
Enter number of times users entered the campaign Tracked when users enter campaign
Exit number of times users exited the campaign Tracked when users exit campaign

To see formulas for other metric calculations with events, like unique occurrences of event, see event glossary.

A/B tests
Event name Definition  Timing
Impression number of times impression criteria for test was met Tracked when users in test target reach the impression criteria

Custom Templates

All of the Leanplum in app message templates are open source within our SDK. You can modify any of Leanplum's existing templates or build your own from scratch to match the look and feel of your app. You can configure what events and metrics are tracked for your custom templates.

See customizing an out-of-the box message template or interpreting message metrics in raw data export for more information.


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