Data
Design a tracking plan
The events, properties and naming a product analytics setup needs.
Fill it in
What people do in it.
What the data is for.
Before anyone implements anything.
Your prompt
Design the tracking plan. [the product] Questions to answer: [your questions to answer] Start from the QUESTIONS and work back to events. A plan built by walking the UI produces four hundred events, of which six get used, and the analysis you actually wanted turns out to need a property nobody captured. Define the naming convention before anything is implemented: object then action, past tense, lowercase with underscores, and properties named the same way everywhere. Renaming later means a migration nobody does. Specify the properties per event with types and allowed values. An event with no properties can be counted and nothing else. Say explicitly what NOT to track, and never put personal data in a property.
Use Design a tracking planOpens with everything above already filled in.
Why this works
A plan built by walking the UI produces four hundred events, six of which get used, and the analysis you wanted needs a property nobody captured. This works back from the questions, fixes the naming before implementation, and says what not to track.