Braze

chord x braze integration the chord’s customer data platform (cdp) integrates with braze to automatically forward ecommerce event data, such as purchases, user behavior, and identity updates, directly into braze this enables marketers to trigger personalized campaigns based on real time shopper actions without manual data pipelines this integration is maintained by chord about this integration chord's cdp captures and standardizes customer events from your ecommerce storefront by connecting chord to braze, marketers gain access to rich behavioral data (such as completed orders, product interactions, and customer identity updates) that can power personalized messaging at scale chord acts as the data layer that feeds braze with clean, structured ecommerce events so your campaigns reflect what customers are actually doing use cases post purchase messaging trigger order confirmation flows, upsell sequences, or review requests in braze when a customer completes an order in chord customer attribute sync keep braze user profiles updated with the latest customer data from chord to improve segmentation accuracy behavioral retargeting use chord event data to power win back or re engagement campaigns in braze for customers who haven't converted recently prerequisites before you start, you need the following prerequisite description a chord account a chord account is required to take advantage of this partnership a braze rest api key a braze rest api key with the appropriate permissions for cloud mode find this key under developer console in the braze dashboard for device mode find this key under settings > app settings > web > api key note these are two distinct api keys a braze rest endpoint chord sends data to the following braze endpoints /users/track and /users/identify the base url depends on your braze cluster and follows the format https //rest iad 0# braze com for example https //rest iad 01 braze com/users/track and https //rest iad 01 braze com/users/identify integrate chord with braze chord supports two connection modes cloud mode and device mode follow the steps for your preferred mode cloud mode step 1 navigate to destinations in the chord cdp log into the chord data platform navigate to the cdp click the add button next to destinations step 2 connect braze (cloud mode) as a destination select braze from the destination catalog enter a destination name and your braze api key (found under developer console in the braze dashboard) click create to connect device mode step 1 navigate to destinations in the chord cdp log into the chord data platform navigate to the cdp click the add button next to destinations step 2 connect braze (device mode) as a destination select braze (device mode) from the destination catalog enter a destination name and your braze api key (found under settings > app settings > web > api key — note this is distinct from your classic braze api key) click create to connect customize chord + braze step 1 select sdk version select the version of the braze sdk to use braze sdk versions 4 1 through 5 9 available step 2 select endpoint select the correct braze sdk endpoint https //www braze com/docs/user guide/administer/personal/sdk endpoints?redirected=1 for your application braze endpoints us 01 through us 09 & eu 01 through eu 02 are available step 3 select event config options enable order completed calls enable track calls enable identify calls send page events page event name allowed user supplied javascript automatically send in app messages eager sdk initialization consent requirements send null consent events use chord with braze once connected, chord maps its tracking events to braze as follows (device mode) chord event braze event order completed logpurchase all other track events logcustomevent identify getuser (updates user attributes) step 1 access event data in braze after setup, chord events will begin flowing into braze automatically navigate to your braze dashboard to verify event receipt under your user profiles or event stream step 2 build campaigns using chord data use the synced events and user attributes in braze to create segments, trigger canvas flows, or power message personalization based on real customer behavior from your chord storefront considerations avoid duplicate events before connecting braze through the chord cdp, confirm with all destination owners that any non chord cdp configured destinations sending to braze are disabled running external destinations alongside chord cdp destinations can result in duplicate events downstream not all chord tracking events are forwarded to braze only the events mapped in the chord tracking plan are relayed to configured destinations troubleshooting if you are unable to verify events properly being passed through to braze from chord, there are a few checks to be made to confirm that data is properly to and from chord into braze ensure that live tracking events are arriving in the chord cdp verify in the live events https //docs chord co/cdp live events tab of the chord cdp that there are live events being fired from all relevant sources without live events, there will be nothing to pass through to braze ensure that these live events are properly being passed to your configured braze destinations first, validate that your configured braze destinations are configured correctly with the appropriate api key, sdk braze version and endpoint second, validate that your configured braze destinations are properly connected to a corresponding source in the chord cdp once validated, confirm that events are firing and are successfully sending to the braze api endpoint ( live events > api destinations & function logs ) verify successful hits to the /users/track and /users/identify endpoints confirm events in your braze dashboard additional destination documentation can be found here braze (cloud mode) docid\ dyuyxhkxlbusglbjawkmt braze (device mode) docid\ e9n1bm5cev1xtc2rbyk8z