Allows you to give another user access to your app statistics. For more information, see the section Managing app access.
For device identification, the AppMetrica SDK uses various types of identifiers available in the system depending on the platform, or combines them for increased accuracy. For this purpose, the Google AID is collected on Android devices, and the Apple IDFA and IV are collected on iOS devices.
An advertising ID that is assigned by Google Play services. The advertiser can use it to identify a unique user, display targeted ads, and track the number of click-throughs from an ad to a website. If desired, the user can reset the ID or disable ad personalization.
Allows you to group users by the app install date and track changes over time for each cohort in the percentage of users who return to the app, or the percentage of users who complete a target event (event conversion). You can also compare these cohorts with each other. For more information, see Cohort analysis.
A user who installed and launched the app at least once during the selected time period. If a user performed multiple installations during this period, only the first installation is counted. If a user removed the app and then re-installed it, this user is considered a new user.
Controls the accuracy of report data. If generating a report requires a large amount of data, collecting this information might take a long time. In order to generate the report faster, the service can use just part of the data (for example, 10%). You can control sampling manually.
A session of the user interacting with the app. The session starts when the app is opened, and ends when the app is closed, a new session is force started, the app crashes, or the user is inactive for a prolonged period (session timeout). By default, the timeout is 10 seconds. You can change this value by calling the setSessionTimeout method in the SDK API.
You can use the AppMetrica SDK to transmit event messages and events with additional parameters.
You can pass any JSON data structure for calculations:
A container with URLs and settings for tracking and collecting statistics about app installs via partners as part of an ad campaign. You can set the destination URL, deeplink, or post-click landing and get a tracking URL. When users go to this URL (and then install or open the app), it is reflected in the report.
A link for sending an event message (about an install or a target event). The event recipient is a partner. You can send additional parameters to the postback URL.
A GET request to the specified URL (the postback URL), which certain parameters can be sent to. You can add up to 5 requests per campaign. More information about the postback policy.
The percentage of users who installed the app during a given day, week, or month (the reference period) and then returned to the app (opened it) on a specific day, week, or month after installing.
This metric is calculated as the ratio of the number of users running the app during the Nth day, week, or month to the number of users who installed the app in the reference period (this number is taken as 100%).
The percentage of users who installed the app during a given day, week, or month (the reference period) and then returned to the app during a specific day, week, or month, assuming they could have potentially returned during the preceding time period. These users are not interpreted as lost (inactive) until the last time they start the app.
To better understand how Rolling Retention works, imagine a user who first opened the app on the day of installation (the reference day), and next opened it on the fourth day after installing. This user is counted as active on the fourth day and for all the previous days, as well. Even though it took the user four days to come back to the app, this was always a possibility during that time.
The page that will be opened in the user's browser after clicking the link to install the app. You can enter it when you configure the tracker.
A link in the format https://appmetriсa.yandex.com/serve/* that takes the user to the app store for installing the app. If the app is already installed, it opens the app (if a deeplink is specified). Created when setting up the tracker. For more information about tracking, see What is tracking?.
* To view the sample report, you need to get demo access.