Data in AppMetrica: overview
AppMetrica collects data about user actions, purchases, ad revenue, and app stability. Together with user and device characteristics, this data helps you analyze how people use the app and where problems occur.
Some data arrives after connecting the AppMetrica SDK — a library for collecting analytics in the app. The transfer of other data needs to be configured. For example, the SDK can record an app launch, but to track onboarding completion, the developer needs to add the sending of the corresponding events.
What data is available
| Data | What you can learn | How to start collecting |
|---|---|---|
| Installs and sessions First launch and subsequent app visits |
How many users open the app and how often they return | Ask the developer to connect analytics. Information about installs and sessions is collected automatically |
| User actions Screen opening, feature usage, scenario stage completion |
Which features are in demand and at which step users stop an action | Define the required events and configure their sending. Learn more — Custom events |
| Purchases and monetization Actions with products, purchases, subscriptions, and ad revenue |
What users buy and what income the app brings | Choose the appropriate event type: Ecommerce, In-App purchases and subscriptions, or Ad Revenue. Setup depends on the event type and platform |
| Users and devices Device and app characteristics, location, user attributes |
How user groups differ and on which devices they use the app | The SDK determines system characteristics automatically, taking into account settings and permissions. The transfer of your own user characteristics needs to be configured. Learn more — User profile and Determining the location |
| Crashes and errors Abnormal terminations and errors during app operation |
What failures occur and in which users | Crash collection is provided in the SDK. The developer configures the sending of custom error messages. For a clear description of a failure, the developer may upload additional files. Learn more — Crashes and errors |
User actions, changes in app operation, and other facts important for analytics are recorded as events. Additional information about an action is passed in event parameters. For example, a screen opening event can contain the name of that screen.
User characteristics are stored in the profile as attributes. For example, when a subscription is issued, its type can be passed in an event parameter — this way you save which subscription the user issued at that moment. The subscription type can also be passed to a profile attribute: the last passed value will be stored there. You can create segments based on profile attributes and compare user groups in reports.
How to transfer data
From the app via the SDK
The developer connects the AppMetrica SDK to the app and configures collection. The library transfers some data automatically. For actions specific to the app, the developer configures the sending of information at the moment of the required action.
Automatic collection doesn't mean that AppMetrica tracks every tap or screen opening. The set of collected data depends on the platform, SDK settings, and the logic added by the developer.
From the server via the Post API
The Post API allows you to send data via HTTP requests. This method is suitable if the information is available on your server, for example after payment confirmation.
If some actions are confirmed on the server, the developer links them to the same user in the app. This is needed to see their actions together.
For the developer: linking app and server data
Download the instructions for the developer (TXT): overview-developer-en.txt
To upload an event via the Post API, the corresponding identifier must have been previously transferred via the SDK. Before setup, check the supported data types and upload restrictions.
How data complements each other
Example: an app with a paid subscription
Session data can help you estimate how often users open the app. Onboarding events will help you find the stage where they stop. Subscription data — estimate payments and renewals, and profile attributes — compare users with different subscription types.
If some users encounter a failure, crash data will help you study the problem and see on which devices it occurs.
For such analysis, first determine which questions you want to check. Then choose the required data and configure its transfer.
Where to start setting up
- To analyze actions, study the event types and choose the appropriate markup method. For multi-step product scenarios, consider Product Flow.
- To compare users by their characteristics, set up user profiles.
- To track app stability, check the collection setup for crashes and errors.
After setup, make sure the data arrives in AppMetrica. The verification method is described in the instructions for the selected data type.
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.