# Conversions API

> Meta's server-to-server interface for sending conversion events, alongside or instead of the pixel.

Source: https://datacenter.so/glossary/conversions-api
Also called: CAPI, Meta Conversions API, Facebook Conversions API.

The Conversions API accepts events such as purchases and leads from your server. Required fields include `event_name`, `event_time`, `user_data` and `action_source`, with `event_source_url` for website events ([Meta](https://developers.facebook.com/docs/marketing-api/conversions-api/parameters/server-event)).

Meta matches events to people with hashed email and phone, the `fbc` click id, the `fbp` browser id, IP address and user agent. Run with the pixel, each event needs the same name and event id in both, or it counts twice. See [the Conversions API explained](https://datacenter.so/guides/meta-conversions-api-explained).

## Related terms

- https://datacenter.so/glossary/event-deduplication
- https://datacenter.so/glossary/fbclid
- https://datacenter.so/glossary/server-side-tracking