Reading standard reports with confidence

0:00 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.

0:37 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.

1:09 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.

1:43 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.

2:19 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.

2:54 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.

3:29 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.

4:05 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.

4:42 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.

5:18 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.

5:55 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.

6:32 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.

7:02 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.

7:34 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.

8:02 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.