About TrackWhy
We built TrackWhy because we were tired of analytics that show you a chart and then stop. You see the top ten pages, the top ten referrers, the top ten countries — and the moment you want to know why, the tool dead-ends. No way past rank ten, no way to click a row and filter everything else, no honest answer to a follow-up question.
Most analytics tools are built to report, not to investigate. They give you a tidy summary and call it a day. But real questions live below the fold: which of the three hundred pages in the long tail is quietly converting, which campaign actually drove revenue rather than just traffic, where in a funnel people give up. If you can only see the top ten of anything, you can’t answer those questions — you can only guess.
And then there’s the trust problem. Too many tools compute their headline metrics wrong. Bounce rate is the classic example: under the engagement model some popular tools ship, it collapses to a broken near-zero that means nothing. We compute it the honest way — the share of single-pageview sessions — because a number you can’t trust is worse than no number at all.
We’re engineers who actually read our numbers, and we kept hitting the same wall. The heavyweight platform was slow, demanded a cookie banner and still buried the answer three menus deep. The lightweight privacy tools were refreshingly simple but capped out exactly when a question got interesting. Nobody offered both: the depth to drill down and the decency to do it without tracking people.
So we built the tool we wanted. TrackWhy gives you search, sort and pagination on every breakdown, click-to-filter that drives the whole dashboard, funnels, retention cohorts and journey paths from one consistent filter algebra — plus Stripe revenue attribution so you can tie traffic to money. And it does all of it from a single 1.7 KB script.
Privacy isn’t a feature we tacked on — it’s a constraint we designed around. TrackWhy is cookieless, sets nothing on the visitor’s device, never stores IP addresses, never fingerprints and never tracks anyone across sites. That’s what keeps it clear of GDPR, ePrivacy and CCPA consent requirements, and it’s why your site needs no cookie banner. You can read exactly what we do and don’t collect on our privacy page — it doubles as the spec.
That’s the whole pitch: real drill-down, honest metrics, privacy by default. If that’s the analytics you’ve been missing, come try it.