What counts as an event in GA4?

Nearly everything: page views, scrolls, clicks, file downloads, video plays, session starts, and any custom event you define. GA4 replaced Universal Analytics' pageview/event/goal split with a single event-based model.

Is a high event count a good sign?

Not by itself. Event count is a volume metric, not an engagement or success metric — it can rise from auto-tracked events like scrolls and clicks without any real increase in meaningful visitor activity.

What's the difference between event count and key events?

Event count is the total volume of all events logged. Key events are the specific events you've manually flagged as meaningful business outcomes, like a purchase or signup — a small subset of total event count.

Why is event count so much higher than my session count?

Because multiple events fire within a single session — a single pageview alone can trigger a page_view event plus scroll and click events, so event count naturally dwarfs session count.

What Is Event Count in Google Analytics?

Event count in Google Analytics is the total number of events GA4 logged over a given period — and in GA4, almost everything is an event. A page view is an event. A scroll past 90% of the page is an event. A click, a file download, a video play: all events. That's why event count is usually the largest number on any GA4 report, and why it's a poor stand-in for anything resembling "how many people did something meaningful."

GA4's everything-is-an-event model

Universal Analytics, GA4's predecessor, split data into separate categories: pageviews, events, and goals were tracked and reported differently. GA4 collapsed all of that into a single model — every interaction, from loading a page to clicking a button, is recorded as an event with a name and optional parameters.

This is a structural choice, not just a naming change. It means the same underlying data type — the event — powers pageviews, engagement signals, custom tracking, and key events alike. Nothing is a fundamentally different kind of record; it's all events, some of which you've chosen to treat as more important than others.

What gets counted automatically

GA4 auto-collects a set of events without any extra configuration: page_view fires on every page load, session_start and first_visit mark the beginning of a session or a new user, and scroll fires when someone scrolls past 90% of a page. Click fires on outbound link clicks, file_download fires when a visitor downloads a file GA4 recognizes, and video_start, video_progress, and video_complete track embedded video engagement.

On top of these, you can add custom events for anything specific to your site — a form interaction, a product filter used, a calculator submitted — and any of these, automatic or custom, can also be marked as a key event. All of it, regardless of type, rolls into the same Event count metric.

Why a high event count isn't automatically good news

Event count is a volume metric — it tells you how much activity happened, not whether that activity meant anything. A site with a lot of scroll tracking and auto-fired engagement events will show a high event count even if very few visitors did anything you actually care about.

This is the core trap: it's tempting to treat a rising event count as a sign of growing engagement, but a code change that adds more auto-tracked events, or a traffic spike from bots, can inflate the number without any real change in visitor behavior.

Event count vs key events vs sessions

Event count measures volume. Key events measure meaningful action — the subset of events you've deliberately flagged as mattering to the business, like a purchase or a signup. A site can have millions of events and very few key events; that gap is normal and expected, not a red flag on its own.

Event count vs sessions is a similar story: many events happen within a single session. One visitor loading one page can generate a page_view, a scroll event, and two or three click events — five or six events from a single pageview, a single session, and a single person.

So a report showing "10,000 events" might represent far fewer real visits than the number suggests. If you want a rough sense of traffic, look at sessions or users, not event count.

FAQ

What counts as an event in GA4?: Nearly everything: page views, scrolls, clicks, file downloads, video plays, session starts, and any custom event you define. GA4 replaced Universal Analytics' pageview/event/goal split with a single event-based model.
Is a high event count a good sign?: Not by itself. Event count is a volume metric, not an engagement or success metric — it can rise from auto-tracked events like scrolls and clicks without any real increase in meaningful visitor activity.
What's the difference between event count and key events?: Event count is the total volume of all events logged. Key events are the specific events you've manually flagged as meaningful business outcomes, like a purchase or signup — a small subset of total event count.
Why is event count so much higher than my session count?: Because multiple events fire within a single session — a single pageview alone can trigger a page_view event plus scroll and click events, so event count naturally dwarfs session count.

If you're here because GA4 is confusing — that's why we built Gizmo.

A dead-simple, cookieless Google Analytics alternative. Free forever, 10k events/mo.

Try Gizmo free See the GA4 alternative