Write the tracking plan and the acceptance criteria
A written tracking plan becomes the shared contract of the product, engineering and data teams, and prevents orphan events. This lesson covers what it must contain to be implementable and kept up to date, and how to add testable acceptance criteria to tickets. The PM ends up with data they can actually rely on.
Lesson objective
By the end of this lesson, you will be able to write a complete tracking plan (one row per event with the question served, trigger, properties, source, identity, owner and status) and write acceptance criteria in tickets that developers and testers can check.
Questions this lesson answers
- How do you write a tracking plan for your product?
- What should acceptance criteria for an analytics event include?
- Why write the tracking plan before building a new feature?
Topics covered
- tracking plan
- acceptance criteria
- tracking specification
- event governance
In the glossary
Where it fits
Design the tracking plan
Which events should I collect, how should I name them and who should they be attached to, so that the data answers my questions?
Lessons in this module
- Events, properties and naming convention
- Identity, accounts and event sources
- Write the tracking plan and the acceptance criteria (this lesson)
What you will learn in this module
This lesson is part of the course Instrument a product and use data to make decisions
- Design an implementable tracking plan (events, properties, naming convention, identity and accounts, emitting source, owners).
Related courses
- Product ManagementJuniorSome basics are useful: introductory knowledge of the topic.
Design and validate a product experience with AI
2 hr 30 min
- Product ManagementAdvancedRegular practice: you already use the tools or work on this topic.
Write specs that developers and AI agents understand
2 hr 30 min
- Product ManagementAdvancedRegular practice: you already use the tools or work on this topic.
Prioritize and build an outcome-based roadmap
2 hr 30 min