Home/Services/Meta / Facebook Tracking/Meta Conversions API
Meta Conversions API Setup for Advertisers
We connect your site or store to the Meta Conversions API so key conversions reach Meta from your server as well as the browser. Every event carries an event ID for deduplication and the customer parameters Meta uses for matching. For advertisers who want Events Manager to reflect real orders and leads.
Meta advertisers who see missing conversions or low event match quality in Events Manager
- Server events for key conversions
- Event ID deduplication with the pixel
- Customer parameters for match quality
- Events Manager coverage review
Free 30-minute tracking audit • No obligation
Why Meta Is Not Seeing All of Your Conversions
A pixel-only setup depends on the browser. A rushed Conversions API setup often creates new problems, such as double counting or server events that carry almost no customer data.
Blocked Browser Events
Ad blockers and browser privacy features stop some pixel requests, so conversions happen but Meta never hears about them.
Double Counted Purchases
Server and browser events sent without a matching event_id and event_name are counted as two separate conversions.
Server Events With Little Data
CAPI events without hashed email, phone, fbp or fbc get low match quality and help Meta far less than they should.
What We Build Into Your Conversions API Setup
The focus is on what Meta needs from each event: the right event name, a shared ID with the pixel, and enough customer information to match the conversion to an ad viewer.
Conversion Event Selection
We decide which events go through CAPI, usually Purchase, Lead and other events you optimize for.
Event ID Deduplication
A shared event_id generated once and sent with both the pixel and the server event.
Customer Information Parameters
Hashed em, ph, fn, ln and external_id, plus client IP address and user agent, sent where available.
fbp and fbc Forwarding
The browser ID cookie and click ID captured on site and passed with each server event.
Integration Method
Native partner integration, CAPI Gateway or server-side GTM chosen to suit your platform.
Event Match Quality Review
Match quality and deduplication checked per event in Events Manager after launch.
How a Conversion Reaches Meta Twice and Counts Once
The same conversion is sent from the browser and the server with one shared event ID. Meta keeps one and uses the richer customer data for matching.
Order placed or lead submitted
One ID shared by browser and server
Browser sends event with fbp and fbc
CAPI sends event with hashed customer data
Matching event_name and event_id merged
One conversion attributed to the ad
What's Included in Meta Conversions API
Clear deliverables, documented and validated before handover.
Current Event Coverage Audit
We compare your pixel and any existing server events against real orders or leads to find where coverage falls short.
Conversions API Integration
Server events configured through the method that suits your platform, with access tokens stored securely.
Deduplication Setup
Event IDs wired through the data layer so browser and server events pair correctly.
Match Quality Parameters
Customer information fields normalized and hashed with SHA-256 before they are sent.
Test Events Verification
Every server event checked in Test Events, with deduplication confirmed in the event overview.
CAPI Documentation
A reference of events, parameters, event ID logic and the integration method, handed to your team.
From Audit to Validated Data
How a Meta Conversions API project runs, step by step.
Audit
Audit pixel events, existing CAPI events and current match quality scores.
Strategy
Choose the CAPI method, the events to send and the customer data to include.
Implementation
Implement server events with event IDs and hashed customer parameters.
Testing
Test server and browser pairs in Test Events and confirm deduplication.
Validation
Validate event counts and match quality in Events Manager after launch.
Platforms and Tools We Work With
The tools involved in a typical Meta Conversions API implementation.
Server events
Paired browser events
Match quality and dedup
Optional event routing
Order and customer data
Meta Conversions API FAQ
Straight answers before you book. Still have a question? Talk to us directly.
How does Meta deduplicate pixel and CAPI events?
Meta compares the event_name and event_id of browser and server events. When both match within the deduplication window, it keeps one event. The key is generating the event ID once, on the page, and passing that same value to both the pixel and the server request.
Which integration method will you use?
It depends on your platform and your other tracking. Shopify and some other platforms have native partner integrations. CAPI Gateway suits advertisers who want a managed option. Server-side GTM suits businesses that also send server data to GA4 or Google Ads. We recommend one and explain why.
How is this different from your server-side Meta CAPI service?
This service is about what Meta receives: which events, how they deduplicate and how well they match. Our server-side tracking category covers the infrastructure behind it, such as hosting and running a server-side GTM container. Many clients need only this service, others need both.
Can the Conversions API send offline or CRM conversions?
Yes. CAPI accepts events that happen outside the website, such as a lead marked qualified in your CRM or a sale closed by phone. We can send those with the customer data you hold so Meta can link them back to ad interactions.
Is customer data sent to Meta safely?
Customer information such as email and phone is normalized and hashed with SHA-256 before it is sent, as Meta requires. We only send fields you collect with a lawful basis and connect sending to your consent setup where needed.
Will event match quality reach a specific score?
We cannot promise a score. Match quality depends on what data your visitors provide and what you are permitted to send. We make sure every available parameter is sent correctly and show you which remaining fields could be added.
Services That Work Well Together
Tracking is a system. These services are often delivered alongside this one.
Hashed customer data added to Meta events so more conversions match to the people who saw your ads.
A combined Meta setup where the pixel and Conversions API work together as one deduplicated event stream.
Meta Conversions API tag in your sGTM container, sent from your own first-party endpoint.
Stop Guessing. Start Measuring.
Get a professional review of your tracking setup and discover where your marketing data may be leaking.
Free 30-minute review • No obligation