Problem
Mixpanel was used without any convention: everyone named events their own way, the same action was tracked under several names, and properties and documentation were missing. The data couldn’t be compared or relied on.
My role
Designing an event tracking standard for the whole app and building a layer that enforces it in code.
What I built
- A tracking plan: a naming convention for events and their properties that applies across the whole app.
- A shared function for sending events, built the same way as the error reporting layer: one entry point instead of SDK calls scattered around the code.
- Cleaning up the existing data: removing duplicates and dead events that had piled up over the years.
- Documentation for the product team.
Outcomes
- Product managers work with the data on their own, without asking a developer how one similar-sounding event differs from another.
- Developers add new events through a single function, so following the standard is the default rather than a matter of memory.
- Data from different areas of the app became comparable.