Data Dictionary
Data & TrackingAlso: Tracking Dictionary · Event Dictionary · Analytics Dictionary
Quick definition
A data dictionary is a reference document that defines every event, property and parameter a business tracks across its marketing and analytics stack. It states what each field means, what values it can hold and where it comes from, so different tools and teams use consistent definitions.
How it varies across Australia
Most Australian businesses running Google Analytics 4 (GA4) or a customer data platform have some tracking documented, but few maintain it as new events get added. The gap between documented and actual tracking widens fastest in businesses running multiple tools without a shared data layer.
See data and tracking maturity across Australian industries →What it actually means
A data dictionary is the shared vocabulary underneath your analytics. Without one, 'purchase' might mean an order placed in one tool, an order paid in another, and a cart reaching checkout in a third. Nobody notices until the numbers disagree in a board meeting.
The dictionary sits above the technical plumbing. Your data layer holds the actual values passed to a tag manager. Your GA4 or CRM stores the events. The dictionary is the document that says what those events and parameters are supposed to mean, what values are valid, and who owns the definition.
It matters most wherever attribution, conversion event definitions or UTM parameter conventions get argued over. A well-maintained dictionary ends those arguments before they start, because the definition was agreed and written down before the dashboard existed.
Most businesses build one during a GA4 migration or a tracking audit, then let it rot. The dictionary is only useful if someone owns it as new events, campaigns and tools get added.
A data dictionary is boring until the day two teams report different revenue numbers from the same event, then it's the most important document in the building.
How it shows up
A data dictionary shows up as a shared spreadsheet or Confluence page listing every tracked event, its trigger conditions, its parameters and their allowed values. It shows up in tag manager naming conventions that actually match what's documented. It shows up in the absence of arguments during quarterly reporting about what 'lead' or 'signup' means. When it's missing, it shows up as every analyst building their own private definitions, and every migration project starting from scratch instead of from a known baseline.
The Australian context
Australian businesses juggling GA4, a CRM and a paid media stack often inherit tracking built by three different agencies over several years. A data dictionary is usually the first deliverable of a proper tracking audit here, because it's the fastest way to find out what's actually firing versus what someone assumes is firing.
Where people get this wrong
Related terms
Common questions
Who should own the data dictionary?
Whoever owns the analytics stack, usually a data or analytics lead rather than marketing. It needs one accountable owner or it drifts out of date within a quarter.
Is a data dictionary the same as a tracking plan?
They overlap heavily. A tracking plan usually specifies what to implement before it's built. A data dictionary documents what's actually live and what each field means once it's running.
Do small businesses need one?
If you're running one tool with a handful of events, probably not yet. Once you add a CRM, paid media platforms and a tag manager, the risk of conflicting definitions rises fast enough to justify one.
How often should it be updated?
Whenever a new event, campaign type or tool is added. Reviewing it quarterly alongside your Google Analytics 4 setup catches drift before it causes a reporting dispute.
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 →