The one-page GA4 report people actually read

In this guide

Why monthly GA4 reports go unread
The metrics that earn a place
Month on month or year on year, and annotating the breaks
GA4 reports, explorations, Data Studio or the Data API
Thresholds, sampling, retention and reports that disagree
Commentary that ends in a decision
The one-page template
Monthly checklist
FAQ

A monthly GA4 report gets read when it fits on one page, uses a handful of clearly defined metrics, and ends each point with a decision and a name against it. Everything else can live in an appendix. Below is a one-page structure, which tool to build each part in, and the GA4 quirks to check before anyone sees the numbers.

Why monthly GA4 reports go unread

A report that lists every metric GA4 can produce hands the analysis to the reader. The person opening it wants to know what changed and what happens next, and a dozen charts make them dig for both.

I draft monthly GA4 reports for 36 websites automatically, and a person checks each one before it’s sent. That check should ask whether the numbers make sense and whether each comment leads anywhere, the split I describe in using AI in a marketing workflow without losing control.

The metrics that earn a place

I’d keep seven items. Define each one once, in plain words, so nobody argues about what a number means.

Sessions. A session ends after 30 minutes of inactivity by default (Google Analytics Help).
Engaged sessions. A session that lasts more than 10 seconds, has a key event, or has 2 or more page or screen views (Google Analytics Help).
Engagement rate. Engaged sessions divided by sessions. Bounce rate is the inverse (same source), so show only one of them.
Key events. GA4’s name for what used to be called conversions (more below).
Session key event rate. Sessions with a key event divided by total sessions (Google Analytics Help).
Channel. Where the session came from, by channel group.
Landing page. The first page of the session.

Key events and Google Ads conversions are different

Google announced on 21 March 2024 that GA4 “conversions” were being renamed “key events” (Search Engine Journal). The measurement didn’t change. “Conversion” now refers to the Google Ads side, the one used for bidding (Google Analytics Help).

So label them as key events on the page. Two different “conversions” figures will eat the meeting. If the business cares about sales, my post on why your best campaign by leads might be your worst by sales explains why leads alone can mislead.

Know what the channel group contains

The default channel group has 19 channels, including AI Assistant for traffic from tools such as ChatGPT, Gemini and Copilot (Google Analytics Help). AI Overviews and AI Mode traffic stays in Organic Search. Cross-network covers Performance Max and Demand Gen (same source).

You can’t edit the default group, but you can build custom channel groups (same source). If you use one, name it on the page.

Month on month or year on year, and annotating the breaks

GA4 offers three date comparisons: Previous period (match day of week), Previous period and Previous year. “Previous year (match day of week)” has been removed (Google Analytics Help). So year on year can now compare months with a different mix of weekdays.

Channel definitions have also moved. The AI Assistant channel was added on 13 to 14 May 2026, and it’s unclear whether older sessions were reclassified (Search Engine Journal). Those sessions likely sat mostly in Referral before (Google hasn’t said); check your own Referral sources first. If that holds, a year-on-year view of either channel won’t compare like with like.

My recommendation: use Previous period (match day of week) as the main comparison, show year on year as context, and write the breaks on the page. For example: “AI Assistant channel added May 2026; earlier sessions likely sat mostly in Referral (Google hasn’t said).” The key events rename is a label change only, so it doesn’t break the numbers.

GA4 reports, explorations, Data Studio or the Data API

How I’d split the work for a one-page report:

Tool	Use it for	Watch out for
GA4 standard reports	Headline numbers, and the check for everything else	Thresholds can hide rows (source); sampling can apply (source); the last 48 hours may differ (source)
Explorations	One-off questions, segments and funnels	Limited by data retention (source); can disagree with reports (source); 200 per user (source)
Data Studio	The shared one-page view, including for people without GA4 access	Won’t match explorations (source); draws on Data API quotas (see below)
Data API	Pulling the same numbers for many properties	200,000 tokens per property per day, 40,000 per hour, 10 concurrent requests on standard (source); sampling can apply (source)

Data Studio is Looker Studio’s new name, announced on 11 April 2026; existing reports carried over, and there’s a free tier and a paid Pro tier (Google Cloud Blog).

Google’s documentation says a Data Studio report “will match the data, but not the explorations” in GA4. If the report uses the owner’s credentials, viewers can see it without GA4 access (Data Studio documentation). When a dashboard number looks odd, check it against the matching standard report.

Because Data Studio’s GA4 reports draw on the property’s Data API quotas (Google for Developers), a busy dashboard can run into quota errors.

Thresholds, sampling, retention and reports that disagree

Check these four before the report goes out.

Thresholds

Google sets data thresholds and you can’t change them. They hide rows when a report includes demographics or has low user counts. A wider date range makes them less likely (Google Analytics Help). If a monthly table has gaps, drop the demographic dimension or note that rows were withheld.

Sampling and (other)

Sampling can apply in reports, explorations and the Data API; BigQuery data isn’t sampled. Dimensions with more than 500 unique values a day can collapse into “(other)” (Google Analytics Help). Check landing page tables for an “(other)” row before commenting on pages.

Retention

Standard properties keep event data for 2 or 14 months. The setting limits explorations and funnel reports only; standard reports aren’t affected (Google Analytics Help). On 2 months, a year-on-year exploration comes back empty. Set it to 14 months now. It only applies from the change onwards.

Reports and explorations that disagree

Reports and explorations can show different figures because of the retention cap, case-sensitive filters, comparisons being applied as segments, and modelling. Data from the last 48 hours may also differ (Google Analytics Help). I’d wait at least two full days after month end before pulling numbers.

Commentary that ends in a decision

Each comment gets four parts: observation, cause, decision, owner. If you can’t fill in the decision, the observation probably doesn’t belong on the page.

Here’s one built from the channel change above:

Observation: AI Assistant appears as a channel this year, and Referral is down year on year.
Cause: The AI Assistant channel was added in May 2026. Those sessions likely sat mostly in Referral before (Google hasn’t said).
Decision: Check last year’s Referral sources for AI tools. If they’re there, annotate the year-on-year view and don’t treat the Referral drop as lost traffic.
Owner: Whoever owns the report, by the next send.

The one-page template

This is the structure, top to bottom:

Header: property, date range, comparison used and the date the data was pulled.
Summary: two or three sentences on what changed and what you’re doing about it.
Scorecard: sessions, engaged sessions, engagement rate, key events and session key event rate, each with its comparison.
Channels: the same metrics by channel group (default or a named custom group).
Landing pages: the top pages by sessions, with key events.
Annotations: definition changes, tracking changes, withheld rows and any “(other)” rows.
Decisions: observation, cause, decision, owner and date for each point.
Appendix link: the exploration or Data Studio report for anyone who wants more detail.

A bare mock-up of the layout:

[Header: property | date range | comparison | date pulled]
[Summary: 2 to 3 sentences]
[Scorecard: 5 metrics, each with comparison]
[Channels table]          [Landing pages table]
[Annotations]
[Decisions: observation | cause | decision | owner | date]
[Appendix link]

Monthly checklist

Wait at least 48 hours after month end.
Confirm data retention is set to 14 months.
Check headline numbers against GA4 standard reports.
Look for thresholded rows, sampling and “(other)”.
Annotate any breaks in the comparison.
Write the decisions and have a person check the page before sending.

If key events feed your paid media reporting, it’s also worth getting offline sales back into Google Ads.

FAQ

What counts as an engaged session in GA4?

One that lasts more than 10 seconds, has a key event, or has 2 or more page or screen views (Google Analytics Help).

Are key events the same as conversions?

In GA4, yes: key events are the old conversions, renamed with the measurement unchanged. In Google Ads, “conversion” is the separate figure used for bidding (Google Analytics Help).

How long does GA4 keep data for explorations?

2 or 14 months on a standard property. Set 14 months, because the change only applies from then on (Google Analytics Help).

For the wider picture, see my guide to marketing measurement.

14 sources, all opened and checked

About key events, Google Analytics Help
Google unifies conversion reporting across Ads and Analytics, Search Engine Journal
Engaged sessions, engagement rate and bounce rate, Google Analytics Help
Analytics dimensions and metrics (sessions and session key event rate), Google Analytics Help
Default channel group, Google Analytics Help
Google Analytics adds AI Assistant as a default channel group, Search Engine Journal
Compare date ranges, Google Analytics Help
Data retention, Google Analytics Help
Why reports and explorations can show different data, Google Analytics Help
Data limits, sampling and (other), Google Analytics Help
Data thresholds, Google Analytics Help
Data API limits and quotas, Google for Developers
Looker Studio is now Data Studio, Google Cloud Blog
Connect to Google Analytics, Data Studio documentation, Google Cloud