User Profiles is a tool which helps you identify users, their devices, event timeline and application crash information. User Profiles can contain any information that either you collect, or is collected automatically by Countly SDK. User properties can be anything that you want to collect, like phone number, gender, age, campaign, or information which can be tied to user or device. This page also has an event timeline showing what user has done historically in each session. Additionally, funnels inside User Profile show whether a specific funnel is passed by this user, or not.
Below you can watch an introduction video to User Profiles.
User Profiles is the best way to track custom information about your users individually.
User Profiles is available with Enterprise Edition, as a plugin. A server with this plugin always shows all basic user information, regardless of whether SDK sends extra custom data or not. Therefore if you have User Profiles, all you would be willing to do is to send custom attributes related to that user, if that's ever needed and required.
With User Profiles, it's possible to understand:
- When and where a user has logged in
- Which events a user has generated during a specific session
- Timeline of user (total sessions and total events per each day)
- What user did during each session
By default, data collected by User Profiles are always shown under "Anonymous" tab. If you send more data (e.g user name, demographic details etc) then these users will be shown under "Known" tab.
In order to know more about users, User Profiles keeps a list of all users in a table. By default, this table shows user's name and surname, device, total sessions, last seen and total time spent information. Click on a specific bar to sort the table with that feature.
If you want to see specific information about a user, click on a user's name. This will open another page, where you see detailed information about that user. Here you can see many boxes with different types of information in it. Below you can see detailed breakdown of those boxes which are located on the left hand side:
- User details & engagement: This box gives an overview of user location, country, user name and surname, last seen info, and avatar. Engagement gauge shows how loyal the user is, by computing how much he has returned back to the application.
- Custom properties: Any data sent alongside the standard data. This data can be in the form of key-value pair and may contain any type of data (e.g boolean, string, number etc)
- Currently affected crashes: This is the last crash this user has seen. Clicking on the crash will get you directly to the crash page.
How is user engagement score calculated?
On each user profile page, you will see a colorful bar that shows user engagement. It's calculated as follows:
- Score1: Average session duration in minutes, 1 point per minute up to 2 points as a maximum
- Score2: Amount of sessions in last week, 1 point per session up to 20 points as a maximum
- Score3: How many days did user use app in last 7 days, 1 point for each day up to 7 points as a maximum
Multiplication of these 3 scores shows user engagement score result. Maximum result is 280 points or 100% engagement.
On the right hand side, information boxes are grouped so that you can know what a user has been doing inside your app. At the top you see a timeline, where each session and event is recorded. Under that part, you see a session history. This session history keeps are record of all sessions of that user, giving information about session date, time and duration.
Session History, you can see
Event Timeline. When you click on a session entry under
Session History table, corresponding session events are shown in this
Event Timeline table. If a crash occurs, this crash information is also shown here, in addition to custom events.
User Profiles gives you detailed information whether user has passed a specific funnel or not. Previously, you should have defined this funnel in order to see it appear here. If the funnel is not completed, then in one of the funnel steps it says "Not Completed".
If you are a developer, sending data including user profiles is not hard. Each official SDK includes information on how to send user profile related data to Countly server. Click on this link for iOS example, and this link for Android example.
Note that you can take advantage of Facebook integration, using Facebook SDK. This helps you collect detailed user information and send it directly to Countly server.