Statable Team

@supplyautomate Thanks Raj. Consent banners are usually what starts the search, and the history is what stops people going through with it.

@zacksoftware Thanks. The import was the part that took longest to get right. It is also what people ask about most, since the usual alternative is running both tools side by side for a year before you trust the new one.

@addisonalbert577 Thanks. Removing the banner is half of it, the other half is that you stop losing the visits where someone declines.

@gofin Thanks Mykola. The MCP part is the one I did not expect people to notice this early, so it is good to hear. It runs on the same scoped API keys as everything else, so you can hand an agent read only access to a single site and nothing more.

If you do try it on a real project, I would like to hear where it falls short. That is the feedback I am short of right now.

@letsconnectcards Thanks, appreciate it. The next piece we are building is server side crawler stats, since a JS tracker misses almost all AI crawlers. Unglamorous but it is the gap we keep hitting.

@jenifergeorge023 Thank you, that is good to hear. Interface was the part we fussed over most.

Hey! I'm Yevhen, founder of Statable.

I built it after watching the same story repeat: a team wants to leave Google Analytics — because of consent banners, complexity, or both — and then realizes switching means throwing away years of historical data. Most stay stuck.

Statable is cookieless web analytics hosted in the Netherlands (EU). No cookies, no fingerprinting, no consent banner needed. And it imports your existing Google Analytics history into the same charts, so the switch doesn't start from zero.

Also: free for open-source and educational sites. Would love your feedback — especially from fellow GA4 refugees.