About events
Events are information about user interactions with the app. All AppMetrica analytics are based on events: reports, funnels, segments, and cohorts. You can work with events in the account interface or download them via the API.
Events are divided into two categories: basic and custom.
Basic events
Basic events are a standard set of events AppMetrica: installs, sessions, purchases, subscriptions, crashes, and more. The full list is in the tables below.
Basic event features:
- Some events are collected automatically, while others need to be configured.
- The number of events is unlimited and not billed.
- Most built‑in reports are based on basic events.
Automatic collection
AppMetrica automatically collects events from this table after the SDK is installed.
|
Event |
What it records |
Which reports track this |
|
Installs |
First app launch after AppMetrica has been initialized. |
You can create segments. |
|
Session starts and ends |
App launches and exits. A session is considered new if the user returns to the app after the specified timeout (Android, iOS). The end of the current session is recorded when the next session starts. Used in reports to identify active users. |
You can build segments based on session starts within a specified period. |
|
App openings via deeplinks, including universal links. Used to track remarketing campaigns. |
You can build segments if deeplinks contain tracking parameters. |
|
|
In-app purchases1, 2 |
In-app purchases made via the App Store or Google Play. |
You can create segments. |
|
Creating and changing the status of subscriptions purchased through the App Store or Google Play. |
You can create segments. |
|
|
App crashes. Allow you to track stability metrics, identify problematic segments, and set monitoring thresholds. Deobfuscation requires uploading mapping, SO, or dSYM files. |
||
|
Push tokens |
Device identifiers in messaging systems: Firebase Cloud Messaging (FCM), Apple Push Notification service (APNs), and Huawei Messaging Service (HMS). Required to send push notifications directly without using the Push API. |
— |
Custom collection
To collect these events, configure event transmission in the app code.
|
Event |
What it records |
Which reports track this |
|
App user attributes, such as level reached, loyalty program status, and internal ID. |
You can create segments. |
|
|
The most common errors, grouped by ID and stack trace. |
Custom collection: conversions
Events for tracking revenue and conversion scenarios. To collect them, configure event transmission in the app code.
|
Event |
What it records |
Which reports track this |
|
Revenue from ad impressions received from the monetizer for each impression (Impression Level Revenue Data). |
You can create segments. |
|
|
Applications and multi-step product and service setup scenarios. |
||
|
The cycle of interactions with products in e-commerce apps. |
Segment building is planned. |
|
|
In-app purchases paid outside the App Store or Google Play. |
You can create segments. |
|
|
Subscription creation and status changes (sent via the Post API). |
You can create segments. |
Custom events
Custom events (client-side or user-defined) are events you create to track app-specific logic: using a feature, completing a level, or tapping a button. You send them from the app code.
Features of custom events:
- Configured manually via the SDK2
- 100 million events per month are collected for free
- Events exceeding the limit are charged For more information, see the section Pricing plans in USD and AED.
|
Event |
What it records |
Which reports track this |
|
User actions specific to your app, such as using a feature or navigating to a specific screen. |
You can build segments based on events, including their parameters. |
Learn more
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.
You can disable automatic collection and configure event transmission manually.
Events can be sent via the Post API.