Tracking Plan

A tracking plan is the written specification of which events a product records, what each one means, and which properties every event must carry.

Each row fixes an event name, the exact condition that triggers it, the required and optional properties, their data types and allowed values, and the owner who answers questions about it. Written before the code, it is the contract that instrumentation is reviewed against and that ingestion-time validation enforces. Without one, two teams instrument the same action under two names, and a drop in a chart can no longer be told apart from a broken release. The real enemy of the plan is drift: a document that is never compared with the live event stream stops being a contract within a couple of releases and becomes stale documentation.