“Instead of tracking 'download clicked, download started, download completed', if you're focusing generically you can say 'button clicked' and give keys to those buttons — ensure there's structure in how that's built. Now when someone comes and says 'we need to know when they hit download and then pause and then share' — well, either way those were clicks of those actions and I've mapped that behind the scenes.”

Build Generic Modular Event Tracking to Avoid Rewriting Your Data Stack Later

Disney+ built Glimpse — a generic click-stream event structure where every interaction is a 'button_clicked' with hierarchical keys, not a bespoke named event per action. When product added new features, the data infrastructure didn't break. Taylor Wells recommends this for any product: define a taxonomy of generic event types with keyed metadata, so new product features get tracked automatically without requiring new instrumentation.