Defining the data to collect with Tracking Plans

As described in Tracking Plans Introduction, a tracking plan is a logical grouping of the data you collect as an organisation by domain, with an explicit owner.

With tracking plans, you can:

• Set clear ownership for the data being created
• Make tracking implementation easier
• Deliver better governance around your data
• More easily communicate what the data means and how to use it
• Collaborate more effectively with the various teams involved in delivering value from your data
• Drive a self-serve culture around data across your organization
• See event volume metrics helping to monitor data collection over time.

Elements of a Tracking Plan

Tracking plan

• Name; a descriptive and unique name for the tracking plan
• Description; a description of the data that the tracking plan captures
• Owner; the individual responsible for the tracking plan
• Domain; the team or business domain that owns the tracking plan
• Source Application; the source application/s the Tracking Plan is implemented in
• Event specifications
  • Name; a descriptive name for the event
  • Description; a description to help people understand what action the event is capturing
  • Source Applications; the source application(s) inherited from the tracking plan containing the Application ID(s) that will be sent with this event
  • Triggers; specific instructions on where the event gets triggered (e.g. when a user clicks the "Add to basket" button)
  • Event data structure; the event data structure that this event will validate against as it is processed by your pipeline
  • Entities; the entities that should be attached to this event (e.g. user, product)
  • Properties; any specific rules for each property of the event