TrackTrendy: The Analytics Engine I Decided to Own

My clients get an analytics dashboard with their hosting plan, and for a while a third-party engine powered it. That meant every report depended on infrastructure I did not control, with per-site costs that scaled against me. I wanted a privacy-first, cookieless analytics product I own outright: the tracker, the ingest pipeline, the query layer and the billing. The catch: the portal was already live, so the swap had to be invisible.

I built a native analytics engine with a dedicated Postgres event store and a 1.5 KB vanilla JavaScript tracker served from a Cloudflare Worker. The ingest pipeline does bot filtering, browser and OS parsing, referrer classification, UTM capture and salted daily visitor hashing with 30-minute sessions. Then I moved the whole history over.

• Migrated 130,677 events and 54,387 sessions across 29 domains
• Imported 506,090 rows of Google Analytics history in 8 seconds
• Verified the cutover with 1,218 automated validation checks, all passing
• Added an AI assistant that explains trends and answers questions in chat

The production cutover took one supervised morning and the portal UI stayed byte-identical, so clients never noticed the engine change. TrackTrendy now runs 29 sites on infrastructure I own end to end, with Stripe billing live and zero third-party analytics fees. The AI assistant reads the same data and turns it into plain-language insights.