Facebook Conversions API

introduction the facebook conversions api (capi) is a tool that lets you send website and customer event data—like purchases, sign ups, or page views—directly from your server to facebook unlike the facebook pixel, which relies on browser tracking, capi runs server side, making it more reliable in environments where browser data might be blocked (like with ad blockers or privacy settings) capi is often used alongside the facebook pixel to create a more complete, resilient view of customer behavior getting started you will need the https //www facebook com/ads/manager/pixel/facebook pixel/ and https //developers facebook com/docs/facebook login/web/accesstokens/ to connect the facebook conversions api destination best practices for setup use capi alongside the meta pixel enable automatic advanced matching send rich user data (hashed) what to expect after capi is configured higher match rates extended cookie lifespan how to monitor & diagnose issues use meta events manager “diagnostics” validate event receipts through “test events” tab leverage facebook developer console ensure deduplication is correctly configured connecting to the facebook conversions api cdp destination log into the chord data platform navigate to the cdp click the "add" button next to destinations select facebook conversions api from the destination catalog enter in the destination name and the facebook pixel id and facebook access token click "create" to connect implementation checklist task why it matters enable both capi & pixel access redundancy and better coverage activate advanced matching increase match quality without compromising privacy test events via diagnostics + test events tab ensure proper delivery and de duplication monitor developer console metrics proactively identify api errors or auth issues match event ids across pixel and server events prevent data duplication or mismatches 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 facebook com/docs/meta pixel/reference#standard events are chord tracking event destination event page pageview checkout started initiatecheckout order completed purchase product added addtocart product viewed viewcontent subscription created subscribe custom/generic events event name to be passed directly 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