I’m building https://analytics.robomiri.com, a lightweight, privacy-first analytics tool that gives you real insight without turning your users into tracked profiles. It captures page views, content engagement, funnels, and user paths in a minimal UI.
My goal is to balance usefulness with simplicity: metrics you can act on, not just dashboards to stare at. I’m leaning hard on defaults like anonymization, flexible retention, and user control over what’s collected.
The hardest parts are always the ones you don’t see: scaling storage & query times, making interpretation meaningful (like “this bounce rate is unusually high”), and doing all of this in a way that’s GDPR/CCPA friendly.
Why do this? Because I believe analytics doesn’t need to feel creepy. You should be able to learn about your users respectfully — see what’s working, diagnose what’s broken — without handing over control or trust.
I had an issue trying to setup funnels or build custom queries on the events from the web.
I think that this question should go more towards the marketing teams that are using web analytics extensively l.
The hardest parts are always the ones you don’t see: scaling storage & query times, making interpretation meaningful (like “this bounce rate is unusually high”), and doing all of this in a way that’s GDPR/CCPA friendly.
Why do this? Because I believe analytics doesn’t need to feel creepy. You should be able to learn about your users respectfully — see what’s working, diagnose what’s broken — without handing over control or trust.