Pinterest Conversions

the pinterest conversions api destination sends event data directly from chord cdp to pinterest's servers, bypassing the browser entirely unlike the pinterest tag (device mode) , server side events are immune to ad blockers and browser tracking restrictions, providing more reliable signal for campaign measurement, audience building, and automated bidding optimization use this destination alongside the pinterest tag destination for maximum data coverage pinterest deduplicates events using the event id field getting started this is a cloud mode destination you will need ad account id — your pinterest ads account id, found in your pinterest ads dashboard url or under ads > account settings conversion token — a conversion access token generated in pinterest ads > conversions see pinterest's documentation https //developers pinterest com/docs/conversions/conversions/ for instructions on creating a server side access token app name — a name identifying your application or integration (e g "my storefront" ) used as the partner name in the event payload connecting to the pinterest conversions api cdp destination warning 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 data platform navigate to the cdp click the "add" button next to destinations select pinterest conversions api from the destination catalog enter the destination name, ad account id , conversion token , and app name click "create" to connect events event mapping chord event pinterest event page pagevisit order completed checkout checkout started initiatecheckout product added addtocart product viewed viewcontent products searched search product added to wishlist addtowishlist (other track events) chord event name passed as is page, track, and screen events are forwarded identify events are ignored user data (all events) all personally identifiable information (pii) is sent to pinterest as raw values; pinterest's api hashes them server side according to its data processing requirements fields that cannot be resolved are omitted pinterest field chord source (priority order) notes email properties email > context traits email array; omitted if not present phone properties phone > context traits phone array; omitted if not present first name properties first name > context traits firstname array; omitted if not present last name properties last name > context traits lastname array; omitted if not present city context traits address city > properties address city array; omitted if not present state context traits address state > properties address state array; omitted if not present zip context traits address postalcode > properties address postalcode array; omitted if not present country context traits address country > properties address country array; omitted if not present external id userid > anonymousid array; omitted if neither is present client ip address context ip not hashed client user agent context useragent defaults to "mozilla/5 0" if not present click id epik query parameter from context page url pinterest click id partner id properties partner id > context campaign name custom data (track events) track events include a custom data block with the following structured schema fields additionally, any properties destination mappings configured in hub that target non schema fields are forwarded as custom properties alongside the structured fields pinterest field chord source (priority order) notes value properties value > properties price > properties revenue > sum of price × quantity across products string; omitted if not resolvable currency properties currency > properties meta i18n currency defaults to "usd" order id properties order id > properties cart id content ids product ids from properties products\[] or properties product id / properties sku falls back to page title for page events contents array of { id, item price, quantity, item name, item category, item brand } per product omitted if no products num items properties quantity > sum of quantities across properties products\[] search string properties query > properties search term relevant for products searched custom property forwarding configure destination mappings in hub with properties destination paths to forward additional event properties into custom data only explicitly configured non schema fields are forwarded — nothing flows through automatically how to configure open the destination's mappings tab in hub add a mapping with source path properties loyalty tier and destination path properties loyalty tier on the next event, custom data loyalty tier will appear in the payload sent to pinterest what is excluded schema fields already handled by the destination transform (e g currency , value , order id , content ids , contents ) — these flow through the structured transform pii fields ( email , phone , first name , last name ) — these are handled via user data when a custom mapping targets a schema field (e g properties value → properties value ), the customer configured value overrides the destination's computed default this allows schema fields to be sourced from a different event property — for example, mapping properties total → properties value to use your order total as the conversion value testing and validation after connecting the destination trigger events from your storefront or use the live events tab in the chord cdp to confirm events are flowing in pinterest ads manager, navigate to ads > conversions and open your conversion tag to verify events are received confirm revenue values and order counts align with your expectations if you are running both the conversions api and the pinterest tag, ensure event id values match across both to prevent duplicate counting chord cdp handles this automatically by using messageid as the event id for both destinations updated 27 may 2026