Skip to main content

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.

  1. 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_started because 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.

  2. 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.

  3. A copy change, tested on the trial

    The AB Designer test “CTA button copy” uses trial_started as 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.

Every field the tracker sends

More use cases

Measure the channels that bring paying customers

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

See the demo