Stop counting visitors. Start counting revenue.

For years I ran privacy-friendly analytics on my own projects, and every month I hit the same wall.

I could see a spike from some referrer. I could see which pages were popular. But when a sale came in, I had no idea which of those visitors actually paid me. My workflow was embarrassing: open Polar, check the payment timestamp, then dig through my traffic dashboard trying to guess where the buyer came from an hour earlier, because is not possible to see this on Polar, they are not an analytics tool.

The tools that answer this question come at a cost

GA4, Mixpanel-style setups, DataFast and most marketing attribution tools can tell you which campaign drove a purchase. But they do it by following people around: cookies, persistent identifiers, cross-session profiles. That means consent banners, GDPR headaches, and a data model I didn't want to force on my visitors just to answer a basic business question.

The privacy-first tools went the other way, they dropped the cookies, but they also dropped the answer. You get clean traffic numbers and nothing connecting them to money.

I wanted both. So I built Kobbe.

What it does

Kobbe is cookieless web analytics with revenue attribution built in. Setup is two steps: add a 1.8KB script tag, and connect your payment provider via webhook, Stripe, Polar, Paddle, Mollie, Shopify, and a few others.

Paid orders then show up next to your traffic:

• Attributed revenue per landing page and per source

• First-touch, last-touch, or linear credit

• How many touches happen before purchase

• Median time from first visit to purchase

• Which page paths show up most often before checkout

The question "did that spike from Reddit make me any money?" finally has a one-glance answer.

How it works without cookies

This was the part I cared most about getting right.

Normal analytics in Kobbe use no persistent browser-side identifiers at all. Same-day unique visitors are counted with a daily-rotating anonymous hash that can't be reversed and can't be linked across days. Raw IPs are never written to the analytics database. If a visitor has Global Privacy Control or Do Not Track enabled, the tracker stops before any request is sent.

Revenue attribution is opt-in and works with tab-scoped state only, attribution context lives in the browser tab during the session and doesn't become a long-lived visitor profile.

To be fully upfront: Kobbe runs on Cloudflare Workers, so requests are processed on Cloudflare's global edge. The company itself is EU-based, the Åland Islands, to be exact, it's where I live.

Everything else you'd expect

Real-time visitors, funnels, custom events, UTM campaigns, Search Console integration, and AI-referrer grouping, so you can see how much traffic ChatGPT and Perplexity actually send you, which is becoming a surprisingly interesting number.

Pricing is event-based. No feature-gating games.

There's a live demo you can explore without signing up:

https://app.kobbe.io/demo/kobbe-studio

If you try it, I'd genuinely love to hear where the attribution model holds up for you and where it doesn't, that feedback shapes what I build next.

/Mike