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.
Adding user properties to your user profiles can help you enrich your user information, segment your audience better, and hyper-personalize your messages. CleverTap provides different methods to update user profile properties. By leveraging these methods, businesses can effectively engage with users and drive growth. The following are the different ways to update user profile properties on the CleverTap dashboard:
- Update User Profile via SDK
- Update User Profile via API
- Upload CSV File
- Import User Profiles via SFTP
- Track an Event from the SDK
You can use the CleverTap SDK to update user profiles and enrich the profile further to send personalized campaigns. The
Onuserlogin method is used to identify individual users on a device. However, if additional user properties such as gender and date of birth are required, the profiles can be updated using the
For more information, refer to Update User Profile via SDK.
You can also update user profile properties using CleverTap's RESTful API. The API allows you to update user profiles and supports updates at scale. To do so, use the CleverTap API to update the user profile property. The CleverTap server receives the update and applies it to the respective user profile.
For more information, refer to Upload User Profile API.
This feature helps update user profile properties in bulk at once. CSV upload is a manual process that requires the user to upload the data directly from the local system to the CleverTap dashboard in CSV format.
To learn more, refer to CSV Upload.
With CleverTap's Imports via SFTP feature, you can update user profile properties by importing the file to the SFTP server. SFTP import is an automated process that helps update user profile properties at regular intervals, such as daily or weekly updates, without manual intervention.
To learn more, refer to Imports via SFTP.
With CleverTap events, you can track all individual actions users perform in your app or website. After the event is triggered, the user profile is automatically updated with the latest property value. The CleverTap server receives the event and updates the user profile property.
For more information, refer to Update User Profile.
CleverTap provides a test user profile feature to update the user profile to a test profile. This feature helps with the following:
- Test messages (including personalized messages) before sending them to the target audience
- Test user segmentation
To mark a particular user profile as a test profile:
- Select the required profile from the Find People page.
- Select Mark as test profile from the Profile page.
When we mark the user profile as a Test profile, the CleverTap server receives the event and updates the user profile with an additional property that is
ct_is_test_user with the value
ct_is_test_user property is of type String.
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.
Updated about 1 month ago