Skip to main content
Hand-picked beta, waitlist openHow the beta works

The truth aboutyour revenue.

Analytics that talk about money. Vero is cookie-free web analytics with revenue attribution: it ties each sale to the visit that brought it and ranks every source and campaign by the money it brings. The AI tells you what moved your revenue.

Hand-picked accounts get Pro free during the betaSee the demo

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

Check it on our own site

We measure getvero.dev with Vero.

  • 1.2 KB

    Tracker getvero.dev downloads, gzipped

  • 100

    Mobile PageSpeed performance, home page

  • /live

    Our own traffic, measured by Vero, open to anyone.

    See getvero.dev/live →
Free site teardown

Weigh the tracking code your homepage ships.

Enter your domain: no signup, and the answer takes seconds. You get its stack, its indexed pages, an estimated traffic range and the gzipped weight of every tracker it loads, cookie banner included, next to Vero's.

How we measure it →
Try with your siteDrop your domain and in seconds we'll size your usage and weigh the trackers your homepage loads. No install.
  • Detect your stack + site type
  • Count indexed pages from your sitemap
  • Estimate your monthly sessions
One visit, start to finish

From click to cash, without losing the thread.

This is the path Vero records for every visit, in the order it happens.

Setting it up takes two steps

  1. 1

    Paste one script tag

    A script from 1.2 KB, with no cookies. Traffic, sources and campaigns count from the first pageview.

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

    Connect your sales

    Paste Vero’s webhook URL into Stripe, Lemon Squeezy or Paddle. The checkout module tags Stripe and Lemon Squeezy payment links with the visit.

    Stripe● Connected
    Lemon SqueezyPaste the URL
    PaddlePaste the URL

    With Paddle or your own checkout, you pass the visit id yourself. See how →

Revenue and profit

See which source pays for itself.

Each sale stays tied to the visit that brought it, so you read revenue by source, campaign, referrer, channel and entry page. Enter what each source costs and the same table ranks them by profit.

How revenue by source works →

Profit by source

Pro
Last 7 days
Profit by source, Last 7 days
SourceVisitsRevenueCostRevenue / visitProfit
news.ycombinator.com3,420€7,124No cost€2.08€7,124
twitter1,245€4,821€1,200€3.87€3,621
producthunt1,632€1,845No cost€1.13€1,845
google612€1,783€1,400€2.91€383
github.com612€968No cost€1.58€968
newsletter743€482€900€0.65-€418 (Lost money)
chatgpt240€400No cost€1.67€400
reddit421€0€1,150€0-€1,150 (Lost money)

Demo week of a fictional SaaS. Cost is what each paid source spent; profit is revenue less cost.

Ask Vero Pro

Ask why revenue moved, in Vero or from your agent.

The AI reads the same figures as your dashboard and answers in plain language, with the numbers behind each answer.

It runs on Google’s Gemini API, which receives aggregated figures, never individual visits. An owner or admin can turn it off for the whole workspace.

Ask Vero, with demo data
Vero
Revenue is €18,423 this week, up 34% on the week before. The Hacker News front page on Tuesday drove it: 3,420 visitors and €7,124, the top referrer by revenue.

The AI also

  • AI insights

    A daily read of your week: which sources drive revenue and what changed.

  • Watches in your words

    Describe what to keep an eye on in a sentence and Vero turns it into a watch.

  • Likely cause of a drop

    When revenue falls, the alert names the likely cause.

  • Weekly email commentary

    The weekly email adds a short read of what happened and why.

Or ask from your own agent

Connect Claude, Cursor or any MCP client and ask about your revenue while you work. Vero hosts the server, so you run none. It is part of Pro.

Set up MCP →
Pricing

Free during the beta. Plain prices after.

Prices in EUR, VAT not included. 20% off when you pay yearly.

BetaNow, picked by hand
€0 for the whole beta

Everything in Pro, AI included. When it ends, 40% off for life on whichever paid plan you choose.

  • 250,000 pageviews and custom events a month
  • Unlimited sites and 2 years of data
  • At least 30 days of notice before it ends
  • Nothing is charged unless you choose a plan
Join the waitlist
ProWhen Vero opens to everyone
€19 + VAT / mo
Pageviews and custom events a month250,000
Billed monthly
  • Which source brought each sale
  • AI, Ask Vero and watches
  • Funnels, A/B tests and the API
  • 2 years of data
  • 14-day free trial, no card, counted from the first event your site records
See full pricing
HobbyWhen Vero opens to everyone
€0 / mo, no card

To start measuring, with your data always yours to take.

  • 10,000 pageviews and custom events a month
  • 1 site and 30 days of data
  • Anomaly alerts
  • CSV export and a record of every sale
Tell me when it opens

How the beta works

Anyone can join the waitlist. I pick accounts by hand, in small batches: signup order buys nothing, and joining does not guarantee a place.

  1. 1You join the waitlistWith your email. I read every entry.
  2. 2I pick your accountIf I pick you, the invite arrives by email.
  3. 3Pro free for the whole betaAI included, 250,000 events a month and unlimited sites.
  4. 430 days of noticeI tell you at least 30 days before the beta ends. From that notice you can choose a plan with 40% off for life.
  5. 5First charge on the last dayChoose a plan and it is charged the day the beta ends. Choose nothing and you move to Hobby, free, with nothing charged.
What about the 14-day trial? It is for new accounts once Vero opens to everyone: 14 days of Pro free, no card, counted from the first event your site records. Beta accounts do not need it: they already use Pro free until the last day of the beta.
FAQ

Before you ask.

Still unsure? Read the guides or write to hello@getvero.dev.

Read all guides →
Do I need a cookie banner, and what does Vero collect?

Vero sets no cookies and writes nothing to the visitor’s device. It records the page, the referrer, campaign tags, the country, screen width, browser language and time zone, and the browser and OS names, and the app when the page opens inside one, plus the events of the modules you turn on and of your own vero.track() calls. What that means for your site is your legal team’s call, and the transparency page lists every field.

See every field →

Can I run it alongside Google Analytics?

Yes. The two scripts do not touch each other, so you can compare them for as long as you like. Your GA history is not imported: Vero counts from the day you add it.

Is it more accurate than Google Analytics?

You will usually see more of your traffic: neither a rejected banner nor Safari’s limits take anything from Vero, because it sets no cookies. Cookie-based tools lose the visitors who reject the banner or run an ad blocker, and Safari ITP shortens their cookies, so returning visitors count as new. An ad blocker can still stop Vero’s script; measure from the edge or your server and there is nothing left in the browser to block. The script leaves out, on purpose, browsers that send Do Not Track or GPC; measured from the edge or your server, they are counted unless your code checks for the two signals.

Can I attribute revenue to sources?

Yes, on Pro. Paste one webhook URL into Stripe, Lemon Squeezy or Paddle and turn on the tracker’s checkout module: each sale arrives with the visit that brought it, and Vero ties it to that visit’s source, campaign, referrer, channel and entry page. On Paddle, pass the visit id as customData.vero in your checkout. On Hobby the sale is stored all the same and adds to your total. If you build your own checkout, send each sale to the ingest endpoint with vero.session().

Revenue docs →

Does the AI work during the beta?

Yes. AI insights, Ask Vero, plain-language watches and the commentary in the weekly email are on, on Pro and in the beta; Hobby has no AI. They run on Google’s Gemini API, which receives aggregated figures, never a single visit or an IP. An owner or admin can turn all AI off on the Team page, and then no model is called. Anomaly alerts do not depend on it: they are statistics on your own data.

Can I take my data with me?

Yes. CSV export of events and revenue is on every plan, Hobby included, up to 50,000 rows per export. A longer period is cut at that cap, so export it in slices.

Will there be a free plan?

Yes: Hobby, free and with no card, once Vero opens to everyone. The pricing page lists what it includes and what Pro adds.

See the plans →

What does a picked account get?

Pro, the AI included, free for the whole beta. The beta card above has the terms, and there is no opening date yet; the beta page says how we pick.

How we pick →

Privacy

Privacy you can check.

Three claims, and how to check each one yourself.

  • Nothing on the visitor’s device

    No cookies and no localStorage. The session id lives in memory, never on disk.

    How to check. Open DevTools, Application tab: Vero writes nothing there.
  • The IP is never stored

    Visitors are counted with a salted SHA-256 hash of the IP, user agent, date and site. The date changes it every day, and the site makes it different on every Vero site.

    How to check. Read the transparency page: it names what goes into the hash (the IP, the user agent, the date and the site) and lists every field the tracker sends. The IP is not among those fields.
  • The script honors Do Not Track and GPC

    A browser that sends either signal is not counted: the script stops before it sends anything.

    How to check. Turn on GPC and watch the Network tab: no event is sent.
Tracker builder

Build your tracker. Load only what you use.

Vero starts from a 1.2 KB core that ties each sale to its source. Add only the modules you need and read the exact gzipped size as you go. The dashboard has the same builder.

1.2KBThe gzipped core every page loads, before you add a single module.

Toggle modules to see the size and the events live. What a module sends never counts toward your plan.

CorePageviews, sessions, referrer and UTM.~1/session: pageview1,232 BRequired
Core and 1 modulecookie-free, IP never stored
1.4 KB1,398 B gzipped
Core 1.2 KBAll 9 modules 2.7 KB
Install
<head>
  <script defer src="https://[your-vero-host]/t.js?s=YOUR_TOKEN"></script>
</head>
Accounts in the hand-picked beta run this exact tracker before launch.Join the waitlist
Script weight and revenue by source, by category, measured on
AnalyticsScript, gzippedRevenue by source
Vero1.2 KB core2.7 KB with all 9 modulesYes, on the Pro planStripe, Lemon Squeezy or Paddle by webhook
Privacy-first analytics1.3–3.8 KBPartial on most
Revenue-first trackers4.0–16.4 KBYes
Traditional web analytics172.7–175.1 KBPartial

Script weight and revenue by source, by category, measured on . Sizes: Vero's come from our build manifest; the rest are the gzipped scripts each product served on that date, lightest to heaviest in each row. Yes: each payment is matched to the visit that brought it. Vero and the revenue trackers connect to the payment provider by webhook. Partial: your site sends a value with an event, and the dashboard splits it by source.

More on the lightweight tracker →
API and MCP

For developers.

Measure from the browser, the edge or your server. Then take your numbers out of the dashboard with an API key, or into Claude and Cursor over MCP.

Read API

GET /api/v1/*Pro

Pull stats, revenue and attribution into your own dashboards and reports.

# bash
curl https://[your-vero-host]/api/v1/stats?period=7d \
  -H 'Authorization: Bearer vk_...'

Ingest API

POST /api/eventsPro

Send events from your backend, cron jobs or workers with a key that can write.

# bash
curl -X POST https://[your-vero-host]/api/events \
  -H 'Authorization: Bearer vk_...' \
  -H 'Content-Type: application/json' \
  -d '{ "type": "custom", "path": "/checkout/complete", "event_name": "purchase_completed" }'

Custom events

vero.track()

Modules cover the common signals. For anything else, call vero.track() with a name and optional properties: a signup, a plan pick, a video play. Vero drops any property value that contains an email address.

On Pro, your backend can send events too, with a write API key. Those events carry no traffic source.

// JavaScript
window.vero.track('signup', { plan: 'pro' })
Custom events in the docs →
  • 1,232 B in the browser

    Browser script

    Pageviews, plus only the modules you switch on: scroll, engagement, Web Vitals, SPA navigation.

    Best for attribution: only its session ties a sale to the visit that brought it.

    Install the script →
  • 0 B in the browser

    Edge middleware

    Your Vercel/Next, Cloudflare or Netlify middleware, or your server, sends each pageview. Ad blockers cannot stop it and it works with JavaScript off.

    Best for complete pageview counts. It sees no scroll, engagement, Web Vitals or SPA route changes, and a sale needs the script to find its source.

    Edge setup →
  • 0 B in the browser

    Server API

    Send sales and refunds from any backend with your ingest secret, on every plan.

    Best for revenue: nothing in the browser can block it. Custom events from here need Pro.

    Server API docs →
Everything Vero does today

Every feature, by the question it answers.

Everything is in Hobby and Pro, except what is marked Pro.

See all features →

In depth

Where each visit comes from

Every source, channel and campaign, and on Pro the revenue each one brought.
  • Sources
    Ranks the sites that send you visits next to the sales they brought. On Pro, Who pays? places each source by its visits and revenue per visit, and each source opens in a sheet of its own.
  • Channels
    Reads each visit's UTM tags first and its referrer after, then groups it into Referral, Search, Social, Direct or AI, plus Email, Paid search, Display and Affiliates once a tagged visit lands there. You see which kind of traffic pays.
  • What direct traffic is made of
    Splits the visits with no referrer and no tag. Those opened inside an app such as Instagram or TikTok carry its name, and that part is certain. The rest is a reading of the entry page: the home page is likely typed or bookmarked, an inner page a direct link, a thank-you page a return from checkout. On every plan.
  • AI assistants as a channel
    Visits from chatgpt.com, perplexity.ai, claude.ai, gemini.google.com and copilot.microsoft.com count as AI instead of hiding in Referral.
  • UTM sources, mediums and campaigns
    Breaks traffic down by the utm tags on your links, down to each campaign, with the revenue each campaign brought on Pro.
  • UTM link builder
    Builds tagged links from where you will share them and says which channel their visits count as. Tags are saved in lowercase, so one source never splits in two. It warns when a link leads to another site or uses a name Vero keeps for its own rows, and Your campaigns lists what each link brought.
  • Countries
    Shows visitors by country; click one and the whole dashboard filters to it.
  • Devices, browsers and OS
    Splits visits by device type, browser and operating system.
  • Languages
    Shows the browser language of your visitors, so you know which translation is worth paying for.

What they do once they are in

Pages, sessions, goals and speed, read against the period before and a typical day.
  • Overview KPIs
    Visitors, revenue, revenue per visitor and bounce rate, plus conversion once you mark a primary goal, each with its sparkline, its change against the previous period and an info mark beside its name that says what it counts.
  • Today vs a typical day
    Reads the last 24 hours against the same hours averaged over the previous 1 to 4 weeks, with the day’s anomalies and deploys.
  • Chart with compare and zoom
    Overlays the previous period and a typical day, and switches to revenue; drag across the chart to zoom into a stretch.
  • Traffic heatmap
    Shows when your traffic arrives, by weekday and hour, names the busiest hour and can show revenue by hour instead. When the data supports it, it tells you which hour to publish just before and which part of your day most sales come in.
  • Realtime visitors and live feed
    Counts who is on the site now, lists their visits and events as they happen, and lists the sales of the last 24 hours.
  • Pages and page detail
    Puts your pages in one table you sort by any column and read as traffic, engagement or money, and opens each one: traffic against the previous period, scroll depth, trend lines, links to its sources, vitals and goals and, on Pro, the revenue of visits that saw it.
  • Page flow
    Shows where visitors were before a page and where they went after it.
  • Sessions with timeline
    Tells each visit step by step, from where it arrived, through its pages and events, to the sale it ended in, with no screen recording, and shows how visits spread by pages seen and time spent.
  • Filter chips
    Click any page, referrer, country, UTM source, UTM campaign or device and every figure on screen filters to it.

The sale, tied to the visit that brought it

Paste one webhook URL and every sale arrives with the source that earned it.
  • Sales recorded
    Stores every sale on every plan and shows the total and the number of sales.
  • Revenue attributionPro
    Ties each sale to the source, campaign, referrer, channel and entry page of the visit that brought it.
  • Stripe, Lemon Squeezy and Paddle webhooks
    Paste one URL into your provider: sales and renewals are recorded and refunds are subtracted.
  • Custom checkout API
    Send sales and refunds from your server; vero.session() gives you the visit id to attach to them.
  • Checkout module
    Adds the visit to your Stripe Payment Links and Lemon Squeezy checkout links, so the sale knows where it came from.
  • Webhook status
    Walks you through each provider in three steps and shows its URL, signing secret, last delivery and last sales, so you know sales are arriving.
  • Revenue over time
    Charts revenue or the number of sales across the period against the previous period, and notes the sales made in other currencies.
  • Revenue per visitor and refunds
    Shows revenue per visitor and the payment conversion: first payments from the period’s visits, divided by its visitors. Refunds are already subtracted, with the total before them beside it. Renewals are counted on their own.
  • Time to payPro
    Times each customer’s first sale from the first page of the visit that paid, for visits that started in the period, and gives the typical wait for each source once the period has 5 sales. Renewals are left out.

Told when a number moves

Vero checks every day, so you learn about a drop from an email, not from next month’s invoice.
  • Anomaly alerts
    Compares visitors, pageviews and revenue with a typical day, every day, and emails owners and admins when one falls.
  • Spike alerts
    Marks rises in green, and emails them only if you switch that on.
  • New-sale alerts
    If you switch it on, tells you by email or webhook when a new customer first pays: site and amount on every plan, source and campaign on Pro. Up to 10 emails per site a day, and no alert for refunds or for a customer id that already has a sale.
  • All your sites at a glance
    With more than one site, each card shows visitors and revenue for the period you choose, with their change, and marks a site with no events in 24 h or a drop today. Those come first, unless you sort by revenue, visitors or biggest change. The totals keep one figure per currency.
  • WatchesPro
    Set a fixed threshold on visitors, pageviews, revenue or bounce rate, for today or 7 days, hear when it is crossed and see when each one last fired.
  • Weekly digest
    A Monday email per site that leads with revenue without tax and the previous 7 days, then your top revenue source, the source that lost the most, a new referrer, visitors, pageviews, bounce rate, top page and top referrer, in the reader’s language.
  • Usage notices
    Emails when your workspace reaches 80% and 100% of its monthly pageviews and custom events.
  • Alert channels
    Sends alerts to email, Slack, Discord or a JSON webhook, with a test button and a choice per category.
  • AI insightsProAI
    A panel that opens with the period in four figures, then a summary, what drove revenue, the opportunities and the next actions, each linked to its screen.

For developers

An API, an MCP server, A/B tests at the edge and a tracker you assemble yourself.
  • Read API v1Pro
    Reads stats, revenue, attribution, goals, vanity traffic, cohorts, realtime and anomalies with an API key.
  • Server ingest APIPro
    POST events from your own server with a write key.
  • API keysPro
    Read-only or read and write keys, one set per site.
  • MCP serverPro
    Lets AI agents such as Claude or Cursor read your stats, revenue, attribution, goals, cohorts, realtime and anomalies.
  • Outbound revenue webhook
    Sends a signed POST to your endpoint on every revenue.recorded and revenue.refunded, with the visit id.
  • Deploy annotationsPro
    Marks deploys on the chart from Vercel, GitHub, Netlify, Cloudflare or by hand, so a drop lines up with the release that caused it.
  • AB DesignerPro
    Pick an element by CSS selector, write its variant in HTML, set traffic weights and a goal; results come with lift, significance and how many more days the test needs at your traffic. It is in beta.
  • Edge A/B snippetsPro
    Ready code for a Cloudflare Worker, Cloudflare Pages or Netlify that keeps each visitor in the same variant without a cookie.
  • Tracker builder
    Pick modules and read the measured gzip size of that exact combination, one of 320. The estimator sizes your plan from pageviews: modules never count toward it.

Your data, under your control

Nothing written to the visitor’s device, nothing kept that identifies anyone, and every row yours to take.
  • No cookies, nothing on the device
    The session id lives only in memory.
  • IP never stored
    Used in memory for the daily hash, then dropped.
  • Do Not Track and GPC honored
    With Do Not Track or Global Privacy Control on, the script sends nothing.
  • PII stripping and bot filtering
    Properties shaped like an email, mailto and tel links, and bots are all dropped before storage.
  • EU storage
    Data is stored in Ireland; compute and cache run at the edge, worldwide.
  • Privacy-policy snippet
    A ready paragraph that describes Vero for your privacy policy.
  • CSV export
    Export events and revenue, up to 50,000 rows per export, on every plan. Each sale carries its amount in whole units and the provider’s charge id.
  • Account export and deletion
    Export the account as JSON, or delete a site or the whole account with its data.
  • Retention by plan
    Data is kept 30 days on Hobby and 2 years on Pro, then deleted automatically.
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

Vicente Torres
Vero is built by one person in Spain. I read every waitlist entry and pick the beta accounts myself.
Vicente Torres, Founder of Vero LinkedIn