Google Analytics 4 reporting
GA4, translated into a client report
Users, sessions, engagement, key events and revenue — by channel, source, campaign, page, event and device — scoped to one client. Sign in to open the report workspace, or preview what's inside.
Google Analytics 4 reporting
GA4 knows everything about a client’s website and shows almost none of it willingly. This dashboard reorganizes the property into the report an account team actually presents: acquisition channels ranked by outcomes, engagement measured GA4’s way, and the path from traffic source through landing page to key event and revenue — readable in one sitting.
The report opens where every analytics conversation starts: which channels bring the traffic and which channels bring the results. Each default channel group is reported with users, sessions, engagement rate, engagement time, key events and revenue, and one click filters the entire dashboard to that channel.
Because the channel table carries outcomes and not just volume, the “lots of traffic, no results” channel is exposed immediately — and the quiet channel quietly converting gets its budget argument made for it.
Channels summarize; source/medium explains. The report drills from each channel group into its constituent sources — google/organic, google/cpc, klaviyo/email and the rest — and from there into tagged campaigns, so a spike in paid social traces to the specific campaign that caused it.
For agencies running the media, this is the accountability layer: the same campaign names your team launched, reported with sessions, engagement, key events and revenue instead of platform-side clicks alone.
GA4 replaced bounce rate with a better question: did the session engage? The report is built on that model — engaged sessions, engagement rate and average engagement time are first-class metrics on every table, trended daily and comparable period over period.
That consistency makes quality arguments concrete: a landing page with strong sessions but weak engagement time is a message problem; a channel with modest traffic but 70% engagement is an expansion candidate.
Every key event — leads, demo bookings, sign-ups, purchases — is reported with its count, session conversion rate and attributed revenue, and the same key-event columns appear on channels, sources, campaigns and landing pages, so “what converts” is answerable at every altitude.
Revenue rides through the whole report rather than living in a separate ecommerce silo, which is what lets a monthly review end on the only slide clients remember: what the website made.
Landing pages are reported with sessions, engagement and key events — the entry-point view that grades both SEO content and paid destinations. Pages & screens adds the consumption story with views, users and time per page, and the events table shows the raw behavioral stream from scrolls and clicks through form submits and purchases.
Together they answer the question analytics reports usually dodge: not just how many people came, but what the site did with them.
Demographic estimates, country and city breakdowns, and the device / browser / operating-system profile complete the audience picture — each with engagement and key-event context so segments are judged on behavior, not just headcount.
Everything lives in one report scoped to a single client and presented with your agency branding, alongside the search, paid and social reporting in the same workspace — data-source setup remains a separate step.
It is GA4's own bucketing of traffic into channels — Organic Search, Direct, Paid Search, Paid Social, Organic Social, Referral and Email. The report opens on that grouping and then drops into source and medium and campaign underneath it, so a channel total can always be traced to the specific sources and UTM values that produced it.
A session is a visit. An engaged session is one that lasted longer than ten seconds, produced a key event, or included at least two page views. Engagement rate is engaged sessions divided by sessions — GA4's replacement for bounce rate, and the reason this report leads with engagement rate and average engagement time instead.
Key events are the events you mark as important: GA4's successor to Universal Analytics goals, and what the platform counts as conversions in most reports. They get their own tab beside the full event list, with revenue attributed to them, so a report can move from “traffic went up” to which actions happened and what they were worth.
Because they answer different questions. GA4 credits a session to the last non-direct channel it can see and counts key events on the site; an ad platform counts conversions against the click or view it served, inside its own attribution window. Showing both, side by side and clearly labelled, is more honest than quoting whichever figure happens to be larger.
Yes. Landing pages, pages and screens, events, key events, demographics, geography and technology each have a tab, all scoped to the client chosen in the header. Revenue sits in the headline tiles attributed to key events, so a landing page can be read for the traffic it receives and the value it produces in the same pass.
