Automatically collected events
Firebase collects these events by default.
Automatically collected events are triggered by basic interactions with your app. As long as you use the Firebase SDK, you don't need to write any additional code to collect these events. To see event reports, click Events in the report navigation in Google Analytics, or click the Events tab in the Firebase console.
| Event name | Triggered... |
|---|---|
| ad_click | when a user clicks an ad. |
| ad_exposure | when at least one ad served by the Mobile Ads SDK is on screen. |
| ad_impression | when a user sees an ad impression. |
| ad_query | when an ad request is made by the Mobile Ads SDK. |
| ad_reward | when a reward is granted by a rewarded ad served by the Mobile Ads SDK. |
| adunit_exposure | when an ad unit served by the Mobile Ads SDK is on screen. |
| app_clear_data | when the user resets/clears the app data, removing all settings and sign-in data. |
| app_exception | when the app crashes or throws an exception. |
| app_remove | when an application package is removed or "uninstalled" from an Android device. This event is different from the Daily uninstalls by device and Daily uninstalls by user metrics, which are both reported by Google Play Developer Console. 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 |
when 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. |
| dynamic_link_app_open | when a user re-opens the app via a dynamic link. |
| dynamic_link_app_update | when the app is updated to a new version and is opened via a dynamic link. Android apps only. |
| dynamic_link_first_open | when a user opens the app for the first time via a dynamic link. |
| first_open | the first time a user launches an app after installing or re-installing it. This event is not triggered when a user downloads the app onto a device, but instead when he or she first uses it. To see raw download numbers, look in Google Play Developer Console or in iTunesConnect. |
| in_app_purchase | when 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. To see in_app_purchase data for Android apps, you need to link Firebase to Google Play. This event is triggered only by versions of your app that include the Firebase SDK. Note: paid app-purchase revenue, subscription revenue (Android only), and refunds are not automatically tracked. Your reported revenue may differ from the values you see in the Google Play Developer Console. Events that are flagged as being invalid or as sandbox (test) are ignored. Only iOS events are flagged as sandbox. Learn more about testing Google Play billing. |
| notification_dismiss | when a user dismisses a notification sent by FCM. Android apps only. |
| notification_foreground | when a notification sent by FCM is received while the app is in the foreground. |
| notification_open | when a user opens a notification sent by FCM. |
| notification_receive | when a notification sent by FCM is received by a device when the app is in the background. Android apps only. |
| os_update | when the device operating system is updated to a new version. The previous operating system version id is passed as a parameter. |
| screen_view | when a screen transition occurs and any of the following criteria are met:
|
| session_start | when 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. |
Was this article helpful?
How can we improve it?