Guide 58 · Reports · GA4 + Tag Manager
Read the Events report: which events fire, how often, and for how many people
The Events report lists every event by count and by users. Read count beside users — a high count with few users is one person firing it over and over.
After step 5, you can name the top five events by count, the events with the widest user reach, and any event whose count jumped without its user count moving.
Download the report reference: the Events reference (JSON) (1419 bytes, MD5 d44e433aab0eb1bd3d6f33727bd87227). It holds the report or exploration definition and the worked example with the recomputed figures shown on this page.
What you need
- Viewer access or above on the property.
- The report path: Reports, then Engagement, then Events.
- The event names your site actually sends — page_view, scroll, click, and any custom event names from your tag setup. Without the names, the table is a list of strangers.
The trace
- Open the report. Sign in, click Reports, then Engagement, then Events. The table lists one row per event name, ranked by event count by default.
- Read event count beside total users for every row you quote. Event count is firings; total users is people. Divide the two in your head, or read the recomputed example below: a ratio near one means the event fires once per person, a ratio of ten means a small group fires it repeatedly.
- Check total revenue on the events that should carry it. Scroll right to the revenue columns. A purchase event with no revenue column filled means the event arrived without its value parameter, which is a tagging fault, not a reporting fault. The event itself is fine; its parameters are not.
- Search for one event before you change the sort. Use the search bar above the table to find a single event name. The search filters in place; changing the sort first re-orders the table and costs you the row.
- Confirm a new event in Realtime or DebugView, not here. Standard reports can take 24 to 48 hours to process data. An event added today belongs in Realtime or DebugView for its first check; it will appear in this report tomorrow at the earliest.
Dead ends
DEAD END — READING EVENT COUNT AS USER COUNT. A scroll event firing 40,000 times for 800 users is normal behaviour. Treating the count as 40,000 people is a forty-fold error.
DEAD END — EXPECTING TODAY'S EVENT IN THIS REPORT. The 24 to 48 hour processing lag means a new event is invisible here on day one. Its absence today proves nothing about the tag.
DEAD END — READING A PURCHASE EVENT WITHOUT ITS REVENUE. A purchase row with zero revenue is a parameter problem in the tag, not a zero-sales day. Check the event's value and currency parameters before you report the revenue.
End state
The Events report answers what happened, and for how many people. The worked example below recomputes the per-user firing ratio for three events, so a high count can be checked against its reach.
Worked example — stated inputs, recomputed results. The events below are stated inputs for the example. Every rate in the table was recomputed from them.
| Row | Sessions | Engaged sessions | Engagement rate | Key events | Key event rate | Revenue |
|---|---|---|---|---|---|---|
| page_view | 5,210 | 3,126 | 60.0% | 0 | 0.0% | $0.00 |
| scroll | 3,840 | 768 | 20.0% | 0 | 0.0% | $0.00 |
| purchase | 96 | 88 | 91.7% | 96 | 100.0% | $7,420.50 |
| Total | 9,146 | 3,982 | 43.5% | 96 | 1.0% | $7,420.50 |
Revenue per session is $7,420.50 ÷ 9,146 sessions = $0.81. Engagement rate is 3,982 ÷ 9,146 = 43.5%.
Sources
- Analytics Help — Confirm that you are collecting data — many reports and explorations can take 24 to 48 hours to process data; Realtime and DebugView confirm collection sooner
- Analytics Help — [GA4] Traffic acquisition report — detail reports group data by dimensions; the search bar above the table finds one row
Checked 11 November 2026. The click paths above are the ones in Google's help pages, opened or read 11 November 2026 (the Explorations and detail-report pages were opened in full; the report, library, navigation and thresholds pages were read from Google's help results the same day, after the browser hit a rate limit). No step in this guide was run inside a live Analytics property, because that needs a Google sign-in and this site does not sign in as anyone. The worked-example figures on this page were recomputed in Python with decimal arithmetic, and the downloadable JSON file carries the same recomputed figures. Google moves menu items without warning; if a path on this page no longer matches, the linked help page is the current map.