CEDX Web Analytics · Marketing
Overview cards, a realtime view with 412 people on the site right now, and a session ledger where every row opens — channel, landing page, duration, device, conversion, revenue. And a health score that watches the tracking itself.
Checkout conversion fell 18% last week. The alert already knows why: payment-step errors rose after a 15-minute CDN incident, and it says so.
Runs on demo data. The chrome reads stream lag ~2s · demo seed.
What it is
412 active users, 18 events a minute, and a 30-minute strip of users per minute. The geo mix reads US 62%, Canada 11%, UK 8%; the top pages right now are the homepage at 184, shell jackets at 96, and checkout at 48 — which means 48 people are deciding this second.
The 400-row sample ledger shows started, channel, landing page, pages, duration, device, conversion and revenue. One social session viewed 10 pages in 1 minute 18 seconds and converted at $460. Aggregates are computed from rows like that — rows you can read.
Tracking health reads 91 — two missing events, seven slow pages, bot share 3.4%. Because when the tag lies, every downstream number is a negotiation. The alerts carry causes: bounce on the sale page climbed to 54% because the ad promised 30% off and the hero still shows full price.
Product tour
Not a mockup and not a concept deck. This is what opens at /app/web-analytics.
01 — Overview
Sessions by channel: organic 62,400, paid 41,200, direct 31,800, social 18,400, email 14,200. Page signals pair conversion with bounce — checkout converts 38.2% with 12.4% bounce while a campaign landing converts 11.3% with 56.6% bounce. Same chart, opposite health.
02 — Realtime
The realtime screen is where a launch gets watched: active users ticking, the per-minute strip bending, three conversions in the last five minutes split between purchase and sign-up events.
03 — Sessions
Filter to converted and the ledger becomes 76 receipts: a referral session that browsed base layers and spent $179, an email session that went straight to a product page and took 6 minutes 44 seconds to decide.
Who runs it
Roles, not references. We have no named customers yet, so nobody in these photographs is quoted, credited or claimed as one.
Reads the overview and the page signals, and walks into the meeting with the cause, not just the delta.
sessions · 186.4K
Watches paid sessions against conversion rate, and catches the landing page whose promise does not match the ad.
paid · 41,200 sessions
Owns tracking health — the two missing events and the seven slow pages are a work queue, not trivia.
health 91 · 2 missing eventsThe shape of it
Every figure below is legible in the captures above. Nothing here is a projection of your estate — it is the state of the demo data.
How it runs
The tracking itself is scored — missing events, slow pages, bot share — before any traffic number is trusted.
Overview trends the month; realtime watches the minute. Both read the same stream.
Alerts arrive with causes — the CDN incident, the mismatched sale hero — not bare deltas.
Revenue is attributed per channel in the demo model, labelled as a model on the card itself.
One record
The sessions being measured are the ones the rest of the estate creates — same channels, same pages, same campaigns.
The URLs in the page-signals table — section scores and session data read the same visits.
CEDX CampaignsThe campaigns behind the paid channel rows, with cost per lead at the other end.
CEDX SEOThe organic rows behind the rankings — sessions next to positions.
CEDX Product AnalyticsWhat those same people do after they sign up — the other half of the funnel.
Limits
Finding this out on the third call is worse for you than reading it here, and worse for us.
Start
Open it right now
Your site, your events
Analytics with the rest of it
Questions
Yes. Every screenshot is a capture of the running build and you can open the same build at /app/web-analytics. The chrome reads stream lag ~2s · demo seed.
A score on the measurement itself — two missing events, seven slow pages, 3.4% bot share on the demo. When the tag degrades, the score drops before your reports quietly rot.
Yes. The ledger sample shows each session's channel, landing page, page count, duration, device, conversion and revenue — 400 rows in the demo, with a converted filter that returns 76.
From the attribution model — and the card says demo model on itself. It demonstrates how attributed revenue reads per channel; it is not a claim about your numbers.
No certification has been issued. What we can evidence about hosting, encryption, tenant isolation and production access is written up on the security page.
Live build, demo data, no card. Then ask what your tracking-health score would read.