Events

This help center article is part of the App + Web Property Beta.

App + Web properties are not currently supported in the Analytics app.

Event recommendations

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.

Currently, these recommendations are only for app events.

Analytics displays three recommendations by default, at the top of the Events table.

Click All Events in the left pane to open the Events table. To see additional recommendations, click Show All.

To open the related help-center documentation, click the Recommended Event chip.

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.

See the other articles in this section to learn more about the events that Analytics recommends for different business types.

To learn how to implement events, refer to the developer documentation

The All events report

To see information about the events you collect, click All events in the left pane.

Summary table

The table lists the events that were triggered in your app during the 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.

If you are collecting custom parameters with your events, and you have registered those parameters, the number of parameters is listed next to the event name. Click the arrow next to the event name to see the parameters.

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.

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 property as conversions, in addition to the three default conversions (first_open, in_app_purchase, and ecommerce_purchase).

To enable an event as a conversion:

  1. Click All events.
  2. In the row for the event, turn on the switch in the Mark as conversion column.

Once you enable an event as a conversion, it is available in Conversions. Attribution reporting begins for that event at the time you enable it as a conversion. Click an event to see the report for that event.

You cannot designate the ad_click and ad_impression events as conversions.

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?