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 |
Event verification
Warning
Verification is only available on Android.
Each app is signed with a unique developer signature represented as a certificate fingerprint. All events sent from the app to AppMetrica servers come with this fingerprint.
If there's no fingerprint or it isn't the expected one, your app data received by AppMetrica may be distorted.
To identify these potentially fraudulent actions, AppMetrica offers the certificate_verification_status parameter within the Data Stream API. This parameter returns the result of matching the target certificate footprint with the certificate footprint that came with the event.
Warning
A valid signature doesn't guarantee that the event is authentic.
How to enable
-
Get the SHA1 fingerprint of the certificate from your app development team.
-
Upload the fingerprint via the API: Uploading an app certificate fingerprint.
-
Shortly after the upload is complete, AppMetrica will begin validating the data coming from your app to its servers against the uploaded certificate.
-
When exporting data from the Data Stream API, add the
certificate_verification_statusfield that will contain the verification result.
Managing certificate fingerprints:
- Information about app certificate fingerprints
- Uploading app certificate fingerprints
- Deleting app certificate fingerprints
FAQ
What if I have more than one certificate?
Upload all the certificates used by your app.
Do I need to tag anything else in the app code?
No, the fingerprints will be automatically sent to the server along with all types of events as soon as you upload the target certificates via the API.
Can I see the validation result in reports?
No, at the moment the validation result is only available over the Data Stream API in the certificate_verification_status field.
Will this field be added to the Logs API?
This field is only available in the Data Stream API.
Where can I share my ideas and suggestions?
Please share them using the form.
See also
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.