Microsoft CAPI

introduction the microsoft advertising conversions api (capi) destination allows you to send server side conversion events from chord directly to microsoft advertising this improves conversion accuracy, strengthens attribution, and ensures your microsoft ads campaigns are optimized using complete and reliable event data getting started when you enable the microsoft capi destination, chord sends purchase events custom conversion events revenue values user identifiers this happens server side, independent of browser limitations or ad blockers use this destination if you run paid media through microsoft advertising you want improved signal reliability you want to support microsoft’s automated bidding and optimization with high quality event data prerequisites before configuring this destination, ensure you have an active microsoft advertising account conversion goals configured in microsoft ads a microsoft ads developer token appropriate account permissions if you are unsure about these requirements, consult your microsoft advertising admin supported events the microsoft capi destination supports purchase lead custom conversion events additional event types may be configured depending on your microsoft ads setup required fields for purchase events, the following fields are required event name event time currency revenue value order id at least one user identifier (email, phone, or microsoft click id) connecting to the microsoft capi cdp destination log into the chord data platform navigate to the cdp click the "add" button next to destinations select microsoft capi from the destination catalog enter in the destination name and the tag id and access token click "create" to connect the tag id is your microsoft advertising uet tag id find in your microsoft advertising dashboard under conversion tracking the access token can be generated in your microsoft advertising account testing & validation after activation use microsoft ads event diagnostics to confirm receipt verify match rates confirm revenue and order counts align with expectations if discrepancies appear confirm msclkid capture is working ensure required fields are populated confirm credentials have not expired 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