You can search for a specific user or filter your users in the Users tab. Once you’ve filtered a list of users, you can download the list as a CSV, view these users in Analytics, create a message that targets all matching users, or add these users to an A/B test.
Here you can use the same Add Segment menu found throughout Leanplum to filter and target users. See Building segments and targets for more on your segmentation options.
Once you select a filter, you'll see the number of users that match your segment, along with a list of some users in that segment. To see all the users in the segment, you can download a CSV of all matching users.
Each row in the user list shows the User ID, Last Device Used, last known Location, and Last Active time for a matching user. A DEV icon next to a user's profile indicates that this user is a developer device (note that this is different from a registered test device).
Once you create a list of users with the Add Segment dropdown, you can use the buttons at the bottom of the page to Send a message to these users or Create an A/B test for these users.
You can also Download a CSV of these users, or Analyze these users in Analytics using the buttons at the bottom of the Users page. Just create a filter or segment using the Add Segment dropdown to get started.
Click on a user from the list or search for a specific user ID, device ID, or push token to see a user's full profile. The User Profile contains metadata about the user, their device, their user attributes, and their event and message milestones within your app.
To find a specific user or user ID, see here.
This part of the profile shows all of the metadata associated with this user. You can also register or unregister a device as a test device here. Here is the metadata displayed by default:
The user ID. If you are passing a custom user ID, that will be used. If not, this will be the device ID.
Whether the user has a registered development device.
Leanplum account owner
If the device is a registered development device, the email address used for the Leanplum account of the user. If it is not, the value will be None.
Note: The Register as test device button will appear if the device is not a registered test device.
By default, IDFV for iOS and MD5 hash of the MAC address for Android.
The name of the device, taken from device settings.
The device model.
The device OS name.
The device OS version.
iOS push token
The iOS push token (iOS only).
iOS push token added
The timestamp of when the push token was added to Leanplum (iOS only).
iOS push token types
The types of pushes enabled on the device, includes Badges, Sounds, and Alerts (iOS only).
Android GCM registration ID
The Android GCM registration ID (Android only).
Android GCM registration ID added
The timestamp of when the registration ID was added to Leanplum (Android only).
The latest app version on the device.
2-letter country code (Determined by IP address geolocation).
States in United States, provinces in other countries (Determined by IP address geolocation).
City name (Determined by IP address geolocation). See Geofencing and location-based messaging for more on how we track location by default.
The profile also contains a Google Map showing the city center of the city the user was in when they started their latest session (not the specific location within the city).
A language ID and a region designator (based on a user's personal phone settings), separated by an underscore. Ex: If a user lives in the US but has their phone's language setting as Australian English, their locale will be "en-AUS_US."
Displays all user attribute names and values tied to the device (Only applies if user attributes are being sent).
Time spent in app
Total amount of time user has spent in the app.
Number of sessions
Total number of sessions a user has had.
Number of events
Total number of events a user has triggered.
Number of states
Total number of states a user has entered.
Timestamps related to the user’s behavior in the app, and to messages they have received. Not all events are included in the milestones. Possible milestones include:
- Install time (called “Created”)
- Last session start time (called “Last Session”)
- Time of first occurrence and last occurrence of a particular event (along with count of lifetime occurrences)
- Time of first instance and last instance of a particular message being sent
- Time of first instance and last instance of a particular message being viewed
- Time of first instance and last instance of a particular message being opened
A list of all active A/B tests and which variants the user is in. To the right of the device model is a list of all variants the user is in for every active A/B test. A checkmark in the bubble indicates which variants they belong to. Clicking on one of the empty circles will force-assign the user to that variant.