GA4 Events vs Sessions — What Each One Counts and Why They Differ

"What is the GA4 event count?" "How is it different from the session count?"

These are the most common mix-ups I hear from people starting with GA4. Both are "counting something," but they mean different things, are calculated differently, and are used for different decisions.

This article walks through what events and sessions actually count in GA4, how every behavior gets recorded as an event under GA4's event-based design, and which metric to look at in which scenario.

TL;DR

• Event count = +1 per user action / Session count = number of session_start event fires — page views, scrolls, clicks are each one event; each visit is one session
• In GA4, sessions and PVs are both recorded as "events" — every behavior lives in the same box called "event," which is why event count is typically larger than session count
• Use sessions for traffic analysis, events for behavior analysis — "where they came from" → sessions; "what they did" → events; conversions are tracked as specific event types

1. GA4 events vs sessions — what is the difference

Event count is the total of every "1 user action = 1 event" recorded in GA4. Page loads, scrolls, link clicks, add-to-cart actions — every behavior is recorded as an event.

The five most common automatic events are page_view, scroll (90% scroll depth), click (outbound link click), first_visit, and session_start (visit start).

Session count, on the other hand, is the count of "1 session = one continuous interaction" from arrival to leaving. In GA4, the session count goes up by 1 every time a session_start event fires.

Session-end conditions:

• 30 minutes of inactivity ends the session automatically
• A new day (midnight) starts a fresh session
• Closing the browser ends the session

The relationship is session = container, event = content. Multiple events fit inside one session — when a user arrives (session_start), views a page (page_view), and scrolls (scroll), all of those events are bundled into one session.

"Session count = visitor count" is wrong. The same person visiting 5 times a day creates 5 sessions, not 1. Visitor count (UU) is a separate metric.

2. Everything in GA4 is an event — why the numbers diverge

The most important thing to grasp about GA4 is the design principle: every behavior is recorded as an event. Page views, add-to-cart actions, even arriving on the site (session start) — all of them are stored in a common box called "event."

Session counts and PV counts are both, at the lowest level, just "the count of how often a specific event fired." Session count = session_start fire count, PV = page_view fire count, and so on. Sessions themselves are treated as a kind of event under this design.

The reason event count and session count differ is simple: multiple events fire inside one session. Here is a concrete example.

For 1 user with 3 visits, 5 page views, and 1 add-to-cart, the totals come to 9 events / 3 sessions. Event count is much larger, which is why the inequality "sessions ≤ events" always holds.

In real EC sites, 5–10 events per session is typical, and product-browse → add-to-cart → checkout flows can hit 15–20 events per session.

3. Which metric to look at — usage guide by scenario

Whether to look at events or sessions depends on what you want to know.

The shortlist:

• Traffic analysis (where from) → Sessions. Check via "Acquisition → Traffic acquisition" by source / medium
• Behavior analysis (what they did) → Events. Check via "Engagement → Events" sorted by fire count
• Conversions → Events (= conversion events). Set purchase or sign_up as conversion events and check via the Conversions report

The rule of thumb: traffic = sessions, behavior = events. Memorize this and you'll know which GA4 screen to open without thinking. To count users (how many people came), look at neither sessions nor events but "Active users" (= UU).

Wrap-up

The GA4 mental model is simple once you internalize the design: everything is an event. Sessions and PVs are just specialized aggregations of specific event types (session_start and page_view respectively). Once that clicks, "why are these numbers different?" stops being a confusing question and starts being an obvious one.

The next time you open GA4, ask yourself "is this a traffic question or a behavior question?" If traffic, find the sessions metric. If behavior, find the events metric. That single mental flip resolves 80% of "which number am I supposed to look at?" confusion.

Question for you

How do you decide between events and sessions in your weekly GA4 reports? Do you treat conversion events as a third metric class, or fold them under events? Curious to hear how others structure their reporting.

---

Read the full Japanese version (with references and related articles) on RevenueScope.