The following user targets can be used as filters in the Analytics dashboard.
This filter will match users based on the app version they are running on their device. You can use this filter with other Technology filters (like OS Name) to view data for specific Android versions or iOS versions.
|Previous event or state occurrence||Users that triggered a specific event after or between a specific time or range.|
|Non-paying Users||Users with zero or negative purchases (set by the Monetization event).|
|Paying Users||Users with positive purchases.|
|Lifetime Value||Users with x amount of lifetime purchases.|
As an example, if you want to view the user activity for all users who triggered a specific event one week ago, you can use the Previous event or state occurrence filter. Select the event, set the time operator to after and enter "1 week ago."
The Current User category is a collection of filters that will only match users based on their status at the moment you are pulling the report. This allows you to see analytics for users that match your filters at this moment.
All of the filters listed on this page are available as current user filters, as well as a few others:
- User Preferences: Filter data by the user's current marketing email preferences.
- User bucket: Filter data by the user's current user bucket.
- User ID: Filter data by the user's current user ID.
As an example, let's say you have a user attribute named "Loyalty Level" with possible values of "Bronze", "Silver", and "Gold" and you want to look at Daily Active User counts over a period of a week for users who are currently at "Silver" level. If you don’t use the Current User filter, the analytic report would include all users who were at "Silver" level at any point over that week, including those users that may have changed from "Silver" level to "Gold" or "Bronze".
Leveraging the Current User filter ensures that the analytics report will only include users who are at "Silver" level at the time that you run the report.
|First-time users||Users that have only a single session (which end with 30 minutes or more of inactivity).|
|Returning users||Users that have more than one session.|
|Number of prior sessions||Users that have n number of sessions.|
|Logged in users||Users that are logged in. If you pass a custom user ID to Leanplum, the user is considered to be logged in.|
|Logged out users||Users that are logged out.|
|Time of first run||Users that first ran the application at a certain time (a particular instant in time, not the entire day).|
|Minutes previously spent in app||User that have n number of minutes spent in the application.|
|City||Users in a specific city (based on their IP address).|
|Country||Users in a specific country (based on their IP address).|
|Language||Users with a specific language set on their device.|
|Locale||Users with a specific locale (language + country) set on their device.|
|Region||Users with a specific state or province.|
|Session start in user's timezone||Users that began their session at a certain time in their time zone.|
As an example, you can view data for all users that began a session in the past week by using the filter Session start in user's timezone with the is since operator and a value of one week ago.
|Device model||Users with a specific model of device.|
|OS name||Users with a specific operating system running on their device.|
|OS version||Users running a specific version of an operating system.|
|Browser name||Users running a specific internet browser (only available with HTML5 SDK).|
|Browser version||Users running a specific version of internet browser (only availble with HTML5 SDK).|
As an example, you can view data for all users running any version of iOS 9 by using two filters: OS Version and OS Name. Set the OS Version filter with an is between operator with 9.0 as the lower value and 10.0 as the higher. Then, add the OS Name filter with the is operator and iOS as the value.
The attribution details for a given user. This is provided through an integration with a 3rd party attribution provider who will pass us the user source details via a postback. If you work with a specific 3rd party and would like to know if we can integrate, please contact your CSM.
|Source publisher ID||Users acquired from a specific publisher, filtered by ID.|
|Source publisher||Users acquired from a specific publisher, filtered by name.|
|Source sub-publisher||Users acquired from a specific sub-publisher, filtered by name.|
|Source site||Users acquired from a specific site, filtered by url.|
|Source campaign||Users acquired from a specific campaign, filtered by campaign name.|
|Source ad group||Users acquired from a specific ad group, filtered by ad group name.|
|Source ad||Users acquired from a specific banner/ad, filtered by banner/ad name.|
You can filter data by any user attribute that you set via our SDK. If, for example, you set an attribute "gender", you could filter data by User attribute > gender > is > Male.