Write an analytics tracking plan for a new feature

Write an analytics tracking plan for the feature below, for the engineers who will add the tracking and the analyst who will build the reports, so that on launch day we can answer the questions listed without another release.

The feature and its user flow:
"""
{{feature_flow}}
"""

Questions we need to answer after launch: {{questions}}

Our event naming convention and existing events, if any:
"""
{{conventions}}
"""

Analytics tool: {{tool}}
Data we must not collect (privacy rules, regulated data): {{privacy_rules}}

Produce:
1. A table of events with the columns Event name, Fires when (the exact user action or system moment), Properties (name, type and example value), Answers question number. Name events as object then past-tense action, for example report_exported, unless our convention says otherwise.
2. For each question, the events and the calculation that answer it, such as "share of accounts that fire report_exported within 7 days of report_created".
3. Success metrics: up to 3, each with its definition.
4. QA checklist: how a tester confirms each event fires once, at the right moment, with the right properties.

Keep to the fewest events that answer the questions, no more than 12, because every extra event costs engineering time and clutters the reports. Reuse existing events where they already capture the moment.

Never include names, email addresses, free text typed by users, or anything our privacy rules list, as a property. Use IDs instead.

If a question cannot be answered from events in this flow, for example because it needs revenue data from another system, say so next to that question instead of inventing an event for it. If the flow leaves a step unclear, list it under "Questions for the team".