wowprompt

Product Analytics Event Tracking Plan

Writes a tracking plan that lists the events, properties and naming rules a product needs to answer its key questions, ready to hand to developers. Use it before launching a feature or when analytics data is messy and nobody trusts the numbers.

A tracking plan with naming rules, an event table with trigger, properties and types, a funnel definition and a QA checklist for developers
The output this prompt produced, unedited.

The prompt

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

  1. Naming rules: object-action format in snake_case, such as order_placed, with three examples and three counter-examples.
  2. Event table:

| Event name | Fires when | Platform | Properties (name: type) | Question it answers |

  1. User properties: | Property | Type | Set when |
  2. Funnels: each key flow written as an ordered list of events.
  3. Events to remove or rename from the existing list, with reasons.
  4. 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].
event tracking planproduct analyticsanalytics eventstracking specificationevent naming conventionproduct metrics

How to run this

Copy the prompt and paste it into Gemini, then set the aspect ratio to 3:4. No reference photo is needed for this one.

The prompt is written in Markdown with each part under its own heading, which is what the copy action hands over. Change one section at a time, keeping the rest intact, so you can tell which change did the work.

Related prompts

All productivity