A tracking plan lists every event and attribute a site or app sends to the customer data platform: its name, fields, when it fires, and who owns it. It’s written before tracking is built and kept current after, so segments, campaigns, and reports all read from names that mean one thing.
Category
Tracking
Also known as
tracking spec; tracking specification; event spec
In practice
A plan that lives only in someone’s head, or only inside the platform, isn’t one you can review. Keep it as one shared table, review it whenever a campaign needs a field that isn’t there, and treat any event in the platform that isn’t in the plan as a defect to explain. The plan is also the fastest way to onboard a new consultant: it tells them what the account measures without a discovery project.
Something out of date?