Get started with Chord CDP

overview getting started with chord cdp is seamless in the sections below, we'll guide you through the following understanding the cdp onboarding process connecting a destination and viewing event streams chord cdp onboarding all new chord customers after january 2025 will be able to leverage chord cdp upon signing up for the chord platform no additional work beyond the initial implementation period will be required from your team legacy chord customers prior to january 2025 who are eligible to use chord cdp will be migrated to the cdp by our implementation team the chord team will work with your development team to replace the existing cdp snippet with a chord cdp snippet and work with you to understand any impacts to how you are currently handling consent management cdp overview chord brands will be able to manage their cdp sources and destinations through the cdp page on the chord data and analytics platform with chord cdp, you will be able to take the following actions view all connected sources and destinations that were set up during initial implementation view event streams for incoming and destination events for event monitoring add additional destinations using the chord destination catalog ( admin users only ) edit or delete connected destinations ( admin users only ) connecting a destination the chord cdp https //docs chord co/cdp destination catalog has a number of key destinations that you can connect to, including (but not limited to) attentive braze facebook conversions api ga4 ga4 (device mode) klaviyo note we will continually add additional destinations to the catalog is your desired destination not in our cdp catalog? send us a note and we’ll consider adding it to our catalog! see more information about cdp destinations https //docs chord co/cdp destinations to add destinations, admin level users can take the following steps to set up destinations via our https //docs chord co/cdp destination catalog on the cdp overview page, click the “ add” button on the right you will be taken to the destinations catalog scroll to view the destination options in the catalog and select the destination you’d like to connect complete the destination connection steps as provided on the screen click “ create ” to complete your destination set up event stream monitoring you can easily view all incoming and destination events through our cdp incoming events to view all incoming events (tracked events from both your storefront and checkout), click on the incoming events tab the following filters can be applied to view specific events sites if you have multiple source connectors, you can select to view events from a specific source connector status can see all events or filter and see events with errors start and end date can view specific incoming events over a certain timeframe by using these filters destination events to view all destination events (events that are getting sent to specific connected destinations), click on the destination events tab the following filters can be applied to view specific events connection select a specific destination event stream you’d like to view status can see all events or filter and see events with errors mode can filter by batch or stream options start and end date can view specific destination events over a certain timeframe by using these filters troubleshooting and faqs question will there be significant differences in tracked events with chord cdp? there will be no differences in tracked events the events api will remain exactly the same question will there be any differences in user identification or how chord unifies customer profiles given chord cdp? there will be no differences in user identification or user stitching processes on the chord side, as this is all handled by our data modeling layer which is unchanged