The Chord Tracking Plan

the chord tracking plan specifies events that chord sends to segment, including events coming from the chord oms source and the website front end source via chord's sdks please review the procotols tracking plan in your segment account to explore the event properties and types events name description recommended segment source account created a new account is created ambassador signup created visitor signs up for information on the ambassador program cart viewed a user viewed their shopping cart front end checkout abandoned the user abandoned the checkout process back end checkout completed fired when a customer visits the checkout#success and is mainly used for conversion campaigns front end checkout started user initiated the order process (a transaction is created) back end, front end checkout step completed user completed a checkout step checkout step viewed user viewed a checkout step collection clicked user clicked on a collection front end coupon applied coupon was applied on a user’s shopping cart or order front end coupon denied coupon was denied from a user’s shopping cart or order front end coupon entered user entered a coupon on a shopping cart or order front end coupon removed user removed a coupon from a cart or order front end email bounced this event should be sent when an email tool receives notice from an email server that an email is undeliverable email captured email entered in a form on the website front end email delivered this event should be fired when the receiving mail server confirms receipt of an email email link clicked this event should be fired when the recipient clicks on a link in the email’s body email marked as spam this event should be fired when a recipient marks an email as spam email opened this event should be fired when the recipient opens the email email queued these events are very similar to the non email business process events except they contain a lot more context about each business event that has taken place within the oms the main purpose of these events is to use the information to build out transactional emails using a third party service back end invite sent customer invites another customer (referral) item restocked item back in stock back end login started registrant starts to sign in front end order cancelled fired when an order is cancelled back end order completed user completed the order back end, front end order cross sell completed fired when a user has purchased additional items during the cross sell flow post checkout page viewed payment info entered user added payment information product added user added a product to their shopping cart front end product clicked user clicked on a product front end product list filtered user filtered a product list or category front end product list viewed user viewed a product list or category front end product removed user removed a product from their shopping cart front end product reviewed user reviewed a product product viewed user viewed a product details front end promotion clicked user clicked on promotion promotion viewed user viewed promotion shipment delivered fired when a shipment has been delivered back end shipment shipped user shipment is shipped back end shipment updated movement or activity registered for a given shipment signed in registrant signs in front end signed out registrant signs out front end signed up visitor signs up for an account, becoming a registrant stock request created a new stock request has been created front end subscription activated a canceled subscription was activated/reactivated back end subscription address updated address associated with subscription is updated subscription canceled a subscription was canceled, either by the customer or by oms because the subscription is failing and exceeded the maximum number of retry attempts back end subscription auto renewed subscription passed the most recent order date, but has not passed the end date fired when a new subscription installment is created and the customer is charged back end subscription cancelled subscription cancelled by the user, or failure to auto renew front end subscription created subscription created back end subscription expired subscription passed the end date, and new orders will no longer be created at the interval specified back end subscription failed an installment generated by the subscription failed to complete back end subscription installment insufficient stock a subscription installment failed because a variant is out of stock subscription order skipped the upcoming order in a subscription is skipped, making the next order front end subscription paused the subscription is paused, and the processing date is indicated on the `actionable date` property a `null` date indi front end subscription payment failed fired when the subscription installment payment fails due to an invalid credit card back end subscription reminder sent when the reminder mail and the last chance reminder mail are sent, this new event is triggered back end subscription resumed the paused subscription is resumed, and the processing date is indicated on the `actionable date` property front end unsubscribed this event should be fired when the recipient unsubscribes from the email the unsubscription can either happen for a pa user created fired when a new user account has been created back end user updated fired when an existing user’s information has been updated back end variant clicked the user clicked on a product variation front end