How to Read GA4 Reports: Ecommerce Needs Just Three

Open GA4 and the left menu sprawls: Reports, Explore, Advertising — and inside Reports, an endless run of Snapshot, Realtime, Acquisition, Engagement, Monetization. "So where am I supposed to look every day?" Unable to answer that, many store owners simply stop opening it. Here's the short answer: for ecommerce revenue decisions, you need three reports. This guide shows where each one lives, what to read in it, and how to connect the three into "revenue efficiency by channel."

TL;DR#

1. Ecommerce revenue decisions need just three GA4 reports

   • "Traffic acquisition" = where visitors come from
   • "Monetization overview (Ecommerce purchases)" = what sold, for how much
   • "Landing page" = which entry pages drive sales

2. Don't try to read everything

   Most GA4 reports aren't directly relevant to ecommerce revenue calls. Open the rest only when you need them

3. Connect the three and you get revenue efficiency by channel

   Read the revenue column in Traffic acquisition, divide by sessions, and you have "revenue per visit" by channel

4. GA4 is free and powerful — but assembly is on you

   Answering real questions means stitching across reports. That's where most people give up

1. Why GA4 makes you feel lost#

Bottom line: GA4 is a general-purpose tool for every kind of site, so only a fraction of its screens matter to ecommerce. Trying to read them all is what gets you lost.

GA4's reports are built to serve blogs, apps, B2B sites, and ecommerce alike. That's why the menu is huge — and why only a small subset matters for ecommerce revenue decisions.

The questions a store operator actually needs answered each day boil down to three:

• Where did visitors come from? (is acquisition working)
• What sold, for how much? (how is revenue this month)
• Which entry pages led to sales? (which page or channel to strengthen)

Each question maps to exactly one report. Everything else — Realtime, Demographics, Tech details — is for troubleshooting or deep dives. Deciding "I check three reports daily, nothing more" is the first step to actually keeping the habit.

2. The three reports: where they live and what to read#

Bottom line: Traffic acquisition, Monetization overview, Landing page. Learn the path and the columns, and five minutes a day is enough.

Note: menu names are as of June 2026. Your property's menu may differ depending on its settings (missing reports can be added from the report Library).

(1) Traffic acquisition — where visitors come from

Path: Reports → Acquisition → Traffic acquisition.

Sessions are broken down by "Session default channel group": Organic Search, Paid Search, Organic Social, Direct, and so on. Watch which channels grew this week. One caveat: visits missing UTM parameters (the tags that identify a traffic source) collapse into Direct. If Direct looks unnaturally large, suspect a tracking issue — see Five causes of rising GA4 Direct/(none) and the order to fix them.

(2) Monetization overview (Ecommerce purchases) — what sold, for how much

Path: Reports → Monetization → Monetization overview (per-product: "Ecommerce purchases").

Total revenue, purchasers, and average purchase revenue live here. For per-product units and revenue, use "Ecommerce purchases." This assumes ecommerce tracking (the purchase event) is set up — if not, start with the 30-minute GA4 ecommerce setup checklist for Shopify. Also, GA4 revenue normally runs a few percent below your cart's numbers; the reasons are covered in Why GA4 revenue doesn't match Shopify.

(3) Landing page — which entry pages drive sales

Path: Reports → Engagement → Landing page.

Sessions and key events (formerly "conversions" — renamed in 2024) are listed by the page where visitors first arrived. For ecommerce this shows which product pages or articles work as entrances. Compare sessions against revenue per entry page and two groups emerge: "high traffic but no sales" and "modest traffic but it sells."

Make these three a morning routine — (1) where from → (2) how much → (3) which entrance — and you can trace the whole revenue picture in five minutes.

3. Connect the three into revenue efficiency by channel#

Bottom line: read the revenue column in Traffic acquisition and divide by sessions per channel. That's "revenue per visit" — the yardstick for budget decisions.

Reading the three reports separately covers daily awareness. But budget decisions — "which channel gets more ad spend or effort" — need one more step: connecting them.

Here's how. In Traffic acquisition, check the "Total revenue" column (on many properties it's in the default columns — scroll the table right; if missing, an editor can add it via "Customize report"). Now sessions and revenue sit side by side per channel. Then divide: revenue ÷ sessions per channel. That's RPS (revenue per session) — a single yardstick for comparing how efficiently each channel turns visits into revenue. Details in What Is RPS: The Metric, Formula, and How to Pull It in GA4.

RPS = channel revenue ÷ channel sessions
Example: Organic Search 600,000 yen ÷ 4,200 sessions = 143 yen

Honest notes on GA4's limits, where most people stumble:

• Column combinations are constrained: some metric combinations can't be shown in standard reports and force you into Explorations
• The Direct problem: checkout domain hops and missing UTMs leak revenue into Direct, distorting per-channel numbers
• Hand-calculation doesn't stick: the division is trivial, but doing it weekly per channel is tedious enough that most people quit

GA4, in short, is a tool where "the ingredients are all there, but you do the cooking." Still — knowing where the ingredients live, you get all this for free. Three reports plus a hand-calculated RPS is the right way to start.

RevenueScope solution

Touring three reports daily, adjusting columns, hand-calculating RPS per channel — this "connecting work" is the main reason GA4 habits die. You know what to do; the cross-screen friction just costs too much, every single time.

RevenueScope puts the three questions from this article on one screen from the start: where visitors came from (sessions by channel), how much was sold (measured revenue by channel), and which traffic converts efficiently (RPS by channel). The answer you used to assemble across GA4 reports is simply there when it opens (computed on RS's own deduplicated tracking).

Open the RevenueScope dashboard and it looks like this (demo data):

In GA4 terms, the initial screen is the finished state of "Traffic acquisition + revenue column + hand-calculated RPS." Connect your ad accounts and it goes further — real ROAS by channel and saturation (how much headroom each channel has left). For which number should drive budget moves, see Three Kinds of ROAS: Which One Should Drive Your Budget?.

Build the viewing habit with GA4's three reports; automate when the assembly friction starts costing you. That's the realistic path to actually keeping your eyes on the numbers.

FAQ#

Frequently asked questions#

Q. Should I learn Explorations?

A. Not at first. Explorations are powerful — free-form tables — but they demand design knowledge. Build the habit on the three standard reports first; learn Explorations the day you need a combination the standard reports can't show. That order avoids burnout.

Q. What about consolidating in Looker Studio (the free dashboard tool)?

A. A solid option. It collects GA4 data on one screen and removes the menu tour. But the initial design — which metrics, arranged how — is still on you, and data quirks like the Direct problem carry over unchanged. Decide based on whether you have time to do that design yourself.

Q. Daily or weekly?

A. Depends on volume. At a few orders a day, daily numbers are mostly noise — weekly is fine. What matters more than frequency is checking the same three reports in the same order. With a fixed routine, anomalies stand out as "different from usual."

Conclusion#

Getting lost in GA4 comes from trying to read a general-purpose tool in full. For ecommerce revenue decisions you need three reports: Traffic acquisition (where from), Monetization overview (how much), and Landing page (which entrance). Build the habit of reading these three in the same order.

Once that's routine, check the revenue column in Traffic acquisition and divide by sessions to get RPS per channel. The moment you spot a "high-traffic, low-efficiency" channel is the moment GA4 stops being a screen you look at and becomes a tool you decide with.

Related articles#

• Why GA4 revenue doesn't match Shopify
• Three Kinds of ROAS: Which One Should Drive Your Budget?
• What Is RPS: The Metric, Formula, and How to Pull It in GA4
• 30-minute GA4 ecommerce setup checklist for Shopify

References#

• Google Analytics Help, "About Analytics sessions"
• Google Analytics Help, "About key events"
• Google Analytics Help, "About events in GA4"