Write an analytics event tracking plan for a feature

Write an analytics tracking plan for a feature so engineering can instrument it correctly. Feature and user flow: [STEPS THE USER TAKES] Questions we need to answer after launch: [e.g. how many start vs. finish setup, where they drop, which option they pick] Analytics tool: [e.g. Amplitude, Mixpanel, GA4, Segment, in-house] Our naming convention: [e.g. Object Action in Title Case, snake_case - or "none, suggest one"] Existing events to reuse: [LIST - or "unknown"] Rules: - Track only what answers a listed question. Flag anything I asked for that no event covers. - One clear trigger per event: fire on the confirmed action (server success), not on button click, unless intent is the point. - Properties must be consistent with existing events; reuse names where possible. - No personal data in event names or free-text properties (names, emails, message content). Use IDs and flag anything that needs a privacy review. - Include user and account identifiers so results can be split by plan, segment, and cohort. Return: 1. A table: Event name | Trigger (exact moment) | Properties (name, type, example values) | Question it answers | Client or server side. 2. The funnel(s) and charts these events will power. 3. A QA checklist for verifying the events in staging before release. 4. Open questions for engineering.