Automatically collected events are triggered by basic interactions with your app.
If you use the Google Mobile Ads SDK, you don't have to write any extra code to collect these events. Although some of these events may not be available in AdMob reporting, they will be available once you link to Firebase.
To review event reports in Firebase, click the Events tab in the Analytics dashboard of the Firebase console.
The following table lists the collected events, their triggers and parameters.
| Event name | Automatically triggered when | Parameters |
|---|---|---|
| ad_click | a user clicks an ad |
ad_event_id |
| ad_exposure | at least one ad served by the Mobile Ads SDK is on screen | firebase_screen, firebase_screen_id, firebase_screen_class, exposure_time |
| ad_impression | a user has an ad impression |
ad_event_id |
| ad_query | an ad request is made by the Mobile Ads SDK | ad_event_id |
| ad_reward | a reward is granted by a rewarded ad served by the Mobile Ads SDK | ad_unit_id, reward_type, reward_value |
| adunit_exposure | an ad unit served by the Mobile Ads SDK is on screen | firebase_screen, firebase_screen_id, firebase_screen_class, exposure_time |
| app_clear_data | the user resets/clears the app data, removing all settings and sign-in data | |
| app_exception | the app crashes or throws an exception | fatal, timestamp |
| app_remove |
an application package is removed or 'uninstalled' from an Android device Note: Android only The app_remove event counts the removal of application packages, regardless of the installation source, and the count changes depending on the date range you are using for the report. The Daily uninstalls by device and Daily uninstalls by user metrics count the removal of application packages only when they were installed from Google Play, and are reported on a daily basis. |
|
| app_update |
the app is updated to a new version and launched again The previous app version ID is passed as a parameter. This event is conceptually different from the Daily upgrades by device metric, which is reported by Google Play Developer Console. An upgrade refers to the updating of the application binary, whereas an app_update event is triggered upon the subsequent launch of the upgraded app. |
previous_app_version |
| first_open |
a user launches an app the first time after installing or re-installing it To review raw download numbers, check in Google Play Developer Console or in iTunesConnect. |
previous_gmp_app_id, updated_with_analytics, previous_first_open_count, system_app, system_app_update, deferred_analytics_collection, reset_analytics_cause |
| in_app_purchase |
a user completes an in-app purchase, including an initial subscription, that is processed by the App Store on iTunes or by Google Play The product ID, product name, currency and quantity are passed as parameters. For Android in_app_purchase events, link your app to Firebase and connect your app to Play. Note: Paid-app purchase revenue and refunds (iOS only) are not automatically tracked. |
product_id, price, value, currency, quantity, subscription, free_trial, introductory_price |
| os_update |
the device operating system is updated to a new version. The previous operating system version ID is passed as a parameter. |
previous_os_version |
| screen_view | a screen transition occurs and any of the following criteria are met:
|
firebase_screen, firebase_screen_class, firebase_screen_id, firebase_previous_screen, firebase_previous_class, firebase_previous_id |
| session_start | a user engages the app for more than the minimum session duration after a period of inactivity that exceeds the session timeout duration. | |
| user_engagement | periodically, while the app is in the foreground. | engagement_time_msec |