Exporting Leanplum in-app message events to other analytics providers

This guide describes different methods to export Leanplum In-app message events to other analytics providers. The events will be exported on a per-user basis (as identified by their user id on Leanplum) so that you will be able to carry out analysis on your users on your Provider.

For in-app messages, there are two kinds of messaging events to track: Views and Accepts.

Method 1: Track in the app

Modify the Leanplum in-app message templates to send tracking events via your Provider's SDK whenever a user opens an in-app message or clicks a call-to-action.

Method 2: exportUsers

This method is suitable if you need to export data on messaging campaigns after the campaign is completed, or at a specific point during the campaign's life.

You can run an API query to export the list of users who have been sent a particular message.

For example, to see a list of all users who have been served in-app Message ID 5181850935361536:

  1. Create an Audience in the Dashboard segmenting the users who have viewed the above message.
  2. Prepare and run the API request below, which would return the list of all users who accepted Message ID 5181850935361536 to date:
  3. The response will return a jobId which you could use to run the getExportResults method and obtain the CSV file with the data.

See more on exportUsers.

Method 3: exportData

You can use exportData to continuously export all Leanplum raw data in JSON format. This gives you maximum flexibility, as the data will contain all event and messaging data for all of your users. You may need resources from your data warehouse team to ingest and process the raw data, and then upload to your Provider.

The raw data can be pulled from Leanplum using the exportData API call, or you can configure Leanplum to automatically push the raw data to an AWS S3 bucket of your choice.

See more on exportData.