Learn · How-To

How to Set Up Meta Conversions API (CAPI) for Accurate Ad Tracking

Browser-based tracking alone now misses a significant share of conversions due to ad blockers, cookie restrictions, and iOS privacy changes. Meta's Conversions API (CAPI) sends conversion data directly from your server, restoring accuracy to your ad reporting and optimisation. This guide assumes basic developer access to your website.

1. 1

   Confirm your Meta Pixel is installed

   Before adding CAPI, make sure your existing Meta Pixel is correctly installed and firing standard events (PageView, Lead, Purchase, etc.) using Meta's Events Manager test tool. CAPI is designed to work alongside the Pixel, not replace it — pairing both improves Event Match Quality.

2. 2

   Choose your CAPI integration method

   Options range from a partner integration (Shopify, WooCommerce, and similar platforms often have built-in CAPI support), to a tag-manager-based server-side container, to a fully custom server-side implementation using Meta's Conversions API endpoint directly. Choose based on your platform and available developer time.

3. 3

   Generate a Conversions API access token

   In Meta Events Manager, select your Pixel, go to Settings, and generate a Conversions API access token. This token authenticates server-to-server requests and must be stored securely on your server — never expose it in client-side code.

4. 4

   Map your events between Pixel and CAPI

   For each event you track via the Pixel (e.g. Lead, Purchase, CompleteRegistration), implement the matching server-side event via CAPI, sent at the same point in the user journey. Include as much customer information as possible — hashed email, phone, and external ID — to maximise match quality.

5. 5

   Implement server-side event sending

   When a tracked action occurs — for example, a form is submitted — your server sends an HTTP POST request to Meta's Conversions API endpoint with the event data, including a shared "event_id" that matches the corresponding Pixel event. This shared ID is what enables deduplication.

6. 6

   Use Event Match Quality to check data quality

   In Events Manager, each event source shows an Event Match Quality score. Higher scores mean more of the customer data points you're sending can be matched to a real Meta user, which directly improves how well Meta can optimise and report on your campaigns.

7. 7

   Test with Meta's Events Manager test tool

   Use the Test Events tool in Events Manager to confirm both Pixel and CAPI events are arriving correctly, with matching event IDs and no duplication, before relying on the data for campaign optimisation or reporting.

8. 8

   Monitor deduplication and match quality over time

   After launch, periodically review Events Manager for deduplication rates and Event Match Quality trends. Configuration drift — for example, a website update that breaks the server-side integration — can silently degrade tracking accuracy, so this isn't a set-and-forget step.