Klaviyo

introduction klaviyo is a marketing automation platform built specifically for e commerce brands, designed to help them deliver personalized customer experiences through email and sms it empowers marketers to build targeted campaigns, automate messaging flows, and measure performance using rich customer data by integrating directly with e commerce platforms and pulling in behavioral and transactional data, klaviyo enables brands to turn insights into action—driving higher engagement, loyalty, and revenue getting started before connecting your klaviyo account as a cdp destination, a custom private api key must be generated with a specific set of configured scopes once you have navigated to create a new private api key ( settings > account > api keys ), the scopes to configure are events api scope must be set to read/write access all other api scopes can be set to read access once configured, click create in the top right corner the api key permissions for you newly created key will appear as follows connecting to the klaviyo cdp destination log into the chord data platform navigate to the cdp click the "add" button next to destinations select klaviyo from the destination catalog enter in the destination name and the klaviyo api key click "create" to connect chord events relevant for destination while typically not all chord tracking events are used downstream in your configured destinations, klaviyo is an exception as a sms and email marketing platform, chord passes through all availalbe/possible track events that are passed through any configured sources upstream all track events are sent to klaviyo's https //developers klaviyo com/en/reference/events api overview with their original name the use cases supported by klaviyo's custom events api include creating custom events that can be used to trigger flows (e g , a reset password event that triggers an email with a reset password url) getting klaviyo events that can be used for data analysis (e g , retrieving engagement events tracked by native klaviyo metrics, such as opened email and clicked sms) getting a specific profile’s events to power an activity feed getting related profile and/or metric data for a given event chord will only send events through to klaviyo if either email or phone is present in the event payload without this identifying attributes, events are skipped note attentive's custom events api is specifically designed to ingest user action events considering this, page view events are not passed through chord tracking event destination event/action all track events event name passed as is identify upsert profile (to create or update user profile) before connecting destinations in the chord cdp, please verify with all destination owners that all non chord cdp configured destinations are disabled running external destinations alongside configured chord cdp destinations can result in duplicate events downstream