Tracking Plans

Detailed technical description of the Tracking Plans feature to plan and monitor your event data.

Tracking Plans let you proactively monitor and act on non-compliant event data coming into your RudderStack sources based on predefined plans. This can help you prevent or de-risk situations where missing or improperly configured event data can break your downstream destinations.

The Tracking Plans currently support only the track events sent to the warehouse destinations.

Tracking Plan features

With the help of a Tracking Plan, you can:

• Define specific event names and properties for each of your track, group, and identify calls.

• Specify whether a property/attribute is required and assign a particular data type.

• Have better control of your data streaming by supporting a versioning system.

• Use the Data Governance API to evaluate your inbound events and metadata, and compare them with your plans.

Refer to the RudderStack Tracking Plans blog post for more information on Tracking Plans and how to use them effectively.

Quickstart

To start using the Tracking Plans, follow these steps:

1. Generate a personal access token in the RudderStack dashboard.

2. Make a copy of the RudderStack Tracking Plan Spreadsheet to create or update your tracking plans.

3. Connect your Tracking Plan to a source. For more information, refer to the Tracking Plan Spreadsheet documentation.

4. (Optional) Use RudderTyper for autocomplete and linting.

Tracking Plan API

The Tracking Plan API lets you build applications or scripts on top of RudderStack's Tracking Plan capabilities. This includes a simple CI/CD pipeline, integrations with other Tracking Plan systems such as Amplitude, Mixpanel, Avo, and many other creative use-cases.

Using the Tracking Plan API

To use the Tracking Plan API, follow these steps:

1. Generate a personal access token in the RudderStack dashboard.

2. Refer to the Tracking API documentation in Postman.

You can also refer to the RudderStack Data Governance API that gives you insights into your current schemas and data volumes going through RudderStack.

We also have the Data Governance API, which is a descriptive API that tells you your current schemas and data volumes going through Rudderstack.

Useful links

The Tracking Plans documentation is divided into the following sections:

FAQ

Which calls are supported for the RudderStack Tracking Plans?

The Tracking Plans feature currently supports only track events.

Are the Tracking Plans supported for all the destinations?

No - the Tracking Plans feature is currently supported only for the warehouse destinations.

Contact us

For queries on any of the sections covered in this guide, you can contact us or get in touch with your Account Manager.