Chord CDP
...
CDP Destination Catalog
ShopMy
9 min
l introduction shopmy helps brands amplify creator‑driven commerce experiences by tracking performance across affiliate and creator channels the shopmy destination enables you to send customer behavior and conversion events from your store (via chord) to the shopmy platform to power creator‑led performance marketing, audience insights, and analytics what the shopmy destination does by connecting shopmy as a destination in the chord cdp, the following happens chord sends tracked events from your store (e g , page views, add to cart, purchase, etc ) to shopmy shopmy uses these events for enhanced conversion tracking and attribution tied to creator referrals and internal analytics events can feed audience building and attribution reports in the shopmy platform you can think of this as a bridge chord handles customer event capture + transformation, and shopmy processes those events for creator performance and conversion insights getting started before you begin confirm you have an active shopmy account with access to the shopmy dashboard you’ll need your shopmy pixel id (or relevant shopmy destination identifier) — this is obtained from within your shopmy account make sure your store is instrumented with chord event tracking (web + server events) connecting to the shopmy 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 into the chord go to cdp > destinations click add destination search for shopmy and select it from the catalog enter a recognizable destination name (e g , “shopmy – prod”) paste your shopmy pixel id in the prompt field click create to activate the destination events page loads the shopmy click tracking script no data is sent — the script manages affiliate attribution cookies ( sms click id ) autonomously track order completed sends an order confirmation to the shopmy api the event is skipped if no sms click id cookie is present (i e , the visitor was not referred by a shopmy affiliate) api call post https //api shopmy us/api/order confirmation shopmy attribute chord source (in priority order) notes orderamount order subtotal > order revenue > order total > 0 orderid order orderid > order id > properties order id clickid sms click id cookie required; event is skipped if not present currency order currency > "usd" (default) is returning customer properties is returning customer > false (default) page url window\ location href current page url at time of event code properties coupon > null coupon/discount code the api request has a 5 second timeout if the request times out or fails, a warning is logged and the event is dropped all other track events are silently skipped page and identify events do not send data to shopmy (they only trigger script loading) initialization the plugin loads https //static shopmy us/affiliates/sms aff clicktrack js on the first event of any type this script handles affiliate click attribution by reading url parameters and setting the sms click id cookie 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 //static shopmy us connect src https //api shopmy us