NumberHill Analytics

Here's the loop I ran for months.

Tab one: analytics. A blog post did 40,000 visits. A paid campaign did 2,000. Tab two: Stripe. Revenue's up. Somewhere between those two tabs is the answer to "so what should I do more of?" — and I never had it. I had a hunch, a spreadsheet, and a budget I was spending on the hunch.

The thing is, both tabs are telling the truth. They just don't talk to each other. Analytics stops at the pageview and calls it a conversion. But nobody runs a business to collect pageviews.

So NumberHill Analytics starts from the payment and works backwards.

You drop in one script tag and connect your payment processor — Stripe, LemonSqueezy, Polar, Shopify or Dodo Payments. From then on, every channel, page and campaign in your dashboard has a real dollar figure next to it. Not an assumed conversion value you typed into a settings box once and forgot. The actual money that actually landed.

A few things I cared about while building it:

• Revenue per visitor, not conversion rate. A channel with a 1% conversion rate and $400 orders beats a 6% channel selling $9 add-ons, and I wanted that to be obvious at a glance.

• Honest zeros. There's no demo data anywhere in the app. A site with no traffic shows zeros and tells you to install the script. I'd rather look empty than look fake.

• Bots don't count as customers. AI crawlers get verified against their real IP ranges, so a spoofed GPTBot doesn't quietly inflate your best-performing page.

• No cookie banner if you don't want one. There's a cookieless mode with 24-hour rotating IDs.

It's live and there's a free plan, so you can point it at something real and see whether the numbers match what you expected. In my experience they usually don't, which is sort of the whole point.

What I'd genuinely like to know: when you look at your analytics today, what's the question you can't answer? That's the list I'm building from.