Write an Event Tracking Plan Where Every Event Maps to a Success Metric
Get a tracking plan table with object_action event names, exact triggers, typed properties and the success metric each event feeds, plus a list of events to cut.
You getNaming conventions, event table and metric coverage
Prompt
You are a senior product analyst who writes event tracking plans engineers can implement without follow-up questions.
Your job: build a tracking plan for a feature or flow I am launching. First, ask me these questions in one message and wait for my answers:
1. What is the feature or flow, and what are its main user steps?
2. Which success metrics will we judge it by?
3. Which analytics tool do we use, and which existing event names must we stay consistent with?
4. Which platforms does it run on (web, iOS, Android, backend)?
Rules:
- Name every event in snake_case object_action form with a past-tense verb (invoice_sent, not SendInvoice or clicked_send).
- Map every event to at least one success metric. Any event that feeds no metric goes in a "Cut or justify" list, not the main plan.
- Each trigger states the exact moment it fires (for example, on server confirmation rather than button click) and the platform.
- Properties use snake_case with a data type and example value. No personal data such as emails or names.
- Every metric must be calculable from the listed events; flag any metric missing an event.
Output format:
1. Naming conventions (3-5 lines)
2. Event table: Event name | Trigger | Platform | Properties (type, example) | Metric it feeds
3. Metric coverage: each metric with its formula built from events
4. Cut or justify list
5. QA checklist (5 items)
End with one line on assumptions and gaps that need my decision.Example output
Tips and common edits
Why this works
- The object_action, past-tense rule with a bad example gives consistent names engineers and analysts can search.
- Forcing each event to map to a metric pushes orphan events into a visible cut list before they ship.
- Requiring metric formulas built from events exposes missing instrumentation while it is still cheap to add.
Use before engineering starts instrumenting a new feature. Have your user flow, success metrics and current event names ready. Works in ChatGPT, Claude or Gemini; paste the table into your tracking spec.
Common edits
- Ask for the event table as CSV so you can import it into your tracking spec or Avo.
- Add a column for owner and implementation status to use it as a launch checklist.
Prompt details
- By
- Prompts-GPT editors
- Published
Did this prompt work?
Keep exploring
More like this
Define a North Star and Success Metrics for a New Feature with Guardrails
Get a North Star metric, up to three primary metrics each paired with a guardrail, exact formulas from your existing data, targets, and ship or roll-back rules.
Diagnose a Sudden Metric Drop with a Ranked List of Likely Causes
Get a ranked table of likely causes for a metric drop, covering tracking, segments, platforms, releases, seasonality and external factors, each with an exact check.
Analyze Your Product Funnel and Find the Biggest Drop-Off to Fix First
Paste your funnel step counts and get a conversion table, the largest leak flagged with reasoning, and one testable fix per step with an expected lift range.
Design an A/B Test Plan with Sample Size Math and Pre-Set Stop Rules
Get a complete A/B test plan with one primary metric, a clear hypothesis, a worked sample size calculation, runtime, and stop rules fixed before launch.
Run a Post-Launch Retrospective Comparing Goals to Actual Results
Get a blameless launch retrospective with a goal-versus-actual table, facts kept apart from causes, and lessons that each carry an owner and a change for the next launch.
Write a Go-to-Market Launch Plan with Owners, Dates and Go/No-Go Criteria
Get a tiered launch plan with a T-minus timeline, one owner role per task, measurable go/no-go criteria, an hour-by-hour launch-day checklist and week-one metrics.