Facebook (Meta) CAPI

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 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 facebook conversions api from the destination catalog enter in the destination name and the facebook pixel id and facebook access token optionally configure action source — defaults to website change to app , email , etc if events originate from non web sources events filter — restrict which events are forwarded (empty sends all) product content id field — which product field to use as the content id ( sku , product id , or variant id ) defaults to sku this value will be used in the contents \[] id field phone field name — the trait field containing phone numbers (leave empty to skip phone matching) 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 events event mapping chord event facebook event page pageview checkout started initiatecheckout order completed purchase product added addtocart product viewed viewcontent products searched search product clicked viewcontent subscription created subscribe (other track events) original event name passed through page, track, and screen events are forwarded identify events are ignored common event fields these fields are included on every event sent to meta facebook field chord source (priority order) notes event name (mapped from event — see table above) event time timestamp converted to unix seconds event id messageid used for deduplication with the browser pixel action source configured action source defaults to website event source url context page url user data all personally identifiable information (pii) is sha256 hashed before being sent to meta, in compliance with meta's data processing requirements facebook field chord source (priority order) notes em (email) properties email > context traits email lowercased and sha256 hashed ph (phone) properties {phonefieldname} > context traits {phonefieldname} non digits removed, leading zeros stripped, sha256 hashed only sent if phone field name is configured fn (first name) properties first name > first word of context traits name sha256 hashed ln (last name) properties last name > second word of context traits name sha256 hashed zp (zip code) properties shipping zipcode > context traits address postalcode sha256 hashed ct (city) properties shipping city > context traits address shipping city sha256 hashed; also enriched from server side geo lookup country context traits address country sha256 hashed; also enriched from geo lookup st (state) (geo lookup) sha256 hashed region code from ip geolocation external id userid , anonymousid array of sha256 hashed values client ip address context ip not hashed client user agent context useragent not hashed fbc properties fbc > context clientids fbc facebook click id fbp properties fbp > context clientids fbp facebook browser id custom data (track events) track events include a custom data block with all event properties, enhanced with the following structured fields facebook field chord source (priority order) notes value properties total > properties value (via event extractor) string; defaults to "0" currency properties currency > properties meta i18n currency content ids each product's sku > product id > variant id (or configured content id field) array of product ids contents array of { id, quantity, item price } per product quantity defaults to 1 content type (derived) "product" for single product, "product group" for multiple content name first product's name content category first product's category num items count of products when no properties products array is present but properties sku exists, a single content ids entry is created from that sku property mappings use custom property mappings if the default field resolution does not match your data model destination path description properties email email for user matching properties total conversion value properties currency currency code (e g , usd ) properties products\[] sku product content ids properties products\[] price per item price properties products\[] quantity per item quantity