Disney+ · B2C · Disney's streaming service
Log one generic 'button clicked' event with keys, not a new event per feature
Guest says it avoided costly renames and merges; still in use years later
Workedanalytics-attribution
What they did
Instead of events like download_clicked/started/paused/completed, track a generic click action with hierarchical keys (button within container within set within page). Map keys to meaning behind the scenes and enrich the stream downstream (e.g. classify as 'project created') for each team, while keeping the raw data. Capture state changes instead of repeating ~100 identical metadata fields on every event. Give the system a memorable, unambiguous name (Glimpse, replacing 'UAT', which clashed with User Acceptance Testing) so everyone knows what 'the events' means.
What happened
Guest says it let new questions (e.g. download, pause, share sequences) be answered without re-instrumenting or merging renamed events; the system is still in use at Disney+.
In their words
Sub Club by RevenueCat · Building an Effective Data Product Strategy — Taylor Wells, News Corp“But instead, if you're focusing generically, you can say, "I'm going to build tracking for button clicked or click action," and then give keys to those buttons, ensure that there's structure in how that's built.”
“Glimpse is the internal event structure of clickstream data within Disney+, which is still there today, at least as of the last time that I'd looked.”
Related topics
Get tactics like this every Monday
New tactics from the week's founder interviews, each linked to where it was said.
More from Disney+
All 7 Disney+ tacticsMore from this episode
- Disney+: Build your own event tracking, keep Adobe as a backup, then drop Adobe~$1K/day in-house vs ~$33K/day for Adobe; Adobe removed within weeks
- Disney+: Email the boss three bullet points by noon each day instead of dashboardsThe president stopped needing dashboards; no numbers
- Disney+: Move a show with near-100% completion up from the last row of the home screen
- Disney+: Group viewers by household, like parents or single adults, not by fan typeHousehold groups predicted behavior better; over half the audience were single adults
- RevenueCat: Start on Amplitude; add a data pipeline once product changes break your definitionsCo-host says it smoothed definition changes for data users; no numbers
- Dump app event logs into a plain SQL database instead of buying analyticsToo hard to explore, so nobody asked questions; moved back to Mixpanel
- Buy analytics tools first, but set dates to decide whether to switchGuest says companies without checkpoints get stuck with rising vendor costs; no numbers