Chord CDP
...
CDP Destination Catalog
Pinterest Conversions
4 min
introduction the pinterest conversions api is a server side tool that lets advertisers send conversion events—like purchases, sign ups, or page views—directly from their servers to pinterest it’s an alternative or complement to the pinterest tag (which operates in the browser) and is designed to improve data reliability, especially when browser tracking is limited by ad blockers or privacy settings getting started you will need the app name, ad account id, and conversion token to connect this destination app name the name of the site from which the event originated ad account id this is a unique identifier of an ad account this can be found in the pinterest ui by following https //developers pinterest com/docs/conversions/conversions/#find%20your%20%2cad account id conversion token this is the conversion token for your pinterest account this can be found in the pinterest ui by following https //developers pinterest com/docs/conversions/conversions/#get%20the%20conversion%20token connecting to the pinterest conversions api cdp destination log into the chord data platform navigate to the cdp click the "add" button next to destinations select pinterest conversions from the destination catalog enter in the destination name and the app name, ad account id, and conversion token click "create" to connect chord events relevant for destination not all chord tracking events are used downstream in your configured destinations the most relevant and important events in the chord tracking plan are mapped within the cdp destination, relayed and then ingested in the destination the chord tracking plan events used by the https //developers pinterest com/docs/track conversions/track conversions in the api/ destination are chord tracking event destination event checkout started checkout order completed checkout page page visit payment info entered add to cart product added add to cart product added to wishlist add to cart product viewed view category products searched search signed up signup 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