Skip to main content
Everything Vero does

From the first click to the sale.

Follow one visit from the link that brought it to the sale it paid for. Every step below is a screen of the demo, with simulated data.

One visit, eight screens, one sale

The path Vero records for every visit.

In the order it happens.

  1. 1Sources

    It arrives from somewhere, and Vero names it.

    Referrer, channel and UTM campaign are recorded on the first pageview. Visits from ChatGPT, Perplexity, Claude, Gemini and Copilot count as their own AI channel.

    See sources in the demo →
    Referrersvisits
    news.ycombinator.com3,420
    google.com2,876
    twitter.com1,245
    producthunt.com987
    github.com612
    reddit.com/r/SaaS421
    chatgpt.com240
  2. 2No cookies

    It is counted without a cookie.

    A 1.2 KB core tracker writes nothing to the device. The IP is used in memory for a hash with a daily salt and never stored.

    See the overview in the demo →
    Visitors14,724 over the period, peak 3,420
    MonTueWedThuFriSatSun
  3. 3Modules

    It reads, scrolls and clicks.

    Optional modules record scroll depth, active time, outbound clicks, downloads and Web Vitals. You load only the ones you read.

    See pages in the demo →
    Outbound linksclicks
    github.com/vero/tracker421
    twitter.com/getvero312
    stripe.com187
    Downloadsdownloads
    integration-guide.pdf142
    press-kit.zip87
    whitepaper-2026.pdf53
  4. 4Edge A/B

    It sees a variant.

    AB Designer rewrites the HTML at the edge, before the page reaches the browser. No script swaps the variant, so nothing flickers. It is in beta.

    See an A/B test in the demo →
    CTA button copyActive
    /, 50% to variant B, .hero-cta, trial_started
    VariantExposuresConversionsRateLiftControl1,830532.9%Bp < 0.051,831764.2%+43%
  5. 5Checkout

    It clicks pay.

    The checkout module adds the visit to your Stripe Payment Links and Lemon Squeezy checkout links. The sale carries it back.

    See the tracker builder in the demo →
    Checkout Links+319 BAdds the visit to Stripe Payment Links and Lemon Squeezy checkout links, so each sale arrives with its source.no event, tags the link
    AB Experiments+248 BRecords A/B exposures from edge-applied variants. Pairs with the /ab designer.exp
  6. 6Revenue

    The sale comes back with its source.

    A Stripe, Lemon Squeezy or Paddle webhook records the sale against the visit. On Pro you read revenue by source, campaign, referrer, channel and entry page, and the profit each source leaves after its spend.

    See revenue in the demo →
    Profit by sourcePro
    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
  7. 7Alerts

    Something changes, and you hear first.

    Every day Vero compares visitors, pageviews and revenue with a typical day. A drop goes to email, Slack, Discord or a webhook; on Pro, watches catch the thresholds you set.

    See alerts in the demo →
    Recent (last 30 days)3
    InfoRevenue ↓ 24.6%€3,500 → €2,640
    SpikeVisitors ↑ 212.4%475 → 1,484
    SpikePageviews ↑ 206.4%1,115 → 3,416
  8. 8Weekly digest

    On Monday, the week in your inbox.

    One email per site, in your language: revenue without tax against the previous 7 days, your top revenue source, the one that lost the most, visitors, top page and top referrer. On Pro, AI insights add what moved revenue and what to try next.

    See AI insights in the demo →
    AI insights, Monday emailPro
    Executive summaryThis week's revenue is up 34% on the week before, driven by the Hacker News front page: €7,124 from 3,420 visitors.
    Revenue driver 1news.ycombinator.com (referrer): €7,124 revenue from 3,420 visitors
    Revenue driver 2twitter (utm_source): €4,821 revenue
Tracker builder

Pick the modules. See the bytes.

The core is 1.2 KB gzipped and all 9 modules together are 2.7 KB. Each of the 320 combinations is measured, not estimated, so the size you see is the size your visitors download.

1.4 KB1,398 B gzipped
Core1,232 B
Everything Vero does today

Every feature, by the question it answers.

Everything below is on Hobby and Pro unless it is marked Pro.

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.
  • Entry and exit pages
    Entries and exit rate are columns of the Pages table: sort by them, or by pageviews, time on page and scroll depth, to see where visits start and where they leave.

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.
  • Saved segments
    Saves a set of filters so you can open it again in one click.
  • Date ranges and share link
    Switch between 24H, 7, 30 or 90 days or a custom range, and copy the view you are on as a link.
  • Goals
    Turns a custom event or a page reached into a goal, created from the Goals screen with no code, with conversions, rate and where each goal converts best by source and entry page, plus an explorer for event properties. Mark one goal as primary and its conversion shows on the Overview.
  • Custom events
    Send any action with vero.track() and the properties you need.
  • FunnelsPro
    Builds multi-step funnels from pages or events, names the step that loses the most people and shows the typical wait between steps.
  • Core Web Vitals
    LCP, INP, CLS, FCP and TTFB by page and device, measured on your real visitors, with a sentence that says whether you pass and each core metric charted day by day against its good line.
  • Scroll, active time, outbound clicks, downloads and leave
    Optional tracker modules: switch on the ones you will read and your visitors download only their bytes.
  • SPA tracking
    Counts navigations in single-page apps as pageviews, from the history API.
  • Achievements
    Marks lifetime milestones and gives you a banner to share each one.

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.
  • Who found the customer and who closed the salePro
    Puts the source that found each customer beside the one that closed the sale, once the period has 5 sales with a visit on record, with the average visits and pages on the day of the first payment and the share paid on that day’s first visit. No cookies, so it links the visits of one day and repeat purchases by the same customer id, never the full journey.
  • Profit by sourcePro
    Enter what you spend each month per source, in its own currency, and read its profit, margin and revenue per visit.
  • Vanity trafficPro
    Lists the sources that bring visits and no revenue.
  • Revenue cohorts
    Groups paying customers into weekly cohorts by the date of their first payment, or monthly ones on ranges over 120 days, with refunds subtracted.
  • Sessions with revenuePro
    Shows how many visits ended in a sale, next to total sessions, average duration and pages per session.

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.
  • Ask VeroProAI
    Ask a question about your data in plain language and get the answer from your own figures.
  • Plain-language watchesProAI
    Write the watch as a question and Vero turns it into a threshold.
  • Anomaly cause and digest commentaryProAI
    Adds a likely cause to anomaly emails and a short commentary to the weekly digest.
  • AI off switchProAI
    Owners and admins turn AI off for the workspace, and no model is called for any of its sites.

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.
  • Edge and server tracking
    Track with no client script, from middleware for Vercel and Next, Cloudflare, Netlify, or Node, Bun and Deno.
  • Install diagnostics
    Checks whether your tracker is reporting and walks you through the setup when it is not.
  • Install prompt for AI editors
    Copy a ready prompt from a framework guide into Cursor, Claude Code or another AI editor. It adds the script and passes the visit id to your checkout; you connect the webhook yourself.
  • Public profile and badge
    Opt in to a public stats page and an SVG badge you can embed anywhere.

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.
  • Teams and roles
    Owner, admin and member roles, invitations and site access per member; only managers change settings.
  • Staff access rules
    Support access is read-only, expires 30 minutes after it starts and is written to an audit log.
  • Sites
    1 site on Hobby and unlimited sites on Pro.
  • Past the monthly capPro
    Pro keeps recording past its monthly cap of pageviews and custom events, up to 5×, and never charges for what goes over. Hobby stops at the cap.
Alerts

You hear from Vero when it matters.

A digest on Monday, an alert when a number moves, and each sale sent on to your own systems. The rest of the week, nothing.

  • Mail, monday

    Your week on myapp.com

    Revenue, visitors, top revenue source and top referrer, in your language.

  • Slack, tuesday

    Spike: visitors above a typical day

    myapp.com is getting more visitors than on a typical day. Open the overview to see where they come from.

  • Mail, thursday

    Revenue below a typical day

    Revenue on myapp.com fell against the same hours of a typical day.

  • Webhook, friday

    revenue.recorded

    A Stripe sale with the visit that brought it, signed and sent to your endpoint.

Check it on our own site

We measure getvero.dev with Vero.

FAQ

What people ask before they switch.

Will the tracker slow my site down?

The core is 1.2 KB gzipped and all 9 modules together are 2.7 KB. You load only the modules you pick, and each of the 320 combinations is measured, so the builder shows the exact bytes.

Do I still need a cookie banner?

Vero sets no cookies, writes nothing to the visitor’s device and never stores the IP. Whether your site needs a banner depends on everything else it loads, so that is for your legal team to decide.

Which sales does Vero see on the free plan?

Every one. Hobby stores each sale and shows the total and the number of sales. Which source, campaign, referrer, channel or entry page brought each one is Pro.

Does the AI work today?

Yes, on Pro and in the beta: AI insights, Ask Vero, plain-language watches and the digest commentary. Owners and admins can turn all AI off on the Team page. Anomaly alerts do not depend on it: they are statistics, not a model.

Where is my data stored?

In Ireland, in a single database with no replicas. The API and the tracker run at the edge closest to each visitor, so compute and cache are global.

Can I take my data with me?

Yes, on every plan. Export events and revenue as CSV, up to 50,000 rows per export, or the whole account as JSON, then delete it.

Hand-picked beta, waitlist open

Find out which source pays your bills.

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

See the demo