Skip to main content

reference

The dashboard, explained

Every view in Vero: what it is, what it is for, how to configure it, and what each number means. Read top to bottom or jump to what you need.

Analytics

Overview

Visitors
14,724
+112% better
Revenue
€18,423
+34% better
Revenue per visitor
€1.25

14,724 over the period

Visitors, peak 3,420
Figures from the Vero demo, a fictional SaaS on myapp.com.

What it is

The home of your dashboard. A strip at the top reads the last 24 hours against a typical day for your site, with the day's anomalies and deploys. Below it: headline KPIs (visitors, revenue, revenue per visitor and bounce rate, plus conversion once you mark a primary goal) with trend sparklines, a visitors-over-time chart with your deploys and anomalies marked on it, and the live event feed.

What it is for

It answers the first question every morning, whether anything unusual is happening, and then whether the week is up or down and why. Every card is clickable to filter the whole dashboard to that slice.

How to configure

Use the period switch (24H, 7D, 30D, 90D) or a custom date range in the top bar; every view respects the same range. On 24H the chart shows the last 24 hours by the hour, with a typical day drawn over them as a dashed line: the same 24 hours, averaged over recent weeks.

Key metrics

Live visitors
Unique people active in the last five minutes.
Visitors
Unique people in the period, counted cookie-free with a daily-rotating hash.
Pageviews
Total pages loaded, including repeat views by the same person.
Sessions
A visit: one continuous burst of activity that ends after 30 minutes idle.

Pages

Top pages

/
pageviews8,421
started here3,320
ended here1,380
time on page41s
scroll62%
/pricing
pageviews4,108
started here640
ended here960
time on page1m 36s
scroll77%
/docs
pageviews3,527
started here910
ended here1,390
time on page2m 48s
scroll70%
/blog/cookie-free-analytics-2026
pageviews2,841
started here1,110
ended here1,020
time on page3m 34s
scroll81%
/changelog
pageviews1,290
started here410
ended here520
time on page1m 13s
scroll58%
PagePageviewsStarted hereEnded hereTime on pageScroll
/
8,421
3,320
1,380
41s
62%
/pricing
4,108
640
960
1m 36s
77%
/docs
3,527
910
1,390
2m 48s
70%
/blog/cookie-free-analytics-2026
2,841
1,110
1,020
3m 34s
81%
/changelog
1,290
410
520
1m 13s
58%
Figures from the Vero demo, a fictional SaaS on myapp.com.

What it is

Every URL on your site ranked by traffic, with entry and exit pages. Switch the list to money to see the revenue each entry page brought. A page’s detail shows where its visits came from and where they went next, inside the same visit.

What it is for

Shows which content actually works. Pair a high-traffic page with low revenue and you have found a page to fix.

Sources

Referrers

visits
news.ycombinator.com3,420
google.com2,876
twitter.com1,245
producthunt.com987
github.com612
reddit.com/r/SaaS421
chatgpt.com240

UTM sources

visitors
(direct)3,987
producthunt1,632
twitter1,245
newsletter743
google612
reddit421
chatgpt240
Figures from the Vero demo, a fictional SaaS on myapp.com.

What it is

Where visitors come from: direct, search, social, and referrals, broken down by referrer and UTM campaign.

What it is for

Acquisition lives here. Ranking channels by revenue instead of clicks tells you where the next euro of budget should go.

How to configure

Nothing to set up: it reads the referrer and UTM tags of every visit.

Revenue

Traffic and revenue by referrer

news.ycombinator.com
Visitors3,420
Revenue€7,124
Per visitor€2.08
twitter.com
Visitors1,245
Revenue€4,821
Per visitor€3.87
google.com
Visitors2,876
Revenue€2,783
Per visitor€0.97
producthunt.com
Visitors987
Revenue€1,845
Per visitor€1.87
github.com
Visitors612
Revenue€968
Per visitor€1.58
chatgpt.com
Visitors240
Revenue€400
Per visitor€1.67
ReferrerVisitorsRevenuePer visitor
news.ycombinator.com
3,420
€7,124
€2.08
twitter.com
1,245
€4,821
€3.87
google.com
2,876
€2,783
€0.97
producthunt.com
987
€1,845
€1.87
github.com
612
€968
€1.58
chatgpt.com
240
€400
€1.67

Profit by source

news.ycombinator.com
Revenue€7,124
Cost€0
Profit€7,124
twitter
Revenue€4,821
Cost€1,200
Profit€3,621
producthunt
Revenue€1,845
Cost€0
Profit€1,845
google
Revenue€1,783
Cost€1,400
Profit€383
google.com
Revenue€1,000
Cost€0
Profit€1,000
github.com
Revenue€968
Cost€0
Profit€968
newsletter
Revenue€482
Cost€900
Profit-€418
chatgpt
Revenue€400
Cost€0
Profit€400
reddit
Revenue€0
Cost€1,150
Profit-€1,150
SourceRevenueCostProfit
news.ycombinator.com
€7,124
€0
€7,124
twitter
€4,821
€1,200
€3,621
producthunt
€1,845
€0
€1,845
google
€1,783
€1,400
€383
google.com
€1,000
€0
€1,000
github.com
€968
€0
€968
newsletter
€482
€900
-€418
chatgpt
€400
€0
€400
reddit
€0
€1,150
-€1,150

Revenue by campaign

No campaign€9,492
launch_week€6,666
brand_search€1,783
spring_launch€482
Figures from the Vero demo, a fictional SaaS on myapp.com.

What it is

Money, attributed. Total revenue over time, and a traffic and revenue table you group by source, channel, campaign, referrer or entry page, with visits, revenue, revenue per visit, sales, average order and conversion on each row. How long they take to pay shows the typical wait from the first page of the visit to the sale, by bucket and by source. A Pro card puts the source that found a customer beside the one that closed the sale, from 5 sales with a visit on record. With no cookies it links the visits of one day and repeat purchases by the same customer id, so someone who comes back on another day before buying cannot be linked. A page’s detail adds the revenue from visits that saw it.

What it is for

This is the number the business is measured on. Revenue attribution reorders every other metric around what actually pays.

How to configure

On the Connect your sales screen, in the sidebar, paste the webhook URL into Stripe, Lemon Squeezy or Paddle and its signing secret into Vero, then turn on the tracker’s checkout module so each sale arrives with its visit. A checkout you build yourself sends each sale to the ingest endpoint with the session id instead. Every plan records the sales and shows the total; the breakdown by source and campaign is Pro.

Key metrics

Revenue per visit
A row’s revenue divided by the visits it brought. It puts a big source and a small one on the same scale.
Conversion
A row’s sales divided by its visits.
Time to pay
The median time from the first page of the paying visit to the sale. It is counted within the visit: with no cookies, someone who comes back another day starts from zero.

Sessions

Total sessions
16,491
Avg duration
3m 18s
Pages per session
2.1
Sessions with revenue
1.1%
187

One session

news.ycombinator.com, United States, Desktop, 5m 12s, €99
+0s
Pageviewscrolled 78%
/
+40s
Pageviewscrolled 100%
/pricing
+75s
Event
upgrade_click
+110s
Pageviewscrolled 55%
/docs
+180s
Outbound link
https://github.com/vero
+265s
Pageviewscrolled 100%
/pricing
+312s
Event
purchase
Figures from the Vero demo, a fictional SaaS on myapp.com.

What it is

Individual visits reconstructed as a timeline of pages and events, without a cookie or a stored identifier. See the journey that led to a signup or a purchase. Above the list, the shape of your visits: how many saw one page, two, or more, and how long they stayed.

What it is for

Aggregates hide the story; a session shows it. An average visit length hides the visits that saw one page and left; the shape shows them. A session is the fastest way to understand why a funnel step leaks.

Web Vitals

LCP (Largest Contentful Paint)Good
0.8s
How long the main content takes to appear.p75, target < 2.5s
INP (Interaction to Next Paint)Good
94ms
How fast the page answers a click or a tap.p75, target < 200ms
CLS (Cumulative Layout Shift)Good
0.02
How much the layout jumps while loading.p75, target < 0.10

LCP by page

p75
/blog/cookie-free-analytics-2026Needs improvement3.4s
/pricingGood2.0s
/docsGood1.1s
/Good0.8s
Figures from the Vero demo, a fictional SaaS on myapp.com.

What it is

Real-user performance: Core Web Vitals (LCP, INP, CLS) measured from actual visitors, not a lab test, and broken down by page and device. A verdict line says whether you pass and, if not, which metric fails and on which page. Each metric’s 75th percentile is drawn day by day against the limit for good, with your deploys marked.

What it is for

Slow pages lose money and rankings. This ties performance regressions to the exact pages and devices where they hurt, and to the deploy that caused them.

How to configure

Enable the vitals module in Settings, Install tab, where you build your tracker. It adds a few hundred bytes and reports automatically.

Key metrics

LCP
Largest Contentful Paint: how long until the main content appears. Good is under 2.5s.
INP
Interaction to Next Paint: how responsive the page feels to clicks. Good is under 200ms.
CLS
Cumulative Layout Shift: how much the page jumps while loading. Good is under 0.1.

Insights & optimization

AI insights

Summary

Executive summary

This week's revenue is up 34% on the week before, driven by the Hacker News front page: €7,124 from 3,420 visitors.
Driver

Revenue driver 1

news.ycombinator.com (referrer): €7,124 revenue from 3,420 visitors
Driver

Revenue driver 2

twitter (utm_source): €4,821 revenue
Figures from the Vero demo, a fictional SaaS on myapp.com.

What it is

Two layers. The statistics run today with no model involved: anomaly detection on traffic and revenue. On Pro, the AI writes the daily briefing on top of it, in plain language, and Ask Vero answers questions about your site.

What it is for

An anomaly tells you a number left its baseline, without you watching the dashboard all week. The briefing reads the dashboard for you and Ask Vero answers questions like "which source grew this week" in one sentence, grounded only in your site data.

How to configure

Anomaly detection needs no setup and no key: it reads the data you already send. The AI layer is on Pro and in the beta, with a per-organization monthly budget cap so cost is always bounded, and it declines off-topic questions. Owners and admins can turn all AI off on the Team page; then no model is called.

Goals

Conversion goals

Trial startedtrial_started
conversions412
rate2.5%
Purchasepurchase
conversions187
rate1.1%
Newsletter signupnewsletter
conversions934
rate5.7%
Demo bookeddemo_booked
conversions76
rate0.5%
GoalConversionsRate
Trial startedtrial_started
412
2.5%
Purchasepurchase
187
1.1%
Newsletter signupnewsletter
934
5.7%
Demo bookeddemo_booked
76
0.5%
Figures from the Vero demo, a fictional SaaS on myapp.com.

What it is

Turn any custom event into a tracked conversion goal and watch its rate over time. Signups, trials, purchases: whatever maps to progress. For your primary goal, Vero shows where it converts best: its rate by source and by entry page, each against your site’s own rate.

What it is for

A goal turns a raw event count into a rate you can improve. It is the unit optimization work is measured in.

How to configure

In the Goals view, name a goal and point it at an event name you already send with window.vero.track. It starts counting immediately.

Funnels

Entered
3,659
Converted
412
Overall conversion
11.3%

Funnels

sessions
Step 1/100.0%3,659
Step 2/pricing38.8%1,420
Step 3signup14.2%520
Step 4trial_started11.3%412
Figures from the Vero demo, a fictional SaaS on myapp.com.

What it is

Chain pageviews and events into an ordered path and see exactly where people drop off, step by step, with the conversion rate at each stage. The biggest leak is named in one sentence: between which two steps, and how many visits leave there.

What it is for

The biggest drop-off is usually the cheapest thing to fix. A funnel points straight at it.

How to configure

Build a funnel by adding steps in order: each step is a path or an event name. Reorder or remove steps any time. Funnels are on Pro.

Alerts

Recent (last 30 days)

3
Info
Revenue -24.6% worse €3,500 → €2,640
Spike
Visitors +212.4% better 475 → 1,484
Spike
Pageviews +206.4% better 1,115 → 3,416
Figures from the Vero demo, a fictional SaaS on myapp.com.

What it is

The anomalies Vero found in your traffic and revenue, each with the baseline it broke and how far it moved. Detection runs on a schedule, with no model involved. On Pro, standing watches you describe in plain language, each showing when it last fired.

What it is for

You cannot watch the dashboard all day. Alerts turn it into something that watches itself and taps you on the shoulder.

How to configure

Anomalies need no configuration: every site with recent traffic is checked, and alerts go to the channels you enabled, email or webhook. On Pro, describe what to watch (for example "tell me if revenue drops 20%") and the AI turns it into a standing rule.

AB Designer

Experiments

CTA button copyActive
/, 50% to variant B, .hero-cta, trial_started
Control
Exposures1,830
Conversions53
Rate2.9%
Bp < 0.05
Exposures1,831
Conversions76
Rate4.2%
Lift+43%
VariantExposuresConversionsRateLift
Control
1,830
53
2.9%
Bp < 0.05
1,831
76
4.2%
+43%
Figures from the Vero demo, a fictional SaaS on myapp.com.

What it is

Run cookieless split tests at the edge: define variants of a page, split traffic, and measure uplift on real conversions, with a sticky bucket per visitor and no client flicker. Each variant reports exposures, conversions, conversion rate, lift over control, and how sure the test is that the leader wins.

What it is for

Opinions are cheap; a measured uplift is not. This is how you turn "I think" into "we know".

How to configure

Create an experiment, add variants with weights and HTML changes, then deploy the edge snippet Vero writes for Cloudflare Workers, Cloudflare Pages Functions or Netlify Edge Functions. Vero serves the config; the edge applies it. The AB Designer is on Pro and is labelled Beta in the dashboard.

Configure

Tracker builder

SPA Navigation+222 B
History API: pushState, replaceState, popstate. For Next, React Router, Vue Router, Nuxt.
Low~0.5/sessionpageview on route change
Web Vitals+587 B
LCP, INP, CLS, FCP and TTFB. One final value per pageview, no sampling.
Low~5/sessionvital: lcp, inp, cls, fcp, ttfb
AB Experiments+248 B
Records A/B exposures from edge-applied variants. Pairs with the /ab designer.
Low~1/sessionexp
Checkout Links+319 B
Adds the visit to Stripe Payment Links and Lemon Squeezy checkout links, so each sale arrives with its source.
Lowno event, tags the link

What it is

A visual builder for your tracking script, in the Install tab of Settings. Toggle optional modules (SPA, scroll, engagement, outbound, downloads, leave, vitals, experiments, checkout) and see the exact gzipped size update live before you copy the snippet.

What it is for

You ship only what you use. Core is 1.2 KB; each module is a few hundred bytes, so the payload stays honest.

How to configure

The edge serves only the modules you selected, keyed to your site token, and caches the result. Change modules any time and re-copy. The URL stays the same.

UTM builder

Your tracked URL

https://myapp.com/pricing?utm_source=newsletter&utm_medium=email&utm_campaign=spring_launch&utm_content=header_cta

What it is

A small tool to build correctly-tagged campaign links. Fill in source, medium, and campaign and it produces a clean, copy-ready URL.

What it is for

Attribution is only as good as your tagging. Consistent UTMs are what make the Sources view trustworthy.

Connect your sales

Payment providers

StripeConfigured
Lemon SqueezyNot configured
PaddleNot configured

What it is

Pick where you take payments: Stripe, Lemon Squeezy or Paddle. Each provider shows whether it is configured and when its last sale arrived.

What it is for

Until a provider is connected, Vero counts visits but not the money they bring.

Settings

General

Install snippet

<script defer src="https://[your-vero-host]/t.js?s=vr_demo_a1b2c3d4e5f6"></script>

What it is

Per-site configuration: three tabs: Install (the tracker builder and your site token, which you can rotate), Sales (the revenue webhooks, with a link to Connect your sales) and Sharing (your public profile and badge), plus site deletion. Account-level settings (API keys, billing, notifications) live on the Account page, in the menu under your name at the bottom of the sidebar. Data retention is set by your plan.

What it is for

This is where security and billing live. Rotating a leaked token or tightening allowed origins takes seconds here.

How to configure

Allowed origins is an allowlist: the API rejects events from any domain not on it, which is why new domains must be added before data flows.

Workspace

Team

What it is

Invite teammates to your organization and manage their roles. Everyone works under one billing account, and each member sees all sites or only the ones you pick for them. Open it from the menu under your name at the bottom of the sidebar.

What it is for

Analytics is a team sport. Shared access means marketing, product, and finance argue from the same numbers.

Hand-picked beta, waitlist open

Ask for a place in the beta.

Anyone can join the list. The accounts we pick get Pro free for the whole beta.

By joining you agree to receive launch updates and accept our Privacy Policy.

See the demo