---
title: "Tracking plan: definition and meaning · Countly"
description: "The agreed list of events and properties, with names and owners. The document that keeps analytics usable in year three."
url: https://countly.com/glossary/tracking-plan
last_modified: 2026-11-11
---

[Glossary](https://countly.com/glossary) · Data

# Tracking plan

The agreed list of events and properties, with names and owners. The document that keeps analytics usable in year three.

Boring, unglamorous and the difference between analytics that still works after three years and analytics that has to be rebuilt. It is a shared document, not a config file, because its purpose is agreement.

[In Countly See how this works in the product](https://countly.com/platform/data-management)

More in Data

- [Autocapture Recording interactions automatically instead of instrumenting each one. Quick to start with, expensive to govern once the schema drifts.](https://countly.com/glossary/autocapture)
- [Customer Data Platform (CDP) A system that unifies customer data from several sources into one profile. Countly builds those profiles in the same store the analytics runs on.](https://countly.com/glossary/customer-data-platform-cdp)
- [Data governance The rules for what is collected, how it is named, who may see it and how long it is kept, decided before the data becomes a report.](https://countly.com/glossary/data-governance)
- [Data pipeline The path an event takes from the SDK to the store: validation, transformation, consent checks and masking, in that order.](https://countly.com/glossary/data-pipeline)
- [Event One recorded action with a timestamp, a user and a set of properties. The unit everything else on this page is built from.](https://countly.com/glossary/event)
- [Event properties The attributes carried by an event (plan, screen, version, value) that make it possible to break a metric down later.](https://countly.com/glossary/event-properties)
[All 91 terms](https://countly.com/glossary)
