How would you set up tracking for a newly launched feature?
Model answer
Model answerBefore writing a single tracking spec, I'd define what questions I need to answer in 30 days. Then I'd map the feature's user journey and identify the key moments: feature discovered, attempted, completed, and returned to. Each moment gets an event. I'd track both success and failure states — where users drop off is as important as where they succeed.
Framework · Event Tracking
- QQuestions first
What do you need to know in 30 days? Let that drive your event design - JJourney mapping
Map the full user journey — every step is a potential event - SSuccess and failure
Track both completions and drop-offs — failures are the most valuable data - CControl group
Always define what 'without this feature' looks like for comparison
Related questions
- How would you define success for a new user onboarding flow?
- What metrics would you track for a social sharing feature?
- What is the difference between a vanity metric and an actionable metric?
- What is a cohort analysis and when would you use it?
- You launch a feature and usage is lower than expected. How do you investigate?