The data you see in your Google Analytics 4 reports comes from events that are triggered as users interact with your website and/or app. For example, a
page_view event is triggered each time a user views a page on your website. The All events report, described below, shows how many times
page_view and other events were triggered.
Many events (including
page_view) can be collected without you adding code. These events may be sufficient for your needs.
- Automatically collected events are collected automatically with basic data collection.
- Enhanced measurement events are collected automatically if you have enabled enhanced measurement. You can enable/disable the collection of individual enhanced measurement events via the Admin page within your Google Analytics 4 property.
However, if you have more advanced data collection needs, you can add code to collect additional events.
- Recommended events are events that you implement yourself, but that have Google-predefined names and parameters. Recommended events unlock existing and future reporting capabilities not available for custom events (events that you name yourself). Here are the events recommended for all properties, Retail/Ecommerce , Jobs/Education/Real estate, Travel, and Games.
- Custom events are events that you name and implement yourself. Before implementing a custom event, check that there is not an automatic, enhanced measurement, or recommended event that already provides what you need. Learn how to implement custom events for web and app.
All events report
Click All events in the left reporting pane. The table lists the events that were triggered in your app during the active date range.
- Count is the number of times the event was triggered
- Users is the 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.
- Count per user is the average number of times per user that the event was triggered
- Value is the sum of any revenue, time, distance etc value parameters supplied with the event.
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.