[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"glossary-tracking-plan::en":3,"gloss-cluster-tracking-plan::en":23,"gloss-next-tracking-plan::en":9},{"slug":4,"category":5,"name":6,"definition":7,"meta_desc":8,"faq":9,"schema_markup":9,"related":10},"tracking-plan","analytics","Tracking Plan","A tracking plan is the single source of truth that defines every analytics event you collect — its name, when it fires, and the properties attached to it. It's a spreadsheet or schema (Avo, Segment Protocols, and Iteratively formalize it) that keeps `Signup Completed` from also appearing as `signup_complete`, `Sign Up`, and `SignupDone` across three developers. For builders, an untracked or inconsistently tracked product is one where every funnel and cohort is quietly wrong, and nobody notices until a board metric looks off. The plan enforces naming conventions (usually object-action, past tense), a typed property schema, and an owner for each event. Practical note: write the plan *before* instrumenting, version it in git, and validate incoming events against it in CI so a rogue `event: undefined` gets rejected at build time rather than polluting your warehouse for months. Treat it as a data contract between product, engineering, and analytics — renaming a live event breaks every downstream report.","A tracking plan is the source of truth for every analytics event — name, trigger, properties — so one signup doesn't arrive as four differently spelled events.",null,[11,14,17,20],{"slug":12,"name":13},"autocapture","Autocapture",{"slug":15,"name":16},"customer-data-platform","Customer Data Platform (CDP)",{"slug":18,"name":19},"data-contract","Data Contract",{"slug":21,"name":22},"product-analytics","Product Analytics",[24,28,31,33,36,37,40,43,46,49,52,55],{"slug":25,"category":5,"name":26,"updated_at":27},"ab-testing","A\u002FB Testing","2026-08-24T02:46:38+00:00",{"slug":29,"category":5,"name":30,"updated_at":27},"active-user","Active User (DAU, WAU, MAU)",{"slug":12,"category":5,"name":13,"updated_at":32},"2026-08-24T02:46:37+00:00",{"slug":34,"category":5,"name":35,"updated_at":27},"cost-per-resolution","Cost per Resolution",{"slug":15,"category":5,"name":16,"updated_at":32},{"slug":38,"category":5,"name":39,"updated_at":27},"deflection-rate","Deflection Rate",{"slug":41,"category":5,"name":42,"updated_at":27},"guardrail-metric","Guardrail Metric",{"slug":44,"category":5,"name":45,"updated_at":32},"identity-resolution","Identity Resolution",{"slug":47,"category":5,"name":48,"updated_at":32},"multi-touch-attribution","Multi-Touch Attribution",{"slug":50,"category":5,"name":51,"updated_at":27},"novelty-effect","Novelty Effect",{"slug":53,"category":5,"name":54,"updated_at":32},"retention-curve","Retention Curve",{"slug":56,"category":5,"name":57,"updated_at":27},"sample-ratio-mismatch","Sample Ratio Mismatch (SRM)"]