Instrumentation Architecture Overhaul
Replaced a fragmented tracking system with a unified taxonomy that made every event across every surface predictable and reliable.
Blinkit's instrumentation had grown organically across multiple app surfaces and teams. Events were named differently depending on which team had built the surface, properties were missing or inconsistent, and there was no shared taxonomy — making cross-team product analytics unreliable and difficult to act on.
Design and implement a unified instrumentation taxonomy that would make every event across every app surface predictable, consistent, and self-documenting — eliminating the specification ambiguity that was making product data impossible to use coherently across teams.
Instrumentation failures are almost always a specification problem, not an engineering problem. When there is no authoritative taxonomy, every team invents its own conventions — events named differently across surfaces, properties missing or inconsistent, location data that cannot tell you where in the app something happened. The result is data that is impossible to use coherently across teams.
The redesign was built around two core principles: events follow a noun + verb in past tense format, making their meaning unambiguous from the name alone, and every event carries the same four property groups — app, device, user, and location — with the location hierarchy detailed enough to answer "exactly where did this happen" for any event on any surface.
- 01Audited existing instrumentation across all app surfaces: catalogued every event, identified naming inconsistencies, missing properties, and undocumented tracking decisions.
- 02Designed the unified taxonomy: noun + verb (past tense) naming convention, with four standard property groups — app properties, device properties, user properties, and a hierarchical location structure covering page name, page variant, parent widget location, parent widget title, child widget location, and child widget title.
- 03Wrote the full event specification for every key user action across the application as a tracking plan engineering could implement against without interpretation.
- 04Implemented the new instrumentation across all surfaces, validated each event end-to-end from trigger through to the warehouse.
- 05Deprecated legacy events surface by surface after validating parity with a parallel running period.
- 06Documented the taxonomy and property standards so new surfaces could be instrumented to specification without data team involvement.
- Unified taxonomy implemented across all Blinkit app surfaces — every event named consistently and unambiguously
- Four standard property groups applied to every event, making cross-surface analysis reliable for the first time
- Full event specification written and handed to engineering as a tracking plan, removing interpretation from the implementation process
- New surfaces instrumentable to spec without data team involvement
Start a conversation.
Every engagement begins with a focused discussion of your current data environment and priorities. To schedule an initial consultation, reach out directly.
Get in touch