Live concurrents
See exactly how many readers are on every story right now — updated every second, never a stale refresh.
PageView.ro streams every reader, story and source into one live board — so your newsroom can act on momentum while it's still building, not after it has peaked.
Sample data from a demo newsroom.
Newsrooms running PageView.ro in production
Over 40,000 pageviews a day, measured in real time.
Six live views, one purpose: help editors decide what deserves the front page in the next five minutes.
See exactly how many readers are on every story right now — updated every second, never a stale refresh.
Spot what's taking off before it peaks. Movers surface the stories accelerating fastest across the desk.
Search, social, direct, internal — plus Google Discover, Google News and AI assistants as their own named channels.
Attribute attention to the newsroom. See which desks and bylines are landing, hour by hour.
One tiny async script. No cookie-banner drama, no render-blocking, no bloat — it just streams.
No cookies, no raw IP stored, no cross-site tracking. EU-hosted ingest with a published DPA.
Explore the board the way an editor does — switch between what's live right now, where readers are coming from, and who they are. Click a view.
Sample data from a demo newsroom.
Five things we do that general-purpose tools don't — because they were never built for publishers.
An optional marker in your article HTML reports back when an aggregator or scraper serves your story from their own domain — the host, the copied URL, and how much attention it took.
Chartbeat, GA4 and Plausible measure only your own pages, so a copy hosted elsewhere is invisible to them.
ChatGPT, Perplexity, Google Discover and Google News arrive as their own traffic sources, split per story — not folded into a generic “referral” bucket you have to reverse-engineer.
GA4 needs hand-built channel groups, and Discover only shows up in Search Console — never in your live view.
GPTBot, ClaudeBot, Bytespider and headless automation are identified and reported separately, on their own retention, without ever polluting your editorial numbers.
Every other tool silently discards bot traffic, so you cannot tell who is training on your archive.
A plugin puts per-article numbers where your editors already work: a Traffic column in the posts list, today's readers in the toolbar, a dashboard widget, and live figures in the post editor.
The API key stays server-side in WordPress and never reaches the browser.
Set a readers-now threshold and a winning story can republish itself to your partner sites, or go out to your own Facebook pages — automatically, or from a button on the live board.
Chartbeat, GA4 and Plausible are read-only measurement products; none of them can act on what they measure.
Every other tool stops at a number. Here the number leads to a decision you can execute without leaving the board — because the same suite that measures your site also publishes to it.
Per-article traffic appears inside wp-admin — a Traffic column in the posts list, today's readers in the toolbar, live figures in the editor. Not a separate tab your desk forgets to open.
The live board shows the moment a story stops climbing — momentum, engaged time, scroll depth and the source split, per article, second by second.
Repost it to your Facebook pages from that same row — immediately, or in the next free slot of your own schedule. No copy-paste, no second tool, no leaving the board.
What we don't claim: we don't measure how many readers a given repost brought back. Those visits return as ordinary Facebook traffic, in the same bucket as any other share — we don't attribute them per repost. What you get is the decision moment and the action next to it, not a number we can't stand behind.
Add one ~2.5KB snippet to your template, or install the WordPress plugin. Events start flowing in seconds.
Concurrents, momentum, sources and authors light up the moment readers arrive — no setup, no dashboards to wire.
Promote, re-headline, re-package — while the story is still climbing, not after it has already peaked.
PageView.ro is a realtime web-analytics platform built specifically for newsrooms. It streams every reader, story and traffic source into one live board so editors can act on a story's momentum the second it starts building — a modern, privacy-first alternative to Chartbeat.
Google Analytics is built for marketers and reports on sessions after the fact. PageView.ro is built for editors and reports in real time: live concurrents per story, a momentum ranking of what's accelerating, and traffic-source splits updated every second — plus a newsroom-specific view of authors and categories.
Typical p99 ingest latency is under 50 milliseconds, and a new story appears on your live board within about 8 seconds of its first pageview.
No. The PageView.ro tracker is a single asynchronous JavaScript snippet of about 2.5KB gzipped. It loads without blocking rendering and sends data in the background, so it has no measurable impact on page performance or Core Web Vitals.
Yes. PageView.ro is GDPR-safe by design: it collects no personally identifiable information, performs no cross-site tracking, requires no cookie banner, hosts its ingest in the EU, and provides a documented DPA.
Add one snippet of about 2.5KB to your site template. Events start flowing to your live board in under 8 seconds — there are no dashboards to configure and no data warehouse to wire up.
Yes, and it goes further than a snippet. The Next Stage Analytics plugin puts per-article traffic inside wp-admin — a Traffic column in the posts list, today's readers in the toolbar, a dashboard widget and live figures in the post editor — and it also feeds the tracker authoritative author and category values from WordPress itself, so the leaderboards don't depend on guessing from your theme. The API key stays server-side and never reaches a reader's browser.
It can repost an already-published article to your own Facebook pages, either immediately or in the next free slot of your publishing schedule, triggered by an editor from the article row on the live board. It requires WordPress with the Next Stage Cross and Next Stage Schedule plugins and connected Facebook pages. It is manual, not automatic, it is Facebook-only, and the resulting visits arrive as ordinary Facebook referrals — PageView.ro does not attribute traffic to an individual repost.
Yes. PageView.ro is built for multi-title publishers: each site gets its own live board, and a network overview aggregates readers, traffic and top stories across every title you have access to, with author and section leaderboards per site.
PageView.ro is invite-only during early access. Tell us about your newsroom and we'll get back to you within two working days.