What is the Tracking Plan?

the chord tracking plan is a specification that defines the events and event properties that chord sends to segment the tracking plan is a comprehensive list of all events chord sends to segment, including events coming from the chord oms source and the website front end source via chord's sdks find an overview of chord's tracking plan events the chord tracking plan docid\ w 5n055z3keefjj759v26 chord imports the tracking plan into segment as a protocols tracking plan , so you can use segment's built in features like violations reporting https //segment com/docs/protocols/validate/review violations/ , which lets you see if events comply with the protocols tracking plan we're using the words "tracking plan" to mean two different things, so let's define chord tracking plan an event spec describing all tracking events and properties that chord will send to segment protocols tracking plan a copy of the chord tracking plan imported into segment what's in the tracking plan? chord sends events to track the full customer journey on your site, as they add products to their cart, filter lists of products, sign into their customer account, and check out chord also sends events when changes take place in the oms, as packages are shipped, customer subscriptions are renewed, and products come back in stock all these events and event properties are described in the chord tracking plan here's the chord tracking plan docid\ w 5n055z3keefjj759v26 of the events in the tracking plan chord's tracking plan incorporates segment's ecommerce spec https //segment com/docs/connections/spec/ecommerce/v2/ , although it has additional events and event properties this is important because some segment third party destinations expect events to follow segment's ecommerce spec for a detailed view of all the events and event properties in the chord tracking plan, you can see the copy that was imported into segment as a protocols tracking plan navigate to the protocols section in segment from here, you can select the tracking plan and explore a detailed view of every event and event property, including the data type of each property (e g "string" or "number") occasionally chord will release a new feature and add new events or event properties to the chord tracking plan chord will notify you that your tracking plan will be upgraded when this happens this means chord will change the protocols tracking plan in your segment account protocols tracking plans have a changelog, so you can always see what has changed using the protocols tracking plan when you sign up, chord will import the chord tracking plan into your segment account as a protocols tracking plan chord will also connect the protocols tracking plan to your chord storefront event tracking docid\ orezputhdayj10b7fsoqn you can use it to monitor your segment events https //segment com/docs/protocols/validate/review violations/ for possible issues impacting your data reporting or third party integrations you can also use it to generate your analytics library if you want to send events directly to segment https //segment com/docs/protocols/apis and extensions/typewriter/ adding the protocols tracking plan to segment and connecting it to sources does not impact the events chord sends to segment (unless you've intentionally configured your segment account to block events not in the protocols tracking plan, which we don't recommend we'll go into this in the next section ) chord sends events to segment that comply with the chord tracking plan, whether or not a protocols tracking plan is provisioned in your segment account deleting an event from the protocols tracking plan does not stop chord from continuing to send the event or your connected destinations from receiving the event validating events when the protocols tracking plan is connected to sources, you can monitor for violations https //segment com/docs/protocols/validate/review violations/ , which are incoming events that don't match the protocols tracking plan it's up to you if you want to monitor this chord monitors for any event violations that impact data reporting however, it's a good starting point for troubleshooting integrations for example, if you see an error with an integration that indicates an event property is missing, you might check for violations for that event the violations could give you more information about how often the property is missing when it started occurring, and its expected value to view violations, navigate to a segment source and select schema > view violations you'll see a list of events and their violations if you see violations for events sent by chord, your protocols tracking plan could be out of date with chord's tracking plan reach out to chord to troubleshoot you can forward violations to a segment source if you want to set up custom monitoring you can also choose to block events that violate the protocols tracking plan, but we advise against this this can result in permanently lost data if you have any questions or need help, please reach out to us at help\@chord co