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.
The problem
- Attribution dies at signup: you see clicks, not which channel becomes paying revenue.
- Cookie banners tank conversion and still leave cookie-based analytics short of the visitors who reject them.
- Product and marketing data live in two tools that never agree.
How Vero helps
Revenue, not vanity
Paste one webhook URL into Stripe, Lemon Squeezy or Paddle and each payment reaches Vero with the session that started it, so revenue rolls up per source, campaign, referrer, channel and entry page instead of per visit.
Trial-to-paid by channel
Track custom events like trial_started and subscription_created, then read them by acquisition source to see where paid revenue really comes from. Anomaly detection flags the day traffic or revenue leaves its own baseline.
The whole funnel, counted
A hash that changes every day stands in for the cookie. Nothing is written to the device, so a rejected banner hides no visit from Vero: you measure the whole funnel.
What you use
- Revenue attribution by source, campaign, referrer, channel and entry page
- Custom events via
vero.track()for activation funnels - Anomaly alerts on traffic and revenue, plus an AI weekly digest on what moved revenue
- Tracker from 1.2 KB, served from the edge
Worked example from the public demo
From the home page to a trial, by source
This is the public demo: a fictional SaaS in its launch week, with €18,423 in sales over 16,491 sessions. Here is how its funnel and its sources read, the way you would read your own.
A funnel that stops at the trial
Of the 3,659 sessions that start on /, 1,420 reach /pricing (38.8%), 520 sign up and 412 start a trial: 11.3% of the sessions that started. The funnel ends at
trial_startedbecause a trial is not paid for in the visit that opens it. The payment arrives later through your provider’s webhook, still tied to its source.Revenue per visitor, by source
The whole site makes €1.25 per visitor. Hacker News sent 3,420 visitors and €7,124, €2.08 each. Twitter sent 1,245 and €4,821, €3.87 each. The source that sends the most people is not the one that pays the most per visit.
A copy change, tested on the trial
The AB Designer test “CTA button copy” uses
trial_startedas its goal, over 3,661 sessions. The control converts at 2.9%, the variant at 4.2%: a lift of +43%, marked significant. Exposures count sessions, not pageviews.
Read as a SaaS founder: ship the winning copy, then put the next launch’s effort where each visitor earns the most, not where the most visitors come from.
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 I attribute revenue without cookies?
Yes. The session id of the visit travels with the checkout and comes back in your payment provider’s signed webhook, so each sale reaches Vero with its source: no cookies, and the IP is never stored.
Does it work with a React/Next SPA?
Yes. The optional SPA module auto-tracks client-side route changes in Next, React Router, Vue and SvelteKit.
Will a cookie banner still be required?
Your legal team decides that. What they will check: Vero writes nothing to the device, stores nothing that identifies anyone and uses the IP only in memory, to compute a hash with a daily salt. /transparency lists every field the tracker sends.
Keep reading
- The sale, tied to the visit that brought itPaste one webhook URL and every sale arrives with the source that earned it.
- Attribute Stripe revenue to its real source.Stripe revenue attribution with one webhook URL: every payment credited to the source that earned it, without tax and refund-adjusted. The IP is never stored.
- How to attribute revenue without cookiesAttribution does not need a persistent identifier. It needs to connect a payment back to the visit that caused it, and that works server-side, at the moment of payment.
- PricingPay for pageviews and custom events. Every Pro tier has every feature.
More use cases
- 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 - 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.
See the use case