Tracking Plan

To define your tracking plan, start by creating your first event on the Events tab.

Note: Iteratively recommends the Object-Action Framework as a best practice for governing the structure of your events. Each event is associated with an Object in your application (e.g. File, Song, Story, or User) and an Action (e.g. Uploaded, Played, Completed, or Logged In).


Every event is defined by:

  • A name
  • A description
  • The sources it applies to (e.g. iOS, Android, Web App)
  • A set of properties

An event may have one or more properties associated with it. Properties further describe the particular event and the context it was invoked in. For example, a Song Played event may contain a songName property.


Every property is defined by:

  • A name
  • A description
  • Whether the property is required or optional
  • A type (e.g. String, Number)
  • A pattern (e.g. not empty, at least 15 characters, a specific regex)

A tracking plan is consumed by developers in the form of type-safe auto-generated code. The code exactly replicates the spec in the tracking plan and enforces all its rules and requirements.