"I finished setting up GA4 ecommerce for my Shopify store, but where do I actually look to make decisions?" This is the most common question I get right after a GA4 ecommerce setup is completed.
GA4's report screen fills up with menus: Monetization, Acquisition, Conversions, Ecommerce Purchases. The data is there. The signal worth acting on is not always obvious. This article walks through how to read the numbers and turn them into ad decisions in four ordered steps — the WHAT and WHY after the HOW.
TL;DR
- Three metrics carry the post-setup analysis: RPS (Revenue Per Session), AOV (Average Order Value), CVR (Conversion Rate)
- Shopify admin shows absolute revenue. GA4 shows source-level breakdown. RPS unifies both into one comparable number
- Four ordered steps: ① Overall RPS → ② Channel RPS → ③ AOV/CVR split → ④ Next-month budget allocation
- Three logic traps that trip up the read even when setup is perfect: CVR-only judgment, site-wide AOV, sessions-as-success
1. Three Metrics That Matter After Setup
After GA4 ecommerce setup is complete, the metrics worth focusing on narrow down to three: RPS, AOV, CVR.
| View | Metrics visible | Strength | Weakness |
|---|---|---|---|
| Shopify Admin | Total revenue / orders / AOV | Absolute final results | No channel breakdown |
| GA4 | Channel sessions / purchases / revenue | Channel-level comparison | Revenue gap vs Admin |
| RPS (unified) | Revenue per session | Cross-channel efficiency | Requires calculation |
A "revenue +20% MoM" line in the Shopify admin panel does not tell you whether AOV rose, sessions grew, or CVR improved. Even GA4's source breakdown shows the relationships, not the next move.
RPS makes the decision concrete. "Google Ads RPS dropped from $1.20 to $0.98" tells you acquisition efficiency is degrading — likely from creative fatigue or traffic-quality decay. Pair it with AOV and CVR to narrow the root cause further.
2. Revenue Analysis in 4 Ordered Steps
Post-setup analysis works better with a fixed order. Run the same four steps every month and decision quality and speed both step up.
| Step | What to look at | GA4 location | Next action |
|---|---|---|---|
| 1 Overall RPS | Revenue per session | Monetization + Acquisition Sessions | Compare vs industry median |
| 2 Channel RPS | Channel-level efficiency | Acquisition default channel group | Rank by RPS |
| 3 AOV / CVR split | Root cause of decline | Custom report | Audience vs LP fix |
| 4 Next-month budget | Reallocation priority | Dashboard summary | Scale / Hold / Cut |
A concrete example: compare "Meta RPS $0.80, AOV $60, CVR 1.3%" against "Organic Search RPS $2.20, AOV $80, CVR 2.75%." Meta is low on both AOV and CVR — the creative is pulling a low-value audience that also fails to convert. Audience pivot (new creative) before LP tweaks is the right call. This kind of decision drops out naturally when you run the four steps in order.
3. Three Logic Traps in Reading the Numbers
Even with a clean setup, three logic traps in reading the numbers themselves trip up many teams.
| Pitfall | Example | Blind spot | Correct metric |
|---|---|---|---|
| 1 CVR-only judgment | Cut Meta budget at CVR 0.8% | AOV difference | RPS-based judgment |
| 2 Site-wide AOV | Whole-site AOV $75 | Per-channel AOV gap | Channel-level AOV |
| 3 Sessions = success | Meta 10,000 sessions/mo | Inefficient spend | RPS × Sessions = revenue |
Pitfall 3 is the one I see most often in stores with clean GA4 data. "We have so much traffic from Meta" feels like success, but if Meta RPS is half the Organic Search RPS, half that budget is going to "buy session count" rather than revenue. Treat absolute counts with suspicion when you have RPS available.
4. ROAS vs RPS — When to Use Which
"Why not just use ROAS?" comes up often. ROAS (Return on Ad Spend) is critical for ad investment but only works on channels with known spend. Organic Search, Direct, and Referral have no defined ROAS.
The practical pattern: use RPS for the whole picture, ROAS for paid channels only. The two play complementary roles — RPS judges acquisition efficiency across the funnel, ROAS judges return on each paid dollar.
5. Next Step — Turn GA4 Setup Into Revenue Decisions
Manually computing channel-level RPS in GA4 every month takes 30–60 minutes per cycle. Over time the work becomes a chore, leading to "skip analysis this month" → "ad decisions revert to gut feel" — a classic failure pattern.
RevenueScope auto-visualizes channel-level RPS, AOV, and CVR from your GA4 ecommerce data. If GA4 ecommerce is already set up, installation takes five minutes with no extra config. Revenue, AOV, RPS, and CVR — the four core metrics, plus Sessions on the dashboard for a 5-KPI card layout — let you run the four steps with zero manual work every month.
What is your monthly cadence for reading GA4 ecommerce data? Do you run a fixed order of steps, or open whatever feels relevant first? I'd love to hear how other teams structure the post-setup analysis loop.
Top comments (0)