---
title: "Reading standard reports with confidence"
description: "The shape of GA4 reporting GA4 has two main analysis surfaces: - Reports — pre-built, aggregated, fast, shareable and suitable for recurring monitoring…"
url: https://optimizeall.com/learn/web-analytics-with-ga4/standard-reports
updated: 2026-10-05
---

Web Analytics with Google Analytics 4 · Reports and explorations · lesson 13 of 20 · 11 min

# Reading standard reports with confidence

## The shape of GA4 reporting

GA4 has two main analysis surfaces:

- **Reports** — pre-built, aggregated, fast, shareable and suitable for recurring monitoring.
- **Explorations** — flexible analysis canvases for ad-hoc questions (next lesson).

The default report collections typically include **Realtime**, **Acquisition**, **Engagement**, **Monetization**, **Retention**, and **User** attributes and technology — though administrators can customize the navigation through the report **library**.

## Acquisition: user versus traffic

This is the most misunderstood distinction in GA4:

| Report | Dimension scope | Answers |
|---|---|---|
| User acquisition | First user source / medium / channel | Where did *new users* first come from? |
| Traffic acquisition | Session source / medium / channel | Where did *each session* come from? |

A user who first discovers you through Instagram and later returns via Google search appears under Organic Social in user acquisition and under Organic Search for the later session in traffic acquisition. Neither is wrong; they answer different questions. When a stakeholder asks "which channel works?", clarify whether they mean *finding new people* or *driving visits and actions*.

## Engagement reports

- **Events** — counts of every event; useful for QA and quick checks.
- **Key events** — outcomes by event.
- **Pages and screens** — views, engagement time, key events by page title or path. Switch the primary dimension to **page path** when titles are duplicated.
- **Landing page** — the first page of sessions; critical for evaluating campaigns and SEO.

## Monetization and retention

Monetization reports show e-commerce purchases, item performance and revenue (when e-commerce events are implemented correctly). Retention shows how many users come back over time and a view of lifetime value. For subscription or repeat-purchase businesses, retention often matters more than acquisition volume.

## Comparisons, filters and date ranges

- **Comparisons** let you place segments side by side (for example mobile vs desktop, or UK vs UAE) directly in reports.
- **Filters** narrow a report to a subset.
- **Compare date ranges** — use the same weekday alignment and be aware of seasonality (Ramadan, Diwali, Black Friday, back-to-school timing differ by market and year).

## Customizing the library

Admins can create **custom report collections** so each audience sees what matters:

```
Collection: "Leadership"
  - Overview: sessions, key events, revenue, key event rate (by channel)
  - Traffic acquisition (session default channel group)
  - Landing pages with key event rate
Collection: "Content team"
  - Pages by content_group and author
  - Engagement rate by landing page
```

Reducing noise in the navigation increases adoption far more than training people to find things in a crowded menu.

## Thresholding and data quality indicators

GA4 may apply **data thresholds** that withhold rows when user counts are small and certain features (such as Google signals or demographics) could allow identification. Reports also show indicators when data is **sampled** or when **modeled data** is included. Check the data-quality icon in the report header before drawing conclusions from small segments.

## Worked example: an influencer campaign readout

A skincare brand ran creator campaigns across the UAE and Saudi Arabia with tagged links (`utm_medium=influencer`, `utm_source=creator_handlename`). To report results:

1. Traffic acquisition → session source/medium, filter medium = influencer.
2. Add metrics: sessions, engagement rate, key events (`purchase`), total revenue.
3. Add a comparison for country = UAE vs Saudi Arabia.
4. Cross-check purchases against creator discount-code redemptions in the store.

Illustratively, one creator may drive many sessions with low engagement, while another drives fewer sessions but far more purchases — the second deserves the renewal conversation.

## 2026 updates to the reporting surface

- **AI assistant traffic.** Google has added dedicated classification for visits from AI assistants (such as ChatGPT, Gemini, Copilot, Claude and Perplexity) in default channel group reporting. Check your property's current channel definitions; if you need your own grouping, create a custom channel group with a source regex.
- **Analytics Advisor / Ask Advisor (beta).** A Gemini-powered conversational assistant inside GA4 can answer questions like "why did revenue drop last week?". Use it to get oriented quickly, then confirm every number in a standard report or exploration before you share it.
- **More flexible dashboards.** Google has been expanding customizable overview and dashboard-style reporting inside GA4. Check the "What's new in Google Analytics" page for the options in your property.

## Hands-on: the same weekly numbers via the Data API

When you report the same numbers every week, automate the pull. This script fetches sessions, key events and revenue by session channel for the last two complete weeks:

```python
# pip install google-analytics-data
from google.analytics.data_v1beta import BetaAnalyticsDataClient
from google.analytics.data_v1beta.types import DateRange, Dimension, Metric, RunReportRequest

client = BetaAnalyticsDataClient()        # Application Default Credentials, read-only access
req = RunReportRequest(
    property="properties/123456789",
    dimensions=[Dimension(name="sessionDefaultChannelGroup")],
    metrics=[Metric(name="sessions"), Metric(name="keyEvents"), Metric(name="totalRevenue")],
    date_ranges=[DateRange(start_date="14daysAgo", end_date="8daysAgo", name="prev"),
                 DateRange(start_date="7daysAgo", end_date="yesterday", name="this")],
)
for row in client.run_report(req).rows:
    print([d.value for d in row.dimension_values], [m.value for m in row.metric_values])
```

Numbers from the API match standard reports (including thresholds and modeling where they apply), which is why they differ from raw BigQuery counts.

## Second worked example: a Lahore SaaS weekly readout

A SaaS company's growth lead used to screenshot six reports every Monday. Now a script pulls channel sessions, key events and trial starts for two weeks, writes them to a sheet with week-over-week changes, and the analyst spends the saved hour on the "why" notes. The leadership collection in GA4 still exists for ad-hoc checks, but the Monday meeting runs from the sheet and its commentary.

## Common mistakes

- Using user acquisition to judge campaign performance for returning customers.
- Reporting page titles when several pages share the same title.
- Comparing a week containing a public holiday with a normal week without noting it.
- Ignoring threshold or sampling indicators on small segments.
- Reading totals without rates: a channel that doubles sessions but halves its key event rate has not necessarily improved.
- Forgetting time zones: a property set to one time zone reporting on markets in another can shift "daily" peaks and make day-of-week comparisons misleading.

## Weekly reading routine

```
1. Key events and revenue vs previous period and same period last year
2. Traffic acquisition: which channels moved, and did key event rate move with them?
3. Landing pages: top gainers and losers by key events
4. Technology: any device/browser with a sudden drop (possible bug)
5. Note anomalies and hypotheses; do not over-explain small changes
```

## Video lecture: Reading standard reports with confidence

Lecture coming soon · 15 chapters · about 8 minutes. Read the full transcript below.

1. Standard reports
2. Why it matters
3. Two surfaces
4. User versus traffic acquisition
5. Clarify, then read
6. Honest comparisons
7. 2026 changes
8. Example 1: creator campaign readout
9. Example 2: Lahore SaaS readout
10. Watch me do it, part 1
11. Watch me do it, part 2
12. Common mistakes
13. Weekly routine
14. Recap
15. Try this now

## Lecture transcript

### Standard reports

Every Monday, somewhere, a marketing manager opens G A four, clicks around for twenty minutes, takes a few screenshots, and still can't say whether last week was good. Standard reports aren't the problem. Not knowing which report answers which question is. In this lecture you'll learn the shape of G A four's reporting, the crucial difference between user and traffic acquisition, how to compare segments honestly, how to customize the library for each audience, what changed in twenty twenty-six, and how to automate your weekly numbers.

### Why it matters

Why does this matter? Because reports are how most people in your organization experience analytics. If they can't find answers quickly, they'll stop looking, or worse, they'll pull the wrong report and draw the wrong conclusion. A channel that looks weak in user acquisition might be strong in traffic acquisition, and vice versa. Knowing the difference, and designing reports around questions, is what turns G A four from a maze into a tool.

### Two surfaces

Here's the shape. G A four has two analysis surfaces. Reports are pre-built, aggregated, fast, shareable, and good for recurring monitoring. Explorations are flexible canvases for ad-hoc questions, which we'll cover next. Think of reports as the dashboard in your car: speed, fuel, warning lights, always there. Explorations are the mechanic's diagnostic computer: powerful, but you plug it in when something needs investigating. The default collections typically include Realtime, Acquisition, Engagement, Monetization, Retention, and user attributes and technology.

### User versus traffic acquisition

Now the most misunderstood distinction in G A four. User acquisition uses first user source, medium and channel. It answers: where did new users first come from? Traffic acquisition uses session source, medium and channel. It answers: where did each session come from? A user who first discovers you on Instagram and later returns through Google search appears under Organic Social in user acquisition, and under Organic Search for the later session in traffic acquisition. Neither is wrong. They answer different questions.

### Clarify, then read

So when a stakeholder asks which channel works, clarify: do you mean finding new people, or driving visits and actions? Then the engagement reports: events, key events, pages and screens, and landing pages. Switch the primary dimension to page path when titles are duplicated. Landing pages are critical for evaluating campaigns and search. And monetization and retention: purchases, item performance, and how many users come back over time. For subscription and repeat-purchase businesses, retention often matters more than acquisition volume.

### Honest comparisons

Comparisons, filters and date ranges. Comparisons put segments side by side, like mobile versus desktop, or the UK versus the UAE. Filters narrow a report. When comparing date ranges, align weekdays and watch seasonality. Ramadan, Diwali, Black Friday and back-to-school timing differ by market and by year. And check the data quality icon in the report header: data thresholds may withhold rows for small groups when Google signals or demographics are involved, and indicators show when data is sampled or modeled.

### 2026 changes

And twenty twenty-six brought changes to the reporting surface. Google added dedicated classification for visits from AI assistants, like ChatGPT, Gemini, Copilot, Claude and Perplexity, in default channel reporting, so check your channel definitions. Analytics Advisor, with Ask Advisor in beta, lets you ask plain-language questions inside G A four. Use it to get oriented, then confirm every number in a report before you share it. And Google keeps expanding customizable dashboard-style reporting, so check the what's new page for your property.

### Example 1: creator campaign readout

First example, a simple one. A skincare brand ran creator campaigns across the UAE and Saudi Arabia, with tagged links where medium is influencer and source is each creator's handle. To report results: traffic acquisition, session source and medium, filtered to medium influencer. Add sessions, engagement rate, purchases and revenue. Add a comparison for the UAE versus Saudi Arabia. And cross-check purchases against each creator's discount code redemptions. Illustratively, one creator drives many sessions with low engagement, another drives fewer sessions but far more purchases.

### Example 2: Lahore SaaS readout

Second example, a business case. A Lahore software company's growth lead used to screenshot six reports every Monday. Now a script pulls channel sessions, key events and trial starts for two weeks, writes them to a sheet with week-over-week changes, and the analyst spends the saved hour writing the why notes. The leadership collection in G A four still exists for ad-hoc checks, but the Monday meeting runs from the sheet and its commentary. Automation moved time from collecting numbers to explaining them.

### Watch me do it, part 1

Watch me customize the library for leadership. As an admin, I create a collection called Leadership with no more than four reports: an overview with sessions, key events, revenue and key event rate by channel; traffic acquisition by session default channel group; landing pages with key event rate; and a monetization overview. I publish it. Reducing noise in the navigation increases adoption far more than training people to find things in a crowded menu. Then I make a second collection for the content team.

### Watch me do it, part 2

Then I automate the weekly numbers with the Data A P I. The lesson's Python script creates a client using application default credentials with read-only access. It requests the session default channel group, with sessions, key events and total revenue, for two date ranges: the previous week and last week. It prints a row per channel. Because the A P I returns the same numbers as standard reports, including thresholds and modeling, they'll match what stakeholders see in the interface, unlike raw BigQuery counts.

### Common mistakes

Common mistakes. Using user acquisition to judge campaign performance for returning customers. Reporting page titles when several pages share the same title. Comparing a week with a public holiday to a normal week without noting it. Ignoring threshold or sampling indicators on small segments. Reading totals without rates. And forgetting time zones: a property set to one time zone reporting on markets in another can shift daily peaks.

### Weekly routine

Here's a weekly reading routine you can adopt. One, key events and revenue versus the previous period and the same period last year. Two, traffic acquisition: which channels moved, and did the key event rate move with them? Three, landing pages: top gainers and losers by key events. Four, technology: any device or browser with a sudden drop, which is often a bug. And five, note anomalies and hypotheses. Don't over-explain small changes.

### Recap

Recap. Reports are for monitoring, explorations for investigation. User acquisition is where new users first came from; traffic acquisition is where each session came from. Compare honestly, with aligned weekdays, seasonality and quality indicators in mind. Customize collections per audience. Use Ask Advisor to orient, then verify. And automate recurring numbers with the Data A P I, so your time goes into explaining them.

### Try this now

Try this now. Design, on paper or in G A four, a leadership collection with no more than four reports, and write the three questions it should answer each week. Then ask Ask Advisor, if you have it, one of those questions, and check its answer against the report. Note where they agree and where they don't.

## Key takeaways

- Reports are for monitoring; explorations are for ad-hoc questions.
- User acquisition = first source of new users; traffic acquisition = source of each session.
- Customize report collections for each audience to drive adoption.
- Check thresholding, sampling and modeling indicators before concluding.

## Try it

Create (or design on paper) a custom report collection for leadership with no more than four reports, and write the three questions it should answer each week.

- [Previous: Privacy by design and data governance](https://optimizeall.com/learn/web-analytics-with-ga4/privacy-by-design)
- [Next: Explorations: funnels, paths, segments and cohorts](https://optimizeall.com/learn/web-analytics-with-ga4/explorations)
- [All lessons of Web Analytics with Google Analytics 4](https://optimizeall.com/learn/web-analytics-with-ga4)