The Meta Conversions API (CAPI) is a server side interface that lets advertisers send event data directly from their web servers to Meta\u2019s advertising platform. By bypassing the browser, CAPI improves data reliability, respects privacy settings, and complements the traditional Meta pixel.<\/p>\n
Browser based pixels depend on client side scripts that can be blocked by ad blockers, privacy settings, or browser restrictions. Server side tracking reduces data loss, aligns with recent privacy regulations, and provides more control over the payload sent to Meta.<\/p>\n
In Business Settings, navigate to System Users, add a new user, assign it to the ad account, and grant the “Ads Management” role. Generate a permanent access token for this system user \u2013 this token will be used in the Authorization header of every API request.<\/p>\n
Configure a webhook or an API route that captures conversion actions on your site \u2013 for example, a purchase confirmation page. Extract the necessary data (order value, currency, product IDs, and user identifiers) and format it according to Meta\u2019s event schema.<\/p>\n
Meta requires hashed user identifiers to improve matching. Collect email addresses, phone numbers, or external IDs, normalize them to lower case, remove whitespace, and apply the SHA\u2011256 hash function before sending.<\/p>\n
Construct a JSON object with the following structure:<\/p>\n
Include the “event_source_url” field to indicate the page where the conversion occurred.<\/p>\n
Use the endpoint https:\/\/graph.facebook.com\/v15.0\/{PIXEL_ID}<\/em>\/events. Attach the access token as a query parameter or in the Authorization header. Ensure the Content\u2011Type header is set to application\/json.<\/p>\n After transmitting the first event, open the Meta Events Manager and select “Test Events”. Your server side event should appear in real time. Use the “Diagnostics” tab to check for any errors such as missing required fields or mismatched hash formats.<\/p>\n In Events Manager, turn on “Automatic Advanced Matching” for the pixel. This allows Meta to supplement server side data with any browser side signals, improving overall match rates.<\/p>\n Event not appearing in Test Events<\/strong> \u2013 confirm that the access token is valid and that the request payload follows the latest schema. Check server logs for HTTP response codes; a 400 series indicates a malformed request.<\/p>\n Low match rate despite server side data<\/strong> \u2013 verify that user identifiers are correctly hashed and that the same format (email, phone) is used consistently across all events.<\/p>\n Duplicate conversions<\/strong> \u2013 implement idempotency by including a unique event_id for each conversion. Meta will ignore subsequent events with the same event_id.<\/p>\n Schedule regular reviews of the Events Manager diagnostics to catch schema changes early. Keep the access token refreshed whenever you rotate system user credentials. Document your server side event mapping in a shared repository to ensure consistency across development teams.<\/p>\n","protected":false},"excerpt":{"rendered":" Learn how to implement Meta Conversions API for reliable server side tracking, from prerequisite configuration to event testing, and ensure accurate measurement for your Meta campaigns.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[132,137,136],"tags":[],"class_list":["post-1503","post","type-post","status-publish","format-standard","hentry","category-meta-ads","category-server-side","category-tracking"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/posts\/1503","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/comments?post=1503"}],"version-history":[{"count":1,"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/posts\/1503\/revisions"}],"predecessor-version":[{"id":1506,"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/posts\/1503\/revisions\/1506"}],"wp:attachment":[{"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/media?parent=1503"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/categories?post=1503"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/apte.ai\/news\/wp-json\/wp\/v2\/tags?post=1503"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}6 Verify Event Delivery<\/h3>\n
7 Enable Automatic Event Matching<\/h3>\n
Troubleshooting Common Issues<\/h2>\n
Best Practices for Ongoing Management<\/h2>\n