Events, properties and naming convention
Poorly named or overly granular events produce data nobody dares to use anymore. This lesson helps a PM turn a user journey into events and properties at the right level of detail, then settle on a naming convention the whole team shares. It is the foundation of a tracking plan engineers can implement without back-and-forth.
Lesson objective
By the end of this lesson, you will be able to describe a flow as events and properties, choose the right level of detail, and write a naming convention the whole team applies.
Questions this lesson answers
- How do you turn a user journey into analytics events?
- What is the difference between an event property and a user property?
- How do you keep analytics event names consistent across a team?
Topics covered
- analytics events
- event properties
- user properties
- naming convention
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 (this lesson)
- Identity, accounts and event sources
- Write the tracking plan and the acceptance criteria
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