Thanks for the detailed response, Glen! Session-based grouping is a smart interim solution — it handles the most common noise patterns without over-complicating the pipeline.
On the server-side SDK roadmap: one thing I've seen work well is offering a lightweight HTTP endpoint that accepts batched events. That way, even if the JS snippet gets blocked, backend integrations (Node, Python, Go) can still feed data in. Umami does something similar and it's been effective for privacy-conscious users who still want analytics.
I'm building a SaaS starter kit myself (PubliFlow) and one of the trickiest parts was deciding whether to bundle analytics or let users plug in their own. Curious — would you consider offering a self-hosted version at some point? That could be a nice complement to the hosted tool.
Keep building! 🚀
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Thanks for the detailed response, Glen! Session-based grouping is a smart interim solution — it handles the most common noise patterns without over-complicating the pipeline.
On the server-side SDK roadmap: one thing I've seen work well is offering a lightweight HTTP endpoint that accepts batched events. That way, even if the JS snippet gets blocked, backend integrations (Node, Python, Go) can still feed data in. Umami does something similar and it's been effective for privacy-conscious users who still want analytics.
I'm building a SaaS starter kit myself (PubliFlow) and one of the trickiest parts was deciding whether to bundle analytics or let users plug in their own. Curious — would you consider offering a self-hosted version at some point? That could be a nice complement to the hosted tool.
Keep building! 🚀