User profiles
A profile contains the characteristics of an app user — attributes. You can analyze them in the profile report and use them for segmenting other reports.
Warning
For example, an event records a subscription issuance, while a profile attribute stores its current type. When a new attribute value is transferred, the previous one is replaced. The profile doesn't replace the event history.
What attributes exist
|
Attributes |
How they appear |
|
System |
The SDK determines information about the device, app, and other system characteristics |
|
Predefined custom |
The developer configures the transfer of supported attributes, for example age or notification permission status |
|
Custom |
You create an attribute in the console and configure the sending of its values, for example subscription type or loyalty level |
How to set up a profile
- Determine which user characteristics are needed for analysis: for example, subscription type or loyalty level.
- For each characteristic, describe the possible values and the update moment.
- Create custom attributes in the Settings → Profile attributes section: set the name and type, then click Add. This step isn't needed for already provided attributes.
- Pass the description to the developer and agree on how to identify the user. A new custom attribute can be transferred about 30 minutes after creation.
Warning
Don't transfer confidential user information.
How to check the result
Open the test profile card and check the identifier and attribute values. Change the test attribute and make sure the value is updated. Then check the grouping in the profile report.
If the characteristics didn't appear, ask the developer to check the link with the profile and the transfer of values. For a custom attribute, also make sure it's created in the console.
Learn more
Attributes are user characteristics. The developer links them to the required profile and configures updates so that reports show current values.
For the developer: profile identifier and attributes
Download the instructions for the developer (TXT): profiles-developer-en.txt
Custom profile attributes
Custom attributes are divided into predefined and custom ones. To collect them, you need to configure sending in the AppMetrica SDK.
Predefined attributes
Attributes that are typical for users of any app and are supported in the AppMetrica SDK in advance:
ProfileId
User profile identifier. Accepts an arbitrary string value. If ProfileId sending isn't configured, predefined attributes aren't displayed in the AppMetrica web interface.
Gender
User profile gender. Possible values: male, female, other.
Age
User profile date of birth or age.
Push enabled
User profile notification status. The status indicates whether the user has allowed receiving notifications.
Name
User profile name. AppMetrica also has system Gender and Age, which are determined automatically using the Crypta technology.
To collect predefined profile attributes, you need to configure their sending in the AppMetrica SDK. Learn more in the Configuring profile attribute sending section.
Custom attributes
Attributes that aren't supported in advance and may differ for different app types. The name and type of custom attributes are set manually in the app settings.
AppMetrica allows you to configure sending of up to 100 custom attributes of the following types:
String
Accepts an arbitrary string value. For example, subscription type: Free, Trial, Premium.
Number
Accepts a numeric value. For example, the number of widgets on the screen: 1, 2, 3, 4.
Bool
Accepts a binary logic value. For example, the presence of a paid subscription: true, false.
Counter
Set by an addition or subtraction operation. For example, the number of completed levels: +1.
To collect custom profile attributes, you need to add them in the app settings and configure their sending in the AppMetrica SDK. Learn more in the Configuring profile attribute sending section.
How to configure attribute sending
- Define the identifier. Configure the transfer of
ProfileIdin the SDK. If the identifier appears only after library initialization, a technical profile may remain and a new profile with the transferred ID may appear. Learn more — about profile identifiers. - Create custom attributes. Open Settings → Profile attributes, specify the name and type, and click Add. This step isn't needed for predefined attributes.
- Configure sending. Pass the developer the names, types, and update conditions. A new custom attribute can be transferred about 30 minutes after creation in the console.
For the developer: sending attributes
If you didn't find the answer you were looking for, you can use the feedback form to submit your question. Please describe the problem in as much detail as possible. Attach a screenshot if possible.