Tracking debt is what happens when your event schema keeps growing but nobody cleans it up. Events added two years ago still fire from zombie code. Three different PMs have named the same action three different ways. Your dashboard shows… Tracking Debt: How It Accumulates and How to Pay It Down
Subscription businesses run on five revenue metrics — MRR, trial-to-paid, expansion, churn, and reactivation — and every one of them is built from the events below. When I joined a Berlin SaaS client in 2023, their billing system fired four… Subscription Event Schema: The Complete Reference
Standard ecommerce tracking gives you four events — view_item, add_to_cart, begin_checkout, purchase — and calls anything in between “abandonment.” For one DACH apparel client in 2024, those four events left us blind to 38% of the drop-off. The biggest losses… The Cart Abandonment Signal: 7 Events You’re Probably Missing
I live in Munich, run analytics projects across the EU, and have watched the same consent banner get approved in France, questioned in Italy, and rewritten in Germany — all in the same quarter. On paper, the GDPR and ePrivacy… CNIL, Garante, BfDI: How Three EU Regulators Interpret Analytics Consent Differently
I’ve watched three product teams in the last year ship tracking that looked fine on paper and returned unusable data in GA4. Every time, the root cause was the same: the tracking spec was written for analysts, not for the… Tracking Specs: How to Write One Engineers Actually Implement
A consistent naming convention is the foundation of clean analytics data. Without standardized naming, your GA4 reports become cluttered with duplicate events like button_click, Button_Click, and buttonClick — all tracking the same interaction but appearing as separate events. This guide… GA4 Event Naming Conventions: A Practical Guide