About Event Tracking

chord automatically sends customer events to segment's tracking api from your website front end and the chord oms these events flow through segment to a chord data warehouse, where the data is modeled and turned into actionable insights https //chord co/segments/insights segment structures data flow as "sources" and "destinations " sources are anything that sends events to segment, like a website or an app destinations are tools or apps that will receive the data flowing from a source chord automatically creates several sources and destinations within segment, but you can also add your sources and destinations destinations are an easy way to enable third party integrations, like advertising and marketing tools read more about this concept in segment's documentation https //segment com/docs/connections/ how does chord use segment? chord provisions two sources in your segment account the chord oms (called the "back end source") and your website (the "front end source") you will have a set of sources per environment for example, if you have a staging environment and a production environment, you'll see four sources "my company back end (production)" "my company front end (production)" "my company back end (staging)" "my company front end (staging)" back end source the chord oms sends events to the back end source immediately using the segment write key environment variable in your oms store settings verify events are tracked by selecting the source within segment, and then selecting the debugger tab you'll see a live feed of events coming from the source the back end source sends events related to orders and customer accounts, like "order completed" and "subscription payment failed " we recommend relying on events from the back end source whenever possible when setting up third party integrations because ad blockers or other factors can impact front end events what is the tracking plan? docid\ rvqtp3y8q8kizuxb5lh7r includes a list of the events sent by the back end source if you're using chord with shopify, you'll see one or more "shopify webhook" sources instead of the chord oms back end source these work similarly shopify sends mission critical events like "order completed" to segment via these sources the shopify tracking plan docid\ ekaz3fd9et0e3gdmjllh6 reference includes a list of events sent by webhook sources front end source the chord javascript sdk sends events to the front end source from your website to set this up, you'll need to load segment's analytics js library on your website and do some configuration see adding tracking docid\ eqgukbpr49vy82sql9ikw once your website is configured, the chord sdk automatically sends events to segment related to customer activity, like "product added" and "promo code applied " the chord sdk also offers functions you can use to instrument your website to track ui related events, like "product clicked " chord's website starter kits are fully instrumented with ui tracking, so you can use them to get started easily or as examples read more about instrumenting your website adding tracking docid\ eqgukbpr49vy82sql9ikw what is the tracking plan? docid\ rvqtp3y8q8kizuxb5lh7r includes a complete list of the events sent by the front end source data warehouse destination chord also provisions a data warehouse destination in your segment account it's connected to front end and back end sources this gives the chord data pipeline access to all events coming into segment from chord sources how should you use segment? chord uses tracking data from segment to provide actionable insights for your business you can also use segment directly to integrate your website with other apps and services add additional sources and destinations when you need them segment has a large catalog of integrations that are available as sources and destinations chord's events follow segment's e commerce spec https //segment com/docs/connections/spec/ecommerce/v2/ , which many destinations understand so that they can be enabled with minimal configuration