Put a price tag
on every visit.
How much did one session earn? That's RPS. Price every channel — budget allocation becomes obvious. Starting today, your own AI analyst tells you how to grow your site.
Problem
Session counts
don't tell you where to put your ad budget.
Traffic grows, revenue doesn't — and more often than not the problem is how you measure, not what you ran. Four measurement traps EC teams hit every day.
CASE 01 — BOT64% of the traffic was bots
YouTube sessions spiked — roughly 1,650 on the surface. Most were crawlers hitting video descriptions; bot-filtered, only 600 were real. Scale the budget on raw counts and the misinvestment starts here. (Figures are from a demo environment.)
▶ RevenueScope: RPS is computed on real, bot-filtered sessions.
CASE 02 — DIRECT/NONEYour biggest channel is “unknown”
(direct) / (none) sits at the top of your GA4 report. When your largest source can't be attributed to anything, budget decisions stall.
▶ RevenueScope: Our tag on your own site records the source on the spot — nothing slips away.
CASE 03 — UTMYou have three “Instagrams”
“Instagram”, “instagram”, “IG”. UTM typos split one campaign into three rows, making each look smaller. Every report means merging them back together by hand.
▶ RevenueScope: UTM tags are automatically normalized.
CASE 04 — THREE SCREENSRevenue, traffic, ad spend — three screens
Traffic lives in GA4, revenue in your cart admin, ad spend in each ad platform. You hop across three services and stitch them together in a spreadsheet before "which channel earned what" even exists. Every report restarts that manual work.
▶ RevenueScope: Connects traffic, revenue, and ad spend in one line — RPS and ROAS per channel, on one screen.
What you need isn't session counts — it's revenue per session (RPS).
Same data, opposite budget decisions
Allocate by session count, or by revenue efficiency?
Last in sessions. But first in revenue per session.
AI Agent — MCP
Turn the AI you already use into your own analyst.Answers arrive without opening your laptop.
ChatGPT, Claude, Gemini, Copilot — the AI you already use reads your store's revenue data directly. On the train or on the shop floor — ask your phone "How were yesterday's sales?" and the answer comes back with the evidence. Reading the numbers and charts — and turning them into reports — you can now leave to the AI.
Q. Is my ad spend right? Where should I add budget? — ChatGPT: By RPS (revenue per session), Google Ads (¥120) slightly beats Yahoo! Ads (¥117) among paid channels. But your most efficient channels overall are email (RPS ¥345) and note (¥336) — strengthen those before adding ad budget. X comes last at ¥30.
Q. Does my budget split match revenue efficiency? — ChatGPT: There's a gap. X takes 31% of your budget but only 4% of revenue efficiency (RPS share). Email is the opposite: 3% of budget, 26% of efficiency. These two have the biggest room for reallocation.
Q. YouTube traffic is suddenly up! Should I add ad budget there? — Claude: Hold on. It looks like ~1,650 sessions, but 64% of that is bots (video-description crawlers etc.). Excluding bots it's 600 real sessions, 11 orders and RPS ¥66 — near the bottom of your channels. Skip the increase and check what's behind the spike first.
Q. Revenue dropped since last week. Why? — Claude: The -18% drop traces mainly to email-channel purchases (-31%). Sessions are flat, so the likely cause is the campaign content or offer — your ads are fine and don't need touching.
Q. Which pages should I fix to grow search traffic? — Gemini: Biggest upside: "skincare order" (rank 9.1 · 41,000 impressions) — just short of the top results. Next is "best whitening serum" (6.8). Improving these two articles is worth about +470 clicks/month.
Q. Are customers actually coming via AI? — Gemini: Yes. ChatGPT referrals drove 280 sessions and ¥128,000 in revenue over the last 90 days. Perplexity, Claude and Gemini also send traffic — a new acquisition surface worth watching. I can show which articles get cited, too.
Q. Update my weekly sales report (Excel) with this week's numbers. — Copilot: Done. This week: revenue ¥1,210,000 (+8% WoW). I've refreshed the channel breakdown table too — email is +15%, X is -12%. No more weekly copy-paste or re-pasting formulas.
Q. New vs returning — which drives revenue? — Copilot: Returning customers. New visitors are the majority of sessions (55%), but 65% of revenue comes from returning (RPS ¥171 vs ¥75 for new). Returning CVR is 6.8% — about 2.4× the 2.8% for new. You have enough new traffic; the upside is the first-purchase rate of new visitors.
Q. Mobile or desktop — who actually buys? — Copilot: Volume is mobile (70% of sessions); efficiency is desktop. Desktop RPS ¥200 is 2.2× mobile's ¥90, and CVR is 6.2% vs 3.8%. Mobile is the entry point, desktop is where purchases close. Cutting cart-to-checkout friction on mobile is your biggest revenue opportunity.
Product — Live Demo
Curious about the numbers? See them for yourself.
And of course, you can check the actual numbers too. Two views — Dashboard and Realtime — switch anytime.
This demo is live — every tab, filter, and period is fully interactive. Try it yourself.
Decide your ad-budget allocation
See ad spend and revenue efficiency (RPS) side by side per channel, and decide where to add or cut. Even tell whether a strong ROAS is new customers — or returning ones re-activating.
Read the column →Know which pages to fix — and grow
Rankings and target keywords surface the pages worth growing; dwell and exit data show the ones to fix. Your content to-do list, in order.
Read the column →Judge on real numbers, bots excluded
Bots are now 53% of all web traffic — more than humans (Thales 2026). We exclude them automatically, so you judge on human behavior only.
Read the column →See what's happening right now
Watch visits, carts, and purchases the moment they happen — catch campaign reactions and sale momentum live.
Read the column →Now, just try it on your own site.
See the metrics from the demo — on your own data.
How It Works
Traffic, revenue, and ad spend — connected in one line, automatically.
Record where visitors come from
A lightweight tag (~2KB gzipped) records UTM parameters, referrers, and entry sources automatically. Naming variants are normalized — channels stay clean.
Pull in revenue and ad spend
Revenue comes from the same dataLayer purchase events GA4 uses — no extra setup. Ad spend arrives via a read-only Google Ads connection, with manual entry for other platforms.
Compute contribution by channel
LINE: ¥1,080,000
Google Search: ¥500,000
See which channel earns what — and whether it justifies its ad spend.
Comparison
The role of each analytics tool
GA4 and ad-measurement tools each play their own role. RevenueScope doesn't compete with them — it complements them, owning the revenue-first question of where to invest next.
RevenueScope | GA4 | Search ConsoleSC | AdAd performance toolAd tool | |
|---|---|---|---|---|
| Focus | Ad budget allocation | On-site behavior | Search performance | Ad conversion tracking |
| Base metric | Revenue | Traffic | Search queries | Ad clicks |
| Signature metrics | RPS / AOV / cross-channel ROAS | Sessions / conversions | CTR / position | CPA / ROAS (own network only) |
| Bot filtering | Behavioral detection, automatic | Known bots only | — | Ad-click fraud only |
| Ad spend intake | Connected + manual entry | — (manual import) | — | Own network only |
| Data freshness | Realtime (incl. revenue) | Realtime (basic only) | 2–3 days | Hours |
| Setup time | ~5 minutes | Medium–high | Low (Google link) | Per network |
| Ad contribution | 4 attribution models | — | — | — (own network only) |
* How ad networks' invalid-click filtering differs from bot exclusion (billing vs analytics) — see the column.
Onboarding
Live before your coffee cools.
Connect your data
Add one tag to your site — no code edits required. Linking Search Console and Google Ads takes a few clicks, anytime.
Ask the AI you already use
Connect RevenueScope to ChatGPT, Claude, and Gemini. Then just ask, “What should I fix to grow?”
No expertise needed. Starting today, your EC gets its own dedicated analyst.
Pricing
One ad-budget mistake. That's the price.
Up to 5,000 sessions/month, your AI analyst stays free. Upgrade when your site grows.
Free
Start here (free forever)
/month (ex. tax)
5,000 sessions/month
- ✓Unlimited members
- ✓1 site monitored
- ✓14 months data retention
- ✓No credit card required
Starter
For small-scale EC sites
/month (ex. tax)
10,000 sessions/month
- ✓Unlimited members
- ✓1 site monitored
- ✓14 months data retention
Growth
For growing EC sites
/month (ex. tax)
50,000 sessions/month
- ✓Unlimited members
- ✓5 sites monitored
- ✓24 months data retention
Scale
For high-traffic sites
/month (ex. tax)
200,000 sessions/month
- ✓Unlimited members
- ✓10 sites monitored
- ✓36 months data retention
✓ Every plan includes: all features (AI analyst integration, dashboard, realtime)
* Session counts are based on real human visitors with bots excluded. RevenueScope filters bots automatically, so counts run lower than bot-inclusive tools like GA4 (by design). * Usage fees for AI services themselves (ChatGPT, Claude, Gemini) are not included — they run on your own AI account. Connecting them to RevenueScope is free on every plan.
FAQ
Frequently asked questions
GA4 focuses on measuring and reporting traffic. RevenueScope starts from revenue data and computes revenue efficiency per ad (RPS/AOV). It answers "which ad generates how much revenue" — a question GA4 can't. The two are complementary.
Yes. RevenueScope reads purchase events from the same dataLayer that GA4 uses, so your existing GA4 setup keeps working with no extra configuration. RevenueScope also works standalone if GA4 isn't installed.
Effectively no. The tag is about 2KB gzipped — far smaller than GA4 — and loads asynchronously, so it doesn't block page rendering.
Yes. Just add a single tag through the GTM admin panel. No need to edit your site's HTML directly.
No. Add one tag from the admin panel and you're done. No HTML edits, server configuration, or any technical work required.
Any EC site that can install GTM or a custom script. Contact us to confirm compatibility with your platform.
RevenueScope's own tag captures purchase events from dataLayer in realtime. GA4 has a 24-48 hour delay, but RevenueScope's own measurement appears on the dashboard within seconds.
OSS tools (Matomo, PostHog, Umami) and GA4 + Looker Studio builds are technically possible, but turning them into a usable revenue dashboard takes engineering and ongoing operations. RevenueScope installs in 5 minutes via a single tag and shows the 4 core metrics (Revenue / AOV / RPS / CVR) plus Sessions in a 5-KPI card layout out of the box. A detailed comparison post is coming soon.
Visitor session data (source, page views, device type) and order amount on purchase events. Personal information such as names and email addresses is not collected.
We use first-party cookies to manage an anonymous visitor ID and a session ID. Sessions end automatically after 30 minutes of inactivity. No third-party cookies are used.
Retention depends on the plan. Free & Starter: 14 months, Growth: 24 months, Scale: 36 months.
Yes. Up to 5,000 sessions/month, all features (ask AI) are unlimited and free forever. No credit card required. You only move to a paid plan once your site grows past that limit.
RevenueScope's AI integration (MCP connection) is included at no extra charge on every plan, including Free. The AI services themselves — ChatGPT, Claude, Gemini — are billed under your own contract with each provider (connecting external tools may require their paid plans). RevenueScope does not cover or resell AI service fees.
Yes. Cancel anytime — no cancellation fee. You keep access until the end of the current billing period. Data is kept for 30 days after that, then deleted.
We currently offer only monthly plans. Annual plans may be added based on demand.
Simply remove the tag from the admin panel — tracking stops immediately, with zero impact on your site.
Contact us. For EC operators well beyond 200,000 sessions/month, an enterprise plan is available. We handle multi-site setups, large session volumes, and custom support arrangements.
RPS (Revenue Per Session) = revenue ÷ sessions, a measure of how efficient each ad is at bringing in revenue. AOV (Average Order Value) = revenue ÷ orders. With RPS you evaluate "which ad is efficient", with AOV you evaluate "order quality / ticket size". Combined with CVR, you get three angles on ad investment — shift budget from low-RPS to high-RPS ads and maximize revenue within the same spend.
RevenueScope treats RPS (Revenue Per Session) as the most important metric. High CVR with low ticket size or thin traffic still won't grow revenue. RPS is the single metric where acquisition efficiency and customer value multiply together — it tells you whether a site is actually making money. CVR and session count are intermediate metrics that support diagnosis but, on their own, are not a basis for ad-investment decisions. RevenueScope places RPS at the center and decomposes ad efficiency through the 4 core metrics — Revenue, AOV, RPS, and CVR.
No — high CVR with low ticket size can still mean poor ROI. RPS and AOV together let you evaluate both acquisition efficiency and purchase quality at once, which is what you need for real budget decisions.
Session and purchase events appear on the dashboard within seconds — effectively realtime.
From each buyer's ad-touch history. Four models are available: full credit to the last touch, full credit to the first touch, equal split across all touches, or higher weight toward the touches closest to purchase. Pick the question you want answered, and the model switches automatically.
RevenueScope is focused on revenue efficiency by ad channel (Revenue / AOV / RPS / CVR — 4 core metrics, plus Sessions in a 5-KPI card layout). For integrated management of gross margin, LTV, inventory, and CRM, we recommend pairing it with other tools (Shopify Analytics / BI tools / CRM SaaS). Use RevenueScope as a lightweight dashboard for daily ad decisions.
Yes. Based on channel-level RPS / AOV / CVR, the AI analyst recommends how to improve your budget allocation. On top of that, a read-only Google Ads connection (manual entry for other platforms, with more APIs to follow) brings in your actual spend — going beyond "which channel earns efficiently" to checking whether your current allocation matches revenue efficiency. RevenueScope never manages ad delivery (bidding or campaign changes) — the final action is always your call.
About
Judge by revenue.Compound your time.
Most EC operators judge their ads by intermediate metrics — CVR, sessions, click-through rate. But those correlate weakly with actual revenue. Revenue First is the philosophy of evaluating ad efficiency from revenue, with RPS (Revenue Per Session) = revenue ÷ sessions as the single most important metric — the one number where acquisition efficiency and customer value multiply together to tell you whether a site is actually making money. RevenueScope puts RPS at the center and lines up revenue, AOV, CVR — and the ad spend you're actually deploying — on one screen, so you can judge whether today's budget split matches revenue efficiency.
The second philosophy became possible only now that your AI is connected. Reading the numbers, interpreting charts, compiling reports, hopping between admin screens — that is no longer human work. Leave the expertise to AI; spend your time on judgment and creation. More than an analytics tool, RevenueScope exists to build that kind of working environment.
Working hours are a slice of your life. Getting paid for busywork is trading lifespan for money — and no job truly pays what a lifespan is worth. What balances the trade is the experience you gain. So put the recovered time into your products, your customers, your most creative work. Experience compounds. That is the investment of time RevenueScope advocates.
RevenueScope is a Japan-born EC analytics SaaS designed from these beliefs — revenue-first judgment and work left to AI, built into a single tool.
— RevenueScope (operated by AltPilot — Founder Toshihiro Shishido)
Founder & Operator
As an executive — moving businesses with numbers
Over a decade as a board member or executive across three university spin-out startups, leading zero-to-one businesses. Fundraising in the hundreds of millions of yen, business planning, investment decisions — a career spent deciding where limited budgets should go. RevenueScope's revenue-first judgment was born on that front line.
As a data scientist — turning analysis into decisions
At Thomson Reuters, led research-management analysis for government agencies and national research institutes — data visualization, KPI design, multivariate analysis. The job was translating mountains of numbers into the next move. Prescriptions over charts: that's where RevenueScope's design begins.
As an engineer — handing human chores to machines
Built RPA, machine-learning models, web crawlers, and OCR pipelines for one of the world's largest legal-tech companies — design through implementation, end to end. RevenueScope's belief in leaving busywork to AI is something I've been building with my own hands for years.
Bring
channel-level answers to your next budget meeting.
No credit card. Tracking starts the moment you paste the tag — from the very first order, you see where revenue comes from.