|
|
|
|
|
|
by nip
1097 days ago
|
|
|
Custom analytics, very barebone: - A single “events” table in my DB (Postgres) - A simple POST /track request with some conventions: a type (error or analytics), a name and a jsonb of data (with similar conventions). - A couple of Postgres views for very specific “dashboards”: paying customers, referrers per week, etc… - A telegram bot with a few buttons that allows me to quickly get insights about the health of my system and analytics on the go - Privacy is very dear to me: I have full control over the code and storage and can ensure that only the utmost minimum is stored when it comes to my users’ data (I am blind of some fronts due to this but it’s a trade off that I’m willing to make) (In total I probably spent 10h building it, over the course of 4 years: very much worth it) |
|
|