A lot of e-commerce operators run ¥300,000/month ($2K) in ads and cannot answer "which ad, for how much revenue" on demand. If you've ever opened GA4, clicked around a few times, and sighed — this article is a handhold out.
The conclusion up front: the reason "which ads drove revenue" isn't visible in GA4 isn't misconfiguration. GA4 is fundamentally a tool to optimize site structure, not to see revenue directly.
Key takeaways#
- GA4 is a site-structure optimization tool. It's not designed to see revenue directly
- CVR is an indirect metric of revenue. CVR going up without revenue going up happens all the time
- E-commerce operators need both indirect metrics (site health) AND direct metrics (revenue breakdown)
1. GA4's real purpose is site-structure optimization#
GA4 is excellent as a behavioral analytics tool. Pageviews, sessions, bounce rate, engagement time, and conversion rate (CVR) — all optimized for recording and aggregating user behavior.
With these metrics you can answer:
- Which page has the highest exit rate?
- Where does funnel drop-off occur?
- Which UI change improved CVR?
- What's the UX gap between mobile and desktop?
In short: GA4 tells you "how to fix site structure so users buy more easily." For measuring the effect of LP revamps, checkout-form optimization, and product page improvements, it's overwhelmingly strong.
But what e-commerce operators actually want to know is a different question entirely:
"Yesterday I spent ¥50,000 on Instagram Ads. How much of that came back as revenue?"
"Between search ads and display ads, which is actually profitable?"
These questions live on a different layer than site-structure optimization. They're asking about the relationship between ad channels and revenue — not about where users drop off.
No matter how many times you click through the GA4 screen, there's no one-shot answer to this question. GA4 was never designed to answer it.
2. CVR is only an "indirect metric of revenue"#
Pause for a moment on CVR as a metric.
The CVR that marketers chase daily is an indirect metric of revenue. CVR going up tends to correlate with revenue going up, but it's not a direct causal relationship.
Things like this happen all the time:
- CVR improved but revenue dropped. A form revamp took CVR from 3% to 4%, but traffic dropped and actual purchase count fell
- CVR dropped but revenue rose. A new ad channel doubled sessions; CVR fell from 2% to 1.5%, but revenue grew 1.3x
- CVR flat but revenue mix distorted. Same total, but high-AOV products stopped selling while low-AOV ones surged
You don't catch any of these if you're only watching CVR. CVR is a "ratio of how well the site converts within itself," not "how much revenue was earned."
Put differently: CVR is a good metric for site-structure health but insufficient as a business-health metric. To measure business health, you need a separate direct metric: "which channel earned how much revenue."
3. Both indirect and direct metrics#
Summing up so far, e-commerce operators need two axes of metrics.
| Axis | Metric | Question it answers | Primary use |
|---|---|---|---|
| Indirect | CVR, bounce rate, engagement time, etc. | Is the site structure working? | LP revamp, form optimization, UX improvement |
| Direct | Revenue by channel, RPS (revenue per session), AOV (average order value) | How much did each ad/channel earn? | Ad budget allocation, channel ROI evaluation |
GA4 excels at the left side (indirect metrics). It's genuinely strong in this domain. For running site-improvement PDCA, GA4 mastery is arguably mandatory.
The problem is most e-commerce operators try to answer the right-side questions (direct metrics) with GA4 alone. Turning on GA4's e-commerce integration does surface revenue numbers, but to reach "see ¥300K of ad spend broken down by channel every day, at a glance," you have to hand-build several exploration reports. That's high operational overhead — and the net result is that people fall back to "just glance at CVR" mode.
"CVR is up, revenue isn't." If this sounds familiar, you're not using GA4 badly — you're just missing a separate lens for direct metrics.
4. How RevenueScope fills the "GA4 blind spot"#
A short note about the tool I'm building.
RevenueScope is a web-analytics service for e-commerce operators, specifically focused on visualizing "ad channel × revenue" on a single screen. Its relationship to GA4 is not competitive — it's complementary. GA4 covers site-structure optimization (indirect metrics); RevenueScope covers channel-level revenue contribution (direct metrics). Clean role separation by design.
- Just install one tag. GTM or raw HTML, no engineering required
- Sessions, revenue, RPS, AOV, CVR by channel — all on one screen
- Zero extra setup if GA4 e-commerce is already configured
- Multi-touch attribution built in
You don't need to abandon GA4. Keep using GA4, and just put a second screen for direct metrics next to it. That's the simplest honest answer I can offer right now.
If you're running even ¥200K/month in ads, a daily view of "which channel earned what" is infrastructure, not luxury. Time spent flipping through GA4 screens is better reinvested in ad-creative iteration — that's where the lever is for the business.
See which ads actually drive revenue, at a glance
14-day free trial. No credit card required. Up and running in 5 minutes.
Start 14-day free trial