Developer tools
Count the developers who block scripts, and see who pays.
Part of your audience runs an ad blocker, reads the docs for weeks and finds you through GitHub and AI assistants. Vero can measure from the edge instead of the browser and ties each sale to its source.
The problem
- Every visitor whose blocker stops the script is missing from browser-only numbers, and so is the channel that sent them.
- The docs get most of the traffic, and you cannot tell which page leads to a paid plan.
- GitHub, Hacker News and AI assistants send visitors that disappear into a generic Referral row.
How Vero helps
Pageviews no blocker can stop
Send pageviews from edge middleware on Vercel and Next, Cloudflare or Netlify, or from your server on Node, Bun or Deno. Nothing runs in the browser, so nothing can be blocked. The script sends a pageview of its own, so pick one per site: the edge where blocked visits matter, the script where you want scroll, engagement and Web Vitals.
Every referrer by name
Visits from chatgpt.com, perplexity.ai, claude.ai, gemini.google.com and copilot.microsoft.com form their own AI channel; GitHub and Hacker News keep their own referrer rows. On Pro each one shows the revenue it brought.
Analytics in your workflow
On Pro, the MCP server lets Claude or Cursor query your stats and revenue from the editor, the read API feeds your own dashboards, and deploy annotations from CI mark each release on the chart.
What you use
- Edge and server tracking with no client script
- AI assistants as their own channel
- MCP server and read API on Pro
- Deploy annotations from CI on Pro
- Revenue by referrer, source and UTM on Pro
- 1.2 KB core script for the browser signals
Worked example from the public demo
Which developer channel pays
The public demo’s sources belong to a fictional SaaS in its launch week. Its developer traffic is the kind that never shows up as a campaign: GitHub, docs readers and an AI assistant.
GitHub, by name
github.com sent 612 visitors and €968, €1.58 per visitor, above the site’s €1.25. No tag needed: the referrer row alone shows that people who arrive from GitHub leave more per visit than the average visitor.
The docs, and what leaves them
/docs had 3,527 pageviews. The outbound module counted 421 clicks to github.com/vero/tracker, and the downloads module 142 downloads of integration-guide.pdf. Neither is a sale, but both point at the readers who are evaluating the product, not just passing through.
ChatGPT as a channel
Visits from chatgpt.com form their own AI channel: 240 visitors and €400 in the week. Small next to Hacker News, but it is a row of its own, so you can watch it grow instead of losing it inside Referral.
The decision: put effort into GitHub and the docs, which bring buyers with no ad spend, and follow the AI row as a channel of its own before spending anything on it.
Figures from the public demo: launch week for a fictional SaaS, not Vero’s data or a customer’s. Open this screen in the demo
Frequently asked
Can Vero’s script be blocked?
Yes, like any browser script. Edge and server tracking cannot, because nothing runs in the browser. Pick one of the two per site: running both counts each page load twice, because the script sends its own pageview.
Which docs pages lead to revenue?
Open a page in Pages: on Pro, its detail shows the revenue from visits that saw it. The same detail shows how many visits started and how many ended on that page.
Do server-side pageviews still count unique visitors?
Yes. The middleware forwards the visitor’s IP, user agent and country with your ingest secret, so the daily visitor hash is computed from the visitor, and then the IP is discarded.
Keep reading
- For developersAn API, an MCP server, A/B tests at the edge and a tracker you assemble yourself.
- See which channel drives Paddle revenue.Paddle revenue attribution: signature-verified transaction and refund webhooks record revenue, attributed by source when the checkout carries the visit.
- Ad blockers skip your analytics. Measure from the server tooA blocked script means a visitor who never existed for you. What ad blockers actually stop, which visitors you lose, and how edge and server-side tracking count them anyway.
- PricingPay for pageviews and custom events. Every Pro tier has every feature.
More use cases
- SaaS
Know which channel brings the paying customers.
Cookie-based analytics loses the visitors who reject the banner and stops at the click. Vero links every trial, activation and paid conversion back to the source that earned it, without cookies.
See the use case - Marketing teams
Put budget on the campaigns that bring revenue.
Stop optimizing to last-click sessions. Vero ranks your UTM campaigns by the revenue they brought, next to each source, referrer, channel and entry page, and flags the day your traffic or revenue leaves its own baseline.
See the use case - Indie hackers
Ship one script. See what makes money.
You do not have time for a tag manager and a consent stack. Vero is one tiny script that ties traffic to revenue and answers questions from your editor.
See the use case - Agencies
Show every client the revenue your work brought.
Clients pay for results in money, not sessions. Vero keeps every client site in one account, ties each sale to the source behind it, and writes nothing to their visitors’ devices.
See the use case - Creators and newsletters
Know whether the newsletter, YouTube or your blog sold the course.
You sell a course, an ebook or templates through Stripe, Lemon Squeezy or Paddle. Vero ties each sale to the source that brought the buyer, without cookies.
See the use case