Document a tracking plan
When you need a tracking plan documented so events, properties, and data flow are consistent and auditable across tools.
0 views0 downloads
Dependencies
--- name: document-tracking-plan description: "When you need a tracking plan documented so events, properties, and data flow are consistent and auditable across tools." ---
Document a tracking plan
Instructions
Use this skill when the user wants to create or update a tracking plan for marketing and product analytics. The job: a single document that lists events, properties, and where data is sent so teams can implement and audit.
Instructions
- Events: List key events (page_view, signup, purchase, etc.) with a one-line business definition and owner.
- Properties: For each event define standard properties (e.g. source, medium, campaign, user_id) and type (string, number, etc.).
- Source: Document where each event is sent (GA4, CRM, warehouse) and how (tag, server, SDK).
- Governance: Naming convention, who can add events, and review cadence. Keep to a few bullets.
- Output: Table or structured list the user can paste into a doc or sheet.
Use case
Ensuring your engineering and marketing teams are tracking the exact same user behaviors with consistent naming.
How to use this skill
List the 5-10 major milestones you want to track across your website or app.