GA4 reports: the 8 standard reports that actually matter

Out of the dozens of GA4 reports in the left-hand menu, eight answer almost every question a marketing team asks: Traffic acquisition, User acquisition, Landing page, Pages and screens, Events, Key events, Ecommerce purchases and Tech details. The rest are overviews, niche views or reports that look useful and quietly mislead.

This is about the standard reports, the ones under Reports in the left nav, and how to read them right. If you want to build your own, I've covered custom GA4 reports and Explorations separately. Most teams don't need either until they've mastered these eight.

The 8 GA4 reports at a glance

Menu paths below follow the default Life cycle and User collections. If your property was created with business-objective collections ("Generate leads", "Drive online sales"), the same reports sit under different headings, and you can switch collections in Reports > Library.

Report	Where	Question it answers	Common misread
Traffic acquisition	Acquisition > Traffic acquisition	Which channels bring sessions, and which sessions convert?	Comparing its totals with User acquisition
User acquisition	Acquisition > User acquisition	Which channels bring new people in the first place?	Treating it as "where my traffic comes from now"
Landing page	Engagement > Landing page	Which entry pages start sessions that go somewhere?	Ignoring the "(not set)" row
Pages and screens	Engagement > Pages and screens	Which pages get viewed, and how much?	Reading by page title instead of page path
Events	Engagement > Events	What's being tracked, and how often does it fire?	Reading event count as number of people
Key events	Engagement > Key events	How many conversions happened, by event?	Comparing key event count with CRM leads one to one
Ecommerce purchases	Monetization > Ecommerce purchases	Which products sell, view to cart to purchase?	Comparing item revenue with order totals in the shop backend
Tech details	Tech > Tech details	Do browsers and devices behave differently?	Skipping it because it looks like IT trivia

Traffic acquisition vs User acquisition: the pair everyone mixes up

These two look nearly identical. Same channels, similar columns. They count different things.

Traffic acquisition is session-based. Its main dimension is Session primary channel group, so every session gets credited to the source that started it. A user who first found you through Google and returned five times through a newsletter adds one organic session and five email sessions. Key events in this report go to the source of the session they happened in.

User acquisition is user-based. Its main dimension is First user primary channel group, so each user is credited forever to the channel that brought them the first time. That newsletter reader stays "Organic Search" here, whatever they do next.

Agnieszka, who runs marketing for a furniture store in Łódź, learned this mid-presentation. Her slide said organic search brought 4,200 users in September. Her colleague's slide, made from the other report, said 2,900.

Both were right. One counted users by first source, the other counted users within organic sessions, and a user can appear under several channels in Traffic acquisition.

My rule: use Traffic acquisition for "how are this month's campaigns doing" and User acquisition for "which channels actually find new customers". Never put their numbers on the same slide without a label. If you're seeing large Direct or Unassigned rows here, that's a tagging problem, not a channel, and I've written about both unassigned traffic and Direct / (none).

Landing page and Pages and screens: different jobs, same data

Pages and screens tells you what got viewed. Landing page tells you where sessions started. That second one is the report I'd open first on any content or SEO question. Most teams don't know it exists.

Read Landing page with sessions, engaged sessions and key events side by side. A page with 3,000 sessions and an 18% engagement rate is a leak. A page with 400 sessions and 30 key events is the one to send more traffic to.

Then look for the "(not set)" row. It shows up when a session has no page view at its start, for example when another event opens the session or when a page view gets blocked or delayed by consent handling. A few percent is normal. Fifteen percent means your tagging has a timing problem.

In Pages and screens, change the primary dimension from "Page title and screen class" to "Page path and screen class". Titles get duplicated across templates ("Product | Store" on 600 pages) and change whenever someone edits the CMS. Paths don't.

One more detail. Views count every page view, including reloads. Users count people.

A page with 5,000 views and 900 users isn't popular, necessarily. It might just be the page people refresh while waiting for an order confirmation.

Events and Key events: occurrences, not people

The Events report lists every event name the property received, with event count, total users and event count per active user. It's the closest thing GA4 has to an inventory. I read it before any other report on a new property, because duplicates and junk show up there first.

Two things to look for:

• Event names that differ only in case or suffix. Generate_Lead next to generate_lead, or form_submit next to form_submit_v2. Each pair is a split number.
• Event count per active user that makes no sense. If purchase averages 2.1 per user per month on a store where people buy twice a year, a tag is firing twice. Often silently.

The Key events report shows the events you marked as key events. If your collection doesn't list it, add it in Reports > Library, or pick a key event from the Key events dropdown in any detail report. Key event count counts occurrences by default, so one person submitting a form three times counts three. You can change the counting method per key event to once per session in Admin > Data display > Key events, which is what I use for lead forms.

Don't expect it to match your CRM one to one. Consent, ad blockers, spam submissions and deduplication on the CRM side all pull the numbers apart.

A gap of 5 to 15 percent is normal. A gap of 40 percent is a broken tag. If conversion rate is what you report, how GA4 calculates it is worth ten minutes, because there are two of them.

Ecommerce purchases and Tech details: the honest ones

Ecommerce purchases works at item level: items viewed, added to cart, purchased, and item revenue for each product. It's the report for "which products sell and which ones get looked at and abandoned".

Wojtek runs a cycling parts shop in Kraków. In August the report showed €48,300 in item revenue. His shop backend said €53,900.

He assumed GA4 was losing orders. It wasn't, mostly.

Item revenue is the sum of item prices times quantity. It doesn't include shipping or tax, and his backend total did. After taking out €4,100 in shipping, the remaining €1,500 gap was about 3%, roughly what you'd expect from consent declines. For order-level revenue, look at Total revenue or Purchase revenue in the Monetization overview instead.

Tech details sits under the User collection, in Tech > Tech details. It breaks sessions, users and key events down by browser, operating system, device category and screen resolution. Everyone skips it. I check it every month.

Here's why. When a checkout or consent update breaks tracking, it rarely breaks everywhere at once. It breaks on Safari, or on iOS, or on one Android browser. A key event rate of 2.4% on Chrome and 0.3% on Safari isn't user behavior. It's a bug, and this report is the fastest place to see it.

The GA4 reports I'd ignore (or open twice a year)

I'll be blunt: a lot of the default menu is there because someone at Google needed a place for it, not because you need to read it.

• Overview pages (Acquisition overview, Engagement overview, Monetization overview). Cards with small charts. Fine for a glance, useless for a decision. Click through to the detail report every time.
• Demographic details. Age, gender and interests depend on Google signals, which in the EU means consent, thresholds and big gaps. Country and city are fine. The rest I wouldn't put in front of a CEO.
• Retention. Interesting chart, almost never actionable for the sites I work with. If you're serious about cohorts, a cohort exploration is better.
• Realtime. A testing tool, not a report. Use it to confirm a campaign or tag is live, then close it.
• Purchase journey and Checkout journey. Useful only if your ecommerce events are complete and in the right order. On most WooCommerce and custom builds I audit, they aren't, and these reports show nonsense drop-offs.

How to read any standard report without fooling yourself

Standard GA4 reports are unsampled and built from pre-aggregated tables, which is why they load fast. That doesn't make them simple. Before trusting a number, I run through this:

1. Check the date range. The default is the last 28 days, and today's data is incomplete. Processing can take 24 to 48 hours, so yesterday may still move.

2. Look for the threshold icon. If Google signals is on and counts are low, GA4 hides rows to protect privacy and shows a warning icon next to the report title. Switching Admin > Data display > Reporting identity to Device-based usually removes thresholds, at the cost of cross-device stitching.

3. Find the "(other)" row. It means the report hit its row limits, usually because of a high-cardinality dimension. The total is right. The breakdown below it isn't complete.

4. Use comparisons, not filters, for quick splits. The Add comparison button at the top lets you put mobile vs desktop or two countries side by side without touching the report setup.

5. Customize, then save. With the Editor role, the pencil icon lets you change dimensions, metrics and charts, then Save as new report. The custom reports guide goes deeper if you outgrow that.

Frequently asked questions

What are the most important GA4 reports? For most businesses: Traffic acquisition, User acquisition, Landing page, Pages and screens, Events, Key events, Ecommerce purchases (for stores) and Tech details. Together they answer where people come from, what they do, what converts and whether tracking works on every browser.

What's the difference between Traffic acquisition and User acquisition in GA4? Traffic acquisition credits each session to the source that started it. User acquisition credits each user to the channel that first brought them. Their totals will never match, and they're not supposed to.

Why does my GA4 Landing page report show "(not set)"? "(not set)" appears when a session starts without a page view, often because another event opened the session or because consent handling delayed the page view. A small share is normal. A large share points to a tag timing problem in GTM.

Are GA4 standard reports sampled? No, standard reports are unsampled. They can still show data thresholds when Google signals is on, "(other)" rows when row limits are hit, and incomplete data for the most recent 24 to 48 hours. Explorations, unlike standard reports, can be sampled on large properties.

Why doesn't GA4 revenue match my shop backend? Item revenue in the Ecommerce purchases report excludes shipping and tax, while most backends include them. Consent declines and ad blockers also remove some orders. Compare item revenue with the backend's product revenue excluding shipping and tax, and expect a gap of a few percent.

Can I add or remove standard reports in GA4? Yes. In Reports > Library, editors can edit collections, add detail reports to the left menu, remove the ones nobody reads and create new reports from templates. Changes apply to everyone using the property.

Next steps

Open the Landing page report this week. Sort by sessions, look at the engagement rate of your top ten entry pages, and check the size of the "(not set)" row. That's ten minutes, and it usually tells you more than a month of glancing at the home dashboard.

Then open Tech details and compare key event rates across browsers. If one browser converts at a fraction of the others, your reports aren't telling you about users. They're telling you about a bug.

If you'd like the tracking under these reports checked properly, the free GTM audit looks at every tag feeding GA4. And if you'd rather have someone read these eight reports for anomalies every month, that's the GA4 monitoring retainer.

---

Sources and further reading - Traffic acquisition report (Google Analytics Help) - User acquisition vs. Traffic acquisition (Google Analytics Help) - Data thresholds (Google Analytics Help) - About the (other) row (Google Analytics Help)