Attentive

introduction attentive is a leading sms first marketing platform designed for e commerce brands to engage with their customers through personalized, real time messaging it helps brands grow their subscriber lists, deliver targeted messages, and drive revenue through thoughtful automation and customer segmentation getting started when creating/using a custom key for the attentive destination, the key must be app specific, so a new app within the your brand's attentive account will need to be created first to do so, follow the guidelines here log into your brand's attentive account and click on the marketplace link on the left hand side of the navigation pane on the app marketplace page, click on the " create app " button on the top right corner set and save the following required permissions on the app permissions page customer attributes write custom events write ecommmerce write privacy request read product catalog no access subscribers write copy and save the klaviyo api key from the new app workspace in a secure place to add to our cdp destination for klaviyo connecting to the attentive cdp destination log into the chord data platform navigate to the cdp click the "add" button next to destinations select attentive from the destination catalog enter in the destination name and the attentive 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, attentive is a notable exception as a sms an 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 attentive's https //docs attentive com/openapi/reference/tag/custom events/ with their original name track events are only sent if at least one identifying attribute is present in the event payload phone email userid anonymousid note attentive's custom events api is specifically designed to ingest user action events considering this, page view and identify events are not passed through 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