Fill in these first
- Product and platform: [e.g. web app, Android and iOS app]
- Analytics tool: [e.g. Google Analytics 4, Mixpanel, Amplitude, other]
- Questions the team needs answered: [e.g. where do new users drop off before first order]
- Key user flows: [list the steps of two or three flows]
- Existing events, if any: [paste names or none]
- User properties you can attach: [plan, signup date, city, device]
Task
Write a tracking plan that answers the questions with the fewest events possible.
Output format
- Naming rules: object-action format in snake_case, such as
order_placed, with three examples and three counter-examples. - Event table:
| Event name | Fires when | Platform | Properties (name: type) | Question it answers |
- User properties: | Property | Type | Set when |
- Funnels: each key flow written as an ordered list of events.
- Events to remove or rename from the existing list, with reasons.
- QA checklist for developers: at least eight checks before release.
Rules
- Each event fires on a completed action, not on a button view, unless view tracking is needed for a question.
- No personal data such as names, emails, phone numbers or full addresses in event properties.
- Keep the plan under 25 events; group variants with a property instead of new events.
- Mark any property whose value list is unknown as [define values].






