Link your apps to Firebase

Automatically collected events

Automatically collected events are triggered by basic interactions with your app. As long as you use the Google Mobile Ads SDK, you don't need to write any additional code to collect these events. While some of these events may not be visible in AdMob reporting, they will be available upon linking to Firebase. To see event reports in Firebase, click the Events tab in the Analytics dashboard of the Firebase console.

The Google Mobile Ads SDK collects these events for Android and iOS apps unless otherwise stated.
 

Event name Automatically triggered Parameters
ad_click when a user clicks an ad
 
ad_event_id
ad_exposure when 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 when a user sees an ad impression
 
ad_event_id
ad_query when an ad request is made by the Mobile Ads SDK ad_event_id
ad_reward when a reward is granted by a rewarded ad served by the Mobile Ads SDK ad_unit_id, reward_type, reward_value
adunit_exposure when 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 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 fatal, timestamp
app_remove

when an application package is removed or "uninstalled" from an Android device

Android only

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.

previous_app_version
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.
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

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.

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

when 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 when a screen transition occurs and any of the following criteria are met:
  • The new screen-class name differs from the previous screen-class name
  • The new screen id differs from the previous screen id
firebase_screen, firebase_screen_class, firebase_screen_id, firebase_previous_screen, firebase_previous_class, firebase_previous_id
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. engagement_time_msec
Was this helpful?
How can we improve it?

Need more help?

Sign in for additional support options to quickly solve your issue