Pinterest Tag

pinterest tag is pinterest's conversion tracking pixel it loads the pinterest tag javascript sdk in the browser and forwards ecommerce events to pinterest for campaign measurement, audience building, and automated bidding optimization there is no server side component getting started this is a device mode destination the pinterest tag sdk is loaded automatically — no manual script installation is required you will need tag id — your pinterest tag id, found in your pinterest ads account under ads > conversions optionally use enhanced match loading — when enabled, passes the user's email to pinterest during initialization for enhanced matching defaults to false connecting to the pinterest tag 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 tag from the destination catalog enter the destination name and your tag id optionally enable use enhanced match loading click "create" to connect events all pinterest tag events include an event id parameter set to the chord messageid for deduplication event mapping page events pinterest sdk call pintrk("track", "pagevisit", pageprops) identify events sets user identity for pinterest enhanced matching pinterest sdk call pintrk("set", { np, em }) product list viewed pinterest sdk call pintrk("track", "viewcategory", categorydata) products searched / products list filtered both map to the search event pinterest sdk call pintrk("track", "search", searchdata) product added pinterest sdk call pintrk("track", "addtocart", cartdata) order completed same attributes as product added above pinterest sdk call pintrk("track", "checkout", checkoutdata) other track events any unrecognized track event is forwarded using the raw chord event name pinterest sdk call pintrk("track", eventname, properties) line items when products are present, each product is mapped to a pinterest line item custom property forwarding configure destination mappings in hub with properties destination paths to forward additional event properties into pintrk("track", ) payloads 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, loyalty tier will appear in the event properties payload sent to pinterest what is excluded schema fields already handled by the destination transform (e g currency , value , order id , line items ) — these flow through the structured transform pii fields ( email ) — handled separately during initialization via enhanced match loading 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 initialization the plugin loads https //s pinimg com/ct/core js , then calls pintrk("load", tagid) (optionally with { em email } if use enhanced match loading is enabled and an email is available on the triggering event), followed by pintrk("page") to fire the initial page view the plugin manages sdk loading state ( fresh → loading → loaded / failed ) to prevent duplicate script loads 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 updated 27 may 2026