This same functionality is also available in Google Analytics 4 properties. Learn more
In this article:

Analytics makes recommendations of additional events you can collect based on your app category in the Google Play Store and in the iOS App Store (e.g., ecommerce, travel, games). The recommendations appear at the top of the Events table.

Analytics displays three recommendations by default. To see additional recommendations, click Show All.

To open the related help-center documentation, click an event name.

To display the code snippet to collect an event, click in the row for that event.

To permanently dismiss all visible recommendations, click Delete to the right of Recommendations.

To dismiss an individual recommendation, hover over the event name, and click Delete.

Learn more about the events that Analytics recommends for different business types.

Summary table

The table lists the events that were triggered in your app during your active date range.

The table shows the following metrics for each event:

  • Count: number of times the event was triggered
  • Users: number of users who triggered the event

Click an event in the table to see a detail report for that event. The information in each detail report varies according to the event.

Event metrics

The following metrics are provided for each event:

  • Event count: number of times the event was triggered
  • Users: number of users who triggered the event
  • Count per user: average number of times per user that the event was triggered
  • Value: sum of all VALUE parameters supplied with the event. Use this context-sensitive metric to track any data that is valuable to your app (e.g., revenue, time, distance).

The metrics reflect different information depending on the event. For example, Event count for first_open indicates the number of times the app was opened for the first time, while Event count for in_app_purchase indicates the number of times an in-app purchase occurred in the app.

Learn more about the events and their associated metrics.

Enable events as conversions

Conversions are your most important events. By designating an event as a conversion, you facilitate attribution reporting and postback capacity for that event. Additionally, conversion events are uploaded immediately by the SDK in order to make them actionable more quickly.

You may add up to 30 events per project as conversions, in addition to the five default conversions (first_open, in_app_purchase, app_store_subscription_convert, app_store_subscription_renew, and purchase).

To designate an event as a conversion:

  1. In Firebase, open your project.
  2. Click Events, then click Network Settings.
  3. In the row for the event, turn on the switch in the Mark as conversion column.

Once an event has been enabled as a conversion, it is available in ATTRIBUTION > CONVERSION EVENTS. Attribution reporting begins for that event at the time you enable it as a conversion.

You cannot designate the ad_click and ad_impression events as conversions.

To see Google Ads-attributed Conversion Events in your Google Ads attribution reports, link your Firebase project to Google Ads, and then import the Analytics Conversion Events to Google Ads (Tools > Conversions > Firebase).

Note: The VALUE event parameter supplied with conversion events must be a number, and it must be accompanied by a currency code.
Was this helpful?
How can we improve it?
Clear search
Close search
Google apps
Main menu
Search Help Center