The Conversions API sends events from your server directly to Meta, complementing the browser pixel, which loses data to blockers and privacy restrictions. Well configured, with deduplication and validation, it improves measurement and optimisation, but requires care with consent and personal data.
The essentials in a definition
The Meta Conversions API sends events from your server to Meta, complementing the browser pixel. Good setup requires sending the right events, deduplicating with a common identifier between pixel and API, respecting consent and validating. The Conversions API documentation, the pixel one and Meta’s help pages describe requirements.
Why it complements the pixel
The pixel runs in the browser and is affected by blockers, restrictions and consent. The API sends server events, more stably. Combining both, with the same events, covers more conversions. It gives the system more signal to optimise and improves the remarketing audience.
Two channels, one set of events.
Set-up
Define the important events (content view, cart, checkout start, purchase, lead). Send them from the server with relevant parameters (value, currency, product identifiers). Use commerce-platform integrations or a server-side tag manager, depending on your stack. Document the configuration.
Prefer few, well-defined events.
Conversions API: setup, deduplication and validation
- Define few important events
- Send from the server with useful parameters
- Deduplicate with a shared ID
- Respect consent and validate
Deduplication
If the pixel and the API send the same event, the platform must recognise it as one, with a shared event ID. Without that, conversions duplicate and reports mislead. Test by sending an event and confirming it appears once, sourced from both. Use the platform’s diagnostic tools.
Duplicates inflate results.
Two measurement channels only help if they count each conversion once.
Consent and validation
Only send personal data when there is a legal basis and consent under the law. Apply privacy rules in both browser and server. Hash identifiers as required. Validate event quality and coverage. Review regularly, especially after site changes.
Measuring better does not excuse respecting people.
Decision table
| Step | What to do | Check |
|---|---|---|
| Events | Purchase, lead and key stages | Consistent names and parameters |
| Deduplication | Common event identifier | No double counting |
| Parameters | Value, currency, hashed identifiers where permitted | Match quality |
| Consent | Send only when permitted | Respect the state |
Common mistakes to avoid
- Not deduplicating. Events are counted twice.
- Sending data without a legal basis. It breaches privacy.
- Not validating against the database. Errors go unnoticed.
How to measure the result
Track deduplication, match quality and the difference between events and orders.
Limits and exceptions
Requirements change; confirm current documentation. The API improves reliability but does not eliminate losses from lack of consent. Technical support and maintenance are needed.
Illustrative example
Illustrative example: a store sends purchase and cart by pixel and by API with the same event identifier, includes value and currency and respects consent. It compares received events with orders and adjusts until the difference is acceptable. Match quality improves.
In practice: checkpoints
Document the events sent, the parameters and the deduplication logic, and keep a test guide to repeat after changes. Compare received events with orders daily in the first days, and then weekly. Monitor errors and sending delays, and create an alert when volume falls suddenly. Check that the consent state is respected, that sensitive data is not sent and that the access tokens are stored securely and rotated. Test with the platform’s diagnostic tools and review the match quality scores, then fix any parameters that are missing or in the wrong format. Keep the setup under version control if you use custom code, so you can see what changed and roll back quickly if something breaks.
Frequently asked questions
Does the API replace the pixel?
No. They complement each other, with deduplication.
Do I need consent?
Yes, according to the law and the legal basis used.
How do I test?
With the platform’s test and diagnostic tools.
Does the API replace the pixel?
It usually complements it; the combination with deduplication is common.
Which parameters should I send?
Those necessary and permitted, following the documentation.
Configure the Conversions API with essential events, identifier deduplication, quality parameters and respect for consent, and validate against the database.
Sources and recommended reading
Last editorial review: October 2026. Informational content; always confirm current conditions in the official sources before deciding.