You have the Google Analytics 4 account. Someone set it up, the data is flowing, and the dashboard greets you with charts you scroll past on the way to something else. This guide is for that moment. It explains what GA4 actually measures, how it is structured, and the handful of numbers worth reading before any of the rest.
Everything is an event
The single idea that unlocks GA4 is this: every interaction is an event. A page view is an event. A scroll is an event. A click on an outbound link, a video play, a form submission, a purchase: all events. An event can carry parameters, which are small pieces of context attached to it. A page_view event carries the page location and title. A purchase event carries the value and currency.
The older version of Analytics (Universal Analytics) was built around the pageview as its core unit, with events bolted on as a secondary thing. GA4 flips that. The pageview is now just one event type among many, which is why GA4 can measure app screens, scrolls, and downloads with the same machinery it uses for pages. Once you accept that everything is an event with parameters, the rest of the interface stops looking arbitrary.
If you remember one sentence: in GA4, users trigger events, events carry parameters, and reports are just counts and rates built on top of those events.
The four reports, in plain terms
The standard reports are grouped into four areas that map to a simple customer journey. Read them in this order and the data tells a story rather than a pile of numbers.
- Acquisition: where your users came from. Channels (organic search, paid, social, direct, referral, email), the specific source and medium, and which campaigns drove them.
- Engagement: what users did once they arrived. Which pages and screens they saw, which events fired, and how long they stayed engaged.
- Monetization: revenue and ecommerce. Items purchased, purchase value, and promotions, if you sell something and have ecommerce tracking set up.
- Retention: whether users come back. New versus returning users and how engagement holds up over the days after a first visit.
Acquisition answers "who showed up and from where". Engagement answers "did they do anything". Monetization answers "did it pay off". Retention answers "will they return". Most reporting questions live in one of those four buckets.
The five metrics to read first
GA4 exposes hundreds of dimensions and metrics. You do not need them. Start with five, and know exactly how each is defined.
- Users: the count of distinct people (more precisely, distinct browsers or devices) who triggered at least one event in the date range. One person on a laptop and a phone usually counts as two.
- Sessions: the count of visits. A session is a group of events from one user within a time window; it ends after 30 minutes of inactivity by default. One user can have many sessions.
- Engaged sessions: a session that meets at least one of three conditions: it lasted 10 seconds or longer, OR it had 2 or more screen or page views, OR it included at least one key event.
- Key events: the actions you have flagged as mattering, such as a lead form submission or a purchase. This is the metric Google used to call "conversions". Each one is counted per event instance, not per session.
- Engagement rate: Engagement rate = engaged sessions ÷ sessions. Its mirror image is bounce rate = 1 - engagement rate. Conversion rate is the related idea for outcomes: user conversion rate = converting users ÷ total users, and session conversion rate = converting sessions ÷ total sessions.
Notice the recurring question hiding in those definitions: per user or per session? The same activity divided by users gives one number and divided by sessions gives another. Always know which denominator a rate is using before you compare it to anything.
Half of reading GA4 well is knowing whether a number is counted per user, per session, or per event.
The three things beginners always misread
1. Sessions versus users
These are not interchangeable. Sessions will almost always be the larger number because one person returns more than once. If a colleague says "we had 4,000 visitors" check whether they mean users (people) or sessions (visits). Reporting one as the other is the most common honest mistake in this tool.
2. Conversions are now key events, counted per instance
The word "conversion" was renamed to "key event" in the reports. The naming matters less than the counting: key events are tallied per event instance, not capped at one per session. If a user submits two forms in one visit, that is two key events, not one. So key events can exceed sessions, which surprises people expecting a tidy one-per-visit number. Choosing which events deserve this status is its own decision, covered in how to choose your GA4 key events.
3. Thresholds, sampling, and the placeholder rows
GA4 applies data thresholds: when a report covers very few users, Google may hide rows to protect identity, so small numbers can simply vanish. Large or complex queries can also be sampled, meaning the figure is an estimate from a subset, usually flagged with an icon. And you will meet placeholder rows: (not set) means GA4 had no value for that dimension, while (direct) in the source column means it could not attribute a referrer, often typed URLs, bookmarks, or stripped tracking. None of these are bugs; they are honesty markers. Treat them as a prompt to check your setup, not a reason to distrust the whole report.
Cheat sheet
| Metric | What it is | How it is counted |
|---|---|---|
| Users | Distinct people (devices) who triggered an event | One count per distinct device in the range |
| Sessions | Visits, grouped events ending after 30 min idle | One count per visit; many per user |
| Engaged sessions | Sessions that were "real" visits | Session lasting 10s+, OR 2+ views, OR a key event |
| Key events | Actions you flagged as important (old "conversions") | Counted per event instance, not per session |
| Engagement rate | Share of visits that were engaged | Engaged sessions ÷ sessions |
| Conversion rate | Share that completed a key event | Converting users ÷ users (or sessions ÷ sessions) |
If you want a sibling source that pairs naturally with GA4 for organic traffic, search query data lives in a different tool. Our Google Search Console for beginners guide covers the half of the picture GA4 does not show.
In Clearly
Connecting a GA4 property in Clearly turns these definitions into a live report. You authorize the property once, pick a date range, and the standard building blocks fill in: a headline scorecard row, channel and engagement breakdowns, and trend charts. The metrics keep the meanings above, so engagement rate stays engaged sessions ÷ sessions and key events stay per instance. Nothing is silently redefined.
The key events you flagged in GA4 surface as headline scorecards, so the actions that matter sit at the top instead of buried in a menu. Acquisition becomes a channel breakdown, engagement becomes its own panel, and the whole thing is shareable with a client by link. You read the report; you do not assemble it.
Where to go next
You now have the model (everything is an event), the map (four report areas), and the five numbers that carry most of the meaning, each with a real definition rather than a vibe. Open your own GA4 account and read just those five, in order, for one date range. Then decide which events deserve to be key events, and pull in Search Console for the organic search side. That is a complete beginner's reading of analytics, and it is enough to brief a client without bluffing.