Product Analytics Event Plan
Define events and properties before instrumenting.
The Open buttons send the prompt text as currently shown below to that site only when you click. Fill in the placeholders first.
[VERIFY] is an editorial flag, not a blank to fill. Wherever the prompt shows [VERIFY], check that item against a reliable source before you use it.
Create an analytics tracking plan. Product and key user flows: [PRODUCT_FLOWS]. Questions we want to answer: [QUESTIONS]. Tools: [TOOLS]. Define a naming convention, then a table of events with Event name | When it fires | Properties | Why we need it | Owner. Limit to the events needed to answer the questions. Specify user identification rules and privacy: no personal data in properties unless approved [VERIFY] with privacy counsel for [JURISDICTION]. Include a validation checklist for QA and a governance process for changes. Mark events that are optional. Add a quality assurance routine for releases that checks events in a test environment before they ship, and a deprecation process for events no longer needed. Provide an example of three events fully specified for an invented product, and a short guide to explaining the plan to engineers in a way that avoids over-tracking. Also add a short list of the events we should deliberately not track and the reasons, such as privacy risk or low value.
Fill in before use
Optional: type your details and the prompt above updates. Nothing is saved or sent.
Replace each bracketed placeholder with your own details, then paste into Any AI or another assistant.