Blog
Follow via RSS →Measure the money.
Short essays on cookie-free measurement, revenue attribution, and growth that pays.
Cookie-free analytics: how it counts visits, what it misses and what the law saysAnalytics without cookies counts visits without leaving anything on the device. How that works, what it can and cannot measure, what the rules say about consent, and how to check a tool before you install it.
In this article
- What is cookie-free analytics?
- How does analytics without cookies count unique visitors?
- What can cookie-free analytics not measure?
- Do cookie-free analytics need a consent banner?
- What a consent banner costs the analytics behind it
- How do you choose privacy-friendly analytics?
- Does cookie-free analytics get past ad blockers?
- How Vero does cookie-free analytics
- Revenue attribution: what it is, which model to use and how to do itRevenue attribution puts a source next to every sale, so you rank channels by money instead of clicks. What it is, which model to pick, how a Stripe, Lemon Squeezy or Paddle payment gets tied to a visit, and where it stops.
- How to pass UTM parameters and the visit to Stripe CheckoutUTM tags do not survive the redirect to checkout.stripe.com. How to carry the source in client_reference_id and metadata, read it back from the webhook, and why carrying the visit is simpler.
- First-touch vs last-touch attribution for a small SaaSFirst touch credits the source that found the customer, last touch the one that was there when they paid. What each gets wrong, what renewals and long trials do to both, and the rule Vero uses.
- Launch-week analytics: Hacker News, Product Hunt and the moneyA launch sends a wave of traffic for a few days and then it leaves. What to set up before, what to watch on the day, and how to tell which launch actually paid.
- Traffic from ChatGPT and Perplexity: measure AI as a channelPeople ask an assistant, the assistant cites a page, and some of them click. Here is how to see those visits as their own channel, and what they are worth in money.
- Revenue by source is not profit: subtract the ad spendA paid channel can top your revenue table and still lose money. How to put spend next to revenue for every source, worked through on a real-looking week.
- 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.
- What your analytics script costs your Core Web VitalsEvery script on a page competes with the page itself. How to measure what your analytics actually ships, what besides bytes it costs, and how to keep the bill small.
- Stop optimizing for vanity trafficVisits feel like progress. A source can send hundreds of visits and no sale, and a dashboard that ranks by traffic will put it near the top.
- 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.
- What a consent banner costs your analytics, in visits and revenueAnalytics that waits for consent only counts the visitors who accept. What that does to your traffic, your sources, your conversion rate and your revenue attribution, and what changes when nothing is written to the device.
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.