The GA4 Reports That Actually Matter (And the Ones You Can Ignore)

The short answer

GA4 has thirty-plus default reports plus a whole separate Explorations interface for custom ones. Most teams pick three or four reports, look at them in standup, and ignore the rest. That's the wrong move in two directions: they're missing the reports that actually answer business questions, and they're spending time on reports that mostly create anxiety without driving decisions.

This post is the short list I work from: five reports that matter, a few I deliberately ignore, and the custom Explorations worth the time to build.

Why most GA4 reporting fails

Two reasons. First, the default GA4 home page surfaces metrics that are easy to display but not particularly decision-relevant. Total users, sessions, views. They go up. They go down. So what?

Second, the reports that DO matter are scattered across multiple sections, each requiring a couple of dropdown changes to be useful. Most users don't make the changes. They look at the default view, see numbers move, and move on without learning anything.

The fix is having a small number of saved views you trust and a habit of returning to them. Five reports. One question per report. Read them every Monday.

The 5 reports I actually use

1. Acquisition > User Acquisition

The single most useful default report. Shows where your new users come from, broken down by First User Source / Medium / Channel. Set the time range to the last 28 days and compare to the prior 28. Save the comparison view.

• What it answers: 'Where is new traffic coming from, and is the mix changing?'
• Watch for: any channel that drops more than 20% week-over-week (especially organic search, where drops can signal indexation problems).
• Tip: switch the secondary dimension to Landing Page to see which entry pages each channel sends users to.

2. Engagement > Landing page

The Landing Page report is the closest thing GA4 has to the old 'Top Landing Pages' report from Universal. Sort by Sessions descending and you see which entry points are doing the work. Add the Conversion (Key Events) column and you see which ones convert.

• What it answers: 'Which pages are driving entries, and which of those entries are converting?'
• Watch for: high-traffic pages with low conversion rates (CRO opportunity) and high-converting pages with low traffic (acquisition opportunity).
• Tip: combine with the Acquisition report to see traffic source breakdown for any specific landing page.

3. Engagement > Events (filtered to Key Events)

Filter the Events report to only your Key Events. This is your conversion summary view. Source, count, value, trend. The version of this report most teams use is the auto-generated 'Conversions' card on the home page, which is fine for a glance but doesn't let you slice by source.

• What it answers: 'How many leads / signups / purchases happened, by source?'
• Watch for: any Key Event suddenly going to zero (almost always a tracking break, not a real outcome).
• Tip: add the source/medium dimension and you have a real attribution view, free.

4. Realtime + DebugView

Realtime is for live monitoring. DebugView is for testing tracking changes. Both are necessary, neither shows up in standard reporting reviews.

• What Realtime answers: 'Is anything happening on the site right now?' Useful during launches, campaigns, and outages.
• What DebugView answers: 'When I submitted that form, did the right event fire with the right parameters?' Mandatory before flagging anything as a Key Event.
• Tip: bookmark DebugView. You'll use it more than any other GA4 surface during conversion-tracking changes.

5. A custom Funnel Exploration on your primary conversion path

Build this once, reuse it forever. Open Explore > Funnel exploration. Define the steps of your primary conversion path: Landing > Service page > Pricing page > Form view > Form submit. Set the steps. Save the exploration.

• What it answers: 'Where in the path do users drop off?'
• Watch for: the largest single-step drop. That's your CRO target.
• Tip: segment the funnel by traffic source. Paid traffic and organic traffic often drop at different steps, which changes the fix.

Reports you can mostly ignore

These reports exist, they appear on dashboards, and they rarely answer a useful question on a small or mid-sized property.

• Demographics. Age, gender, interests. The thresholding rules suppress so much data on most properties that the reports show partial views, often unreliable. If you have very high traffic and Google Signals enabled, this changes. For most properties, skip.
• Tech > Browser / OS. Useful for one specific question: 'Is anything broken for a specific browser or device?' Otherwise, ignore. Don't chase 'we lost users on Safari' as a marketing problem when it's almost always a UX or QA problem.
• Predictive metrics. GA4 needs over a thousand purchases per week within the last 28 days to populate predictive metrics reliably. Most properties don't hit that bar. The numbers display, but they aren't trustworthy.
• The Acquisition Overview card on the home page. The summary version of the User Acquisition report. Use the full report instead.

Custom Explorations worth building

Beyond the funnel exploration above, three more Explorations earn the time it takes to build them.

Path exploration on landing pages

Shows the actual sequence of pages users hit after landing on a specific entry page. Useful for understanding whether your top traffic page is a hub that distributes users to converting pages, or a dead end where most users bounce.

Segment overlap on Key Events vs. organic traffic

Quickly answers: 'How much of my conversion volume comes from organic search?' The default Acquisition report answers this in aggregate. Segment overlap shows the actual user-level overlap and is faster to read at a glance.

Free-form table on landing page + conversion rate

Build a free-form Exploration with Landing Page as the row dimension and Sessions, Key Events, and Conversion Rate as metrics. Sort by Sessions. This gives you the page-level conversion rate view that GA4's standard reports never quite produce cleanly.

Where this connects to CRO

Reporting is what surfaces the CRO opportunities. The funnel exploration shows you where users drop. The landing page report shows which pages convert and which don't. Without the reports, CRO is guesswork. With them, the next test almost always has an obvious target.

If you're new to optimization, the CRO beginner's guide walks through the mindset and process. The reports above are the diagnostic that tells you what to optimize first.

Getting started

If you want to clean up your reporting routine, here's the order.

1. 1Run the GA4 audit checklist. Don't trust reports built on broken tracking.
2. 2Open the User Acquisition report. Set the time range to last 28 days vs. prior 28. Save the view.
3. 3Open the Landing page report. Add the Key Events column. Sort by Sessions.
4. 4Open the Events report. Filter to Key Events. Add source/medium as a secondary dimension.
5. 5Build one Funnel Exploration on your primary conversion path. Save it to the shared library.
6. 6Schedule a 15-minute weekly check-in. Read all five views. Note any anomaly.
7. 7If you want a custom dashboard built on top of these (Looker Studio or otherwise), reach out. Reporting setup is part of every analytics engagement I run.

Better reporting doesn't mean more reports. It means fewer reports, read consistently, with a clear question each one answers. Cut the noise and the signal gets a lot easier to hear. The outdoor and DTC teams I work with run their Monday meeting off these five views and almost never need anything else.

Frequently asked questions

Why are my GA4 numbers different from Universal Analytics?

GA4 uses a different data model (event-based instead of session-based), different attribution defaults (data-driven instead of last-click), and different sampling thresholds. Direct comparisons between UA and GA4 metrics are usually misleading. Treat GA4 as a fresh baseline, not a continuation of UA history.

Should I rebuild my dashboards in Looker Studio or stay in the GA4 UI?

If you have more than two people consuming the data, Looker Studio. The GA4 UI is fine for analysts but exhausting for stakeholders who don't want to learn it. Looker Studio reads from the GA4 connector and lets you build cleaner, more focused views with the metrics that matter to your team.

How often should I review GA4 reports?

Weekly for the standing five views. Monthly for a deeper dive into Explorations and trend analysis. Anything more frequent on a small business property is overkill, the data is too noisy at short intervals to drive decisions.

Are GA4 numbers ever 100% accurate?

No, and that's true of every analytics platform. Cookie consent rejections, ad blockers, sampling, and bot filtering all shave the edges. The goal isn't perfect numbers. It's directionally trustworthy numbers, consistent enough to detect real change. Audit your setup, accept the residual uncertainty, and keep moving.

Keep reading