Retention.com

introduction retention com helps brands capture, enrich, and activate anonymous and first party customer data—especially via identity resolution and re engagement tools like cart abandonment campaigns and winback automation connecting retention com as a cdp destination enables chord to pass customer and behavioral events directly into retention com for enrichment and activation getting started before connecting retention com as a cdp destination retention com account – ensure your team has an active retention com account with api access api credentials – retrieve your retention com api key or token from your dashboard typically found under settings → api access in the retention com portal connecting to the retention com cdp destination 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 log in to the chord data platform go to cdp → destinations click add and select retention com from the list fill in the configuration form destination name choose a name (e g , “retention com – prod”) api key / token paste in your retention com api credentials click create to activate the connection post‑connection considerations event deduplication avoid dual tracking events to retention com outside of chord if using direct scripts or tag managers, consider removing them to reduce duplication custom field mapping in the chord cdp destination settings, you can map custom chord fields to retention com expected parameters (e g , product category or brand) testing use the destination events view in chord to confirm successful delivery and payload shape verification & troubleshooting check cdp → incoming events to verify event capture within chord go to cdp → destination events and filter by retention com to inspect delivery status troubleshooting checklist validate api token permissions ensure email or phone number is present on all identify events confirm consent preferences are being passed correctly use retention com’s logs or support to troubleshoot missing data events once connected, chord will send key customer events in real time to retention com these events power lifecycle automations, identity resolution, and behavioral segmentation only supported event types will be sent; unsupported or redundant events may be dropped automatically event mapping chord event retention sdk call page geq page() identify geq suppress(email) email captured geq suppress(email) order completed geq trackorder(orderdata) product added geq addtocart(productdata) product viewed geq event("viewed product reclaim", productdata) event mapping notes identity matching retention com uses email and other identifiers to power its identity resolution and anonymous visitor matching chord ensures these values are included when available behavioral triggers events like product added , cart viewed , and checkout started are used to power retargeting workflows such as abandoned cart sequences custom metadata product level metadata (sku, category, price, etc ) is passed where possible to enable more precise targeting consent signals ensure you are passing opt in status where relevant retention com respects user consent preferences when provided page fires a retention com page view call retention sdk call geq page() no additional attributes are sent with page events identify suppresses retention com collection for known users when a user is identified with an email, retention com stops anonymous visitor collection for that email retention sdk call geq suppress(email) parameter chord source (in priority order) notes email properties email / properties emailaddress > context traits email > traits email event is skipped if no email is found track email captured suppresses retention com collection when an email is captured (same behavior as identify) retention sdk call geq suppress(email) parameter chord source (in priority order) notes email properties email > traits email event is skipped if no email is found order completed sends an order tracking call to retention com retention sdk call geq trackorder(orderdata) retention attribute chord source (in priority order) notes order number properties cart id / properties cartid / properties order id / properties orderid / properties id > "" order amount properties total > properties value > 0 converted to string order email properties email / properties emailaddress > context traits email > traits email > "" product added sends an add to cart event uses the first product from properties products , or falls back to extracting product data directly from properties retention sdk call geq addtocart(productdata) retention attribute chord source (in priority order) notes name properties products\[0] name > properties name > "" price properties products\[0] price > properties price > "" converted to string productid properties products\[0] product id / properties products\[0] productid > properties products\[0] sku > properties products\[0] id > properties product id / properties sku / properties id > "" categories properties products\[0] category > properties category > "" imageurl properties products\[0] image url > properties image url > "" url properties products\[0] url > properties url > "" brand properties products\[0] brand > properties brand > "" product viewed sends a product viewed event using retention com's reclaim feature retention sdk call geq event("viewed product reclaim", productdata) same attributes as product added above initialization the plugin manages sdk loading state ( fresh → loading → loaded / failed ) to prevent duplicate script loads concurrent events during loading are queued via a shared initialization promise if the script fails to load, subsequent events are silently dropped csp requirements if your site uses a content security policy, allow the following domains directive domain script src https //s retention com connect src https //s retention com