Tracking Plan
Data & TrackingAlso: Measurement Plan · Analytics Tracking Plan
Quick definition
A tracking plan is a document that lists every event, property and naming convention a business will track across its website, app and marketing tools. It acts as the blueprint that analysts, developers and marketers all build from, so data lands consistently in tools like GA4 and the CRM.
How it varies across Australia
Most Australian small and mid-sized businesses have no tracking plan at all. Larger organisations tend to have one, but it's often stale within a year as new campaigns and tools get bolted on without updating the document. The gap between businesses with a maintained tracking plan and those without shows up clearly in how usable their attribution and conversion data actually is.
See data and tracking maturity across Australian industries →What it actually means
A tracking plan is the shared map that stops your website, your CRM and your ad platforms from speaking three different dialects about the same customer action.
Without one, every developer names events however feels natural that week. "Purchase", "purchase_complete" and "order_confirmed" might all describe the same thing, sitting in three different reports, none of which talk to each other. Attribution breaks quietly. Conversion rate gets calculated on whichever event someone happened to pick.
A good tracking plan lists the event name, when it fires, what properties it carries (order value, product category, campaign source) and which tool receives it. It ties directly into the data layer, the structured data feed that sits between your website and tools like GA4 or a tag manager.
The plan isn't a one-off document. Campaigns change, new landing pages launch, a UTM parameter naming convention gets forgotten by a new hire. Businesses that treat the tracking plan as a living reference catch these drifts before they cost a quarter of clean data. Businesses that write it once and file it away end up rebuilding their entire tracking a year later, usually right when they need the numbers most.
A tracking plan is boring paperwork right up until the day someone asks why three tools report three different conversion counts.
How it shows up
A tracking plan shows up as a shared spreadsheet or document that lists every tracked event, its trigger condition, its properties and its destination tool. In practice you'll see it referenced during any new campaign build, any CRM field addition, or any argument about why GA4 and the CRM disagree on conversion counts.
Its absence shows up differently. Reports that don't match. A rebuild every time someone new touches the tracking. Consent settings applied inconsistently across pages. Nobody able to say with confidence what a given event actually captures.
The Australian context
Australian businesses juggling consent requirements under the Privacy Act need the tracking plan to double as a consent record. Which events fire before consent, which fire after, and which tool receives what data all need to be documented in one place if you want to defend your tracking setup to a regulator or a client. Businesses that skip this step often discover the gap only when a legal review or an ACCC-adjacent inquiry asks for it directly.
Where people get this wrong
Related terms
Common questions
Who should own a tracking plan?
An analytics lead or marketing operations person should own it, with input from developers and campaign marketers. Ownership by developers alone tends to produce a plan built around technical convenience rather than business questions.
How often should a tracking plan be updated?
Review it every quarter at minimum, and update it immediately whenever a new campaign, landing page or integration introduces new events. A plan reviewed once a year is usually already out of date by the time anyone opens it.
Is a tracking plan the same as a data layer?
No. The data layer is the technical structure that carries event data from your website to your tools. The tracking plan is the human-readable document describing what should be in that data layer and why. One is documentation, the other is implementation.
Do small businesses need a formal tracking plan?
Even a simple spreadsheet listing key events, their triggers and their destinations beats no plan at all. Small businesses skip this because it feels like overhead, then spend far more time later untangling conflicting numbers across their tools.
Debrief
Get the next one
No spam. No fluff. Just the next article, straight to your inbox.
Keep exploring
About New Rebellion
New Rebellion is a marketing intelligence consultancy. We build tools, score Australian businesses on how their marketing actually performs, and publish Debrief every day. This dictionary is part of how we work in the open.
How we think →