Product/Analytics
Every reader counted, in real time
The measurement behind every figure: the edge network counts on the server – every reader, not only those who let scripts through – the site's own script measures the reading, and VOR Search shows what readers look for and do not find.
Real time
Every reader, counted on the server
VOR Analytics counts at the edge, before any script: every user, page view, hour and section – including the readers who block scripts and whom tag-based analytics never see.
The last 30 minutes
Updated every fifteen seconds: users in the last hour, page views, active for five full minutes, visits, requests, pages per user, users per minute, page views per device, country, page and section. The shaded bars are the last minutes, filled in afterwards.
Against the same time yesterday
Every figure compared with the same minute the day before – a drop shows at once, not in tomorrow's report.
Periods on top
Today, yesterday, 7, 14, 30, 90 days, this year – the same page, the same figures as in Studio's overview, in the Insights connection and in Ask VOR.
Devices, countries, sections
Where the readers are, on what, reading which section – for the period you choose.
No cookie banner needed for the count
The server count needs no script and no consent to count a page view – the reading measurement and any third-party tools stay your choice.
Pages that stop answering
Monitoring watches response times and pages that stop responding, minute by minute, and raises the alarm in the order queue.
Own measurement
How they read, not only how many
The site's own script measures what the edge cannot see: active read time, depth, shares, clicks and sources – per article and section.
Read time and depth
Active seconds and how far the reader got, per article – the figure behind “Read time” in Studio's overview.
Shares and clicks
Most shared, buy clicks per article, clicks on related – what the reader did next.
Sources
Search, social, direct, newsletters, the app – per article and section.
Third-party analytics beside it
Google Analytics can be shown next to the own figures, with the caveat that it only sees users who let the script through. Read the three together: the edge for how many, the own script for how they read, the third party for comparison with other sites.
Games, engagement, the app
Quizzes, tools and the reader app have their own pages with the same period choice; apps that live only on the phone send nothing to the server.
Per language
Page views per language over the last seven days – every language version measured on its own.
VOR Search
What readers look for – and do not find
The site's own search engine, the same hits and order as the search box, across every language you publish in.
The reader's own words
The search box is the only place where a reader states their need in their own words. A keyword without hits is a reader already on the site, looking for something not yet written – the shortest way to an article with an audience before it is written.
The Searches page
The twenty most searched, the words, searches per day, from search to article.
Without hits → suggestions
Keywords without hits become suggestions in Best ideas and the order queue, matched to approved stores where there is a business case.
Fast, everywhere
The index is served from the edge, so search answers in milliseconds in every language – on the site, in the app and in Studio's own search.
Tag search and Read also
The same index drives the reader's way onward – which is why no article is published untagged.
In the API and the connections
Search is an operation in the API and a tool for the agents, so an assistant can find the article before it suggests a headline.