After integrating our SDK, the platform creates a user profile for each person who launches your app or visits your website.
A CleverTap user profile has a set of default fields, such as email, phone number, and language. You can also extend the default user profile by adding custom fields that are specific to your business.
Custom Profile Field Example
If you offer a subscription service in your app, you can create a custom profile field to track what type of plan the user purchased.
The benefit of adding more information to a CleverTap user profile means the ability to:
- Create a user segment for people who have a specific profile property you have defined, then build a campaign to engage with that segment.
- Personalize your campaign messaging with information.
- Personalize your app based on information from that person's CleverTap user profile.
A CleverTap user profile consists of three parts:
- Identifiers: Each user profile is given a unique CleverTap ID. You can also add other identifiers to recognize the user including email, phone number, Facebook ID, or your own custom identifier.
- Properties: This is information stored about the user such as age, gender, device, and location. You can also extend the default user profile by adding custom fields that are specific to your business.
- Events: This is a log of actions taken by a user in your app such as a product viewed, a video watched, or an item added to cart.
The CleverTap user profile type changes automatically depending on the information set in them. A user profile can only belong to one type.
- Anonymous: Anonymous profiles do not yet contain uniquely identifiable information about the user.
- Addressable: Addressable user profiles are reachable either via email or push notifications.
- Customer: When you record a purchase via the Charged event, that user will be marked as a Customer.
When tracking anonymous profiles, CleverTap tries to retain guest events as much as possible. The following scenarios explain how anonymous profiles are logged in the system.
Anonymous user X performs event A from desktop A > Logs in > Performs event B.
The same user now uses a separate browser and performs event A anonymously > Logs in (as the same user) > Performs event B. Event B will be mapped to this user X.
In scenario 2, all the events done before the user identifies themselves are mapped to an anonymous profile. All events post login is mapped to user X and is visible on the profile. As a best-case scenario, the platform shows all the events on the same user X except that any events done in an anonymous mode are shown in gray; these grayed-out events will not be considered for analytics or segmentation. The events before the login event will not be remapped to user X because they are done in an anonymous mode.
Since the user has performed the events anonymously, we consider this user as a different user, even though, this is mapped to an already existing identified profile.
You can update a user profile in two ways:
- Add information to a user profile through our SDKs.
- Add information to a user profile through our server-side APIs.
System user properties are user properties that are derived from the user information that is received from your application after you integrate our SDK.
Age: If the
DOBis available as a profile property, CleverTap automatically calculates the age for the user profile.
You can now create and target segments based on user age, such as all users between 25 to 30 years.
To look at a specific user's profile in the CleverTap dashboard:
- Navigate to the Segment tab.
- Click Find People.
- In the By identity box, search for a user by an identifier, such as email or a custom identifier you define. If you declare that Phone is your identity, you can also search by phone.
- On the Find People page, you can also search for users who match a specific set of criteria. This criteria can include actions taken, actions not taken, and profile properties.
Updated about a month ago