analytics-debt

This post introduces the Core Entity Test to decide when to create new events versus reusing existing ones with more properties. It includes real-world pitfalls around analytics debt and rising costs, with insights on designing for long-term maintainability.

Based on product audits, this post explains how exceeding 30 core events leads to confusion, duplicative metrics, and inflated tooling costs. Timo recommends modeling a small set of core entities and using properties to capture UI-specifics. Includes governance tips.