Event taxonomies and product analytics that hold up at scale.
I design event taxonomies, instrument products with Amplitude, and write up the reasoning behind analytics decisions — not just the dashboards.
Read analytics writing →Relevant projects
Runo Product Analytics & Amplitude Instrumentation
Worked on a product analytics layer at Runo — Amplitude provider abstraction, event taxonomy, user/company traits, deduplication, and platform-aware tracking across auth, billing, CRM, and call workflows.
Designing Hybrid Telephony for a Sales CRM
A deeper look at how cloud and GSM calling were unified into one hybrid telephony model at Runo, and what broke before the model existed.
Relevant writing
Sizing an event deduplication window
A short note on why a fixed time window for analytics event deduplication needs tuning, not just existing.
Turning scattered product behavior into systems
A recurring theme in product engineering: ambiguous, duplicated behavior across screens is more dangerous than it looks, and the fix is rarely glamorous.
Keeping sandbox traffic out of production analytics
Why analytics initialization should check environment/host before sending any events, not just before reporting them.
Relevant codelabs & research
Designing an Event Taxonomy for Amplitude
How to name events and properties so analytics stays usable as the product grows, instead of becoming hundreds of one-off strings.
Amplitude's Event Taxonomy Documentation
Amplitude's own guidance on event/property naming and taxonomy planning — used as a reference while building out the analytics layer described in the Runo Product Analytics project.
Comparing Event-Deduplication Strategies for Client-Side Analytics
An open investigation into time-windowed vs. idempotency-key deduplication for client-emitted analytics events, prompted by dedup work on the Runo product analytics layer.