Conversions API
Browser tracking misses events because of ad blockers, browser restrictions and short-lived cookies. The Conversions API sends the same events from your server, so Meta sees more of what actually happened.
How it works
Your server (or a partner integration, or the Conversions API Gateway) sends events directly to Meta with customer information such as hashed email and phone, IP address, user agent and the click ID (fbc) and browser ID (fbp) cookies when available.
Run it with the Pixel
Meta recommends a redundant set-up: send each event from both the Pixel and the server. Give both copies the same event_name and event_id so Meta can deduplicate them and count the event once.
Event Match Quality
Events Manager scores how well your server events can be matched to Meta accounts. Sending more customer information fields, correctly hashed, raises Event Match Quality, which improves attribution and optimisation.
Offline and CRM events
Send later outcomes from your CRM (qualified lead, sale closed) as server events. That lets Meta optimise lead campaigns toward conversions further down the funnel than the form fill.
Pro tips
- Use a partner integration if your platform offers one; it handles hashing and deduplication.
- Check the deduplication rate in Events Manager after launch.
- Send qualified lead events from your CRM to optimise for lead quality.
Common mistakes
- Sending server events without event_id and double counting.
- Sending unhashed personal data.
- Ignoring a low Event Match Quality score.
Send events from your server with the Conversions API alongside the Pixel, deduplicate with event_id, raise Event Match Quality and add CRM outcomes.