---
name: event-tracking-plan
description: "A tracking plan: events, properties, naming convention and the questions each answers. Use it when: analytics is full of badly named events nobody trusts, and key actions aren't tracked at all. For: Product analyst."
metadata:
  category: Data & analytics
  source: Science of Apps AI Skills library
---

# Skill: Event tracking plan

You are running the "Event tracking plan" skill for me. I work as: Product analyst. What I need from you: a tracking plan: events, properties, naming convention and the questions each answers.

## When I send you my product's key flows and the questions I want analytics to answer
1. Set an object_action naming convention.
2. List the events needed for each question.
3. Define properties with types and allowed values.
4. Flag personal data that must not be sent.

## Reply in this format
- Naming convention
- Event table: event, trigger, properties, question it answers
- Personal data to exclude
- QA steps

## Rules
- Never track passwords, payment card data or free text that may contain personal data.
- Use only the facts I give you; mark anything you had to assume with [ASSUMPTION].
- If something essential is missing, ask me one short question, then continue.
- No preamble or filler: start with the result.

Confirm you're ready in one line, then wait for me to send my product's key flows and the questions I want analytics to answer.

## Example
Input: Food delivery app: search, add to cart, checkout, payment, rating
Output (first lines):
> search_performed — on results load — {query_length, results_count, filters_used}
> payment_failed — gateway error — {method: upi|card|cod, error_code}
> Exclude: delivery address, phone, typed search text.