About events
AppMetrica collects basic data on app usage through different types of events. Most events are registered automatically. However, collecting data on some events requires a manual setup.
This data can help you understand what's happening within your app, for example, how often in-app purchases are made, how many users are active, and much more.
|
Event and its type |
Tracking |
Description |
Logs API/ Data Stream API |
Segmentation |
Reports |
|
Installations (basic) |
Auto |
Registered when the app is first started with AppMetrica initialized. |
Yes |
Yes |
|
|
Session start and end (basic) |
Auto |
App startup/shutdown with AppMetrica initialized. A session is considered new when the user returns to the app after a period that exceeds the specified timeout (Android, iOS). The end of the current session is registered when the next one starts. Used in reports to identify active users. |
Yes |
Yes, by session start within a specified period |
|
|
Deeplinks (basic) |
Auto / Custom |
App openings via deeplinks, including universal links. Used to track remarketing campaigns. |
Yes, in the Logs API |
Yes, via deeplinks (if they contain tracking parameters) |
|
|
Events (custom) |
Custom |
User actions specific to your app (for example, using a certain feature or switching to a certain screen). |
Yes |
Yes, by events, including their parameters |
|
|
Profile attributes (basic) |
Custom |
App user attributes, such as level achieved, loyalty program status, and internal ID. |
Yes, in the Logs API |
Yes |
|
|
In-app purchases (basic) |
Auto / Custom |
Events of in-app purchases that were made via the App Store / Google Play. |
Yes |
Yes |
|
|
Ad Revenue (basic) |
Custom |
Revenue from ad impressions received from a demand platform and provided for each impression (Impression Level Revenue Data). |
Yes |
Yes |
|
|
E-commerce (basic) |
Custom |
Events that track the product interaction cycle in e-commerce apps. |
Yes |
Planned |
|
|
In-app subscriptions (basic) |
Auto |
Data on subscription purchases and status changes made via the App Store or Google Play. |
No |
Yes |
|
|
Crashes (basic) |
Auto |
Crash events that enable tracking stability metrics, identifying problematic cross-sections, and configuring monitoring thresholds. Deobfuscation requires uploading mapping, SO, or dSYM files. |
Yes |
No |
|
|
Errors (basic) |
Custom |
Events that track the most frequent errors grouped by ID and stack trace. |
Yes |
No |
|
|
Push tokens (basic) |
Auto |
Events that contain a special device ID in Firebase Cloud Messaging (FCM), Apple Push Notification Service (APNS), and Huawei Messaging Service (HMS). Required for sending push notifications directly to systems without using the Push API. |
Yes |
No |
No |
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.