The Conversions API is a channel that faxes your shop ledger to head office, separate from the visit counter (pixel). Even if a customer never passed the counter, the ledger (your server) still has the record, so you send that.
The developer docs describe it as connecting an advertiser's marketing data (website, app and messaging events and offline conversions) from their server, website platform, app or CRM to Meta systems, to optimize ad targeting, lower cost per result and measure outcomes. Server events are linked to a dataset ID and processed like events sent by the Meta Pixel or SDKs, so they can be used in measurement, reporting and optimization. Offline events can also support offline custom audiences and measurement.
Adoption has three steps: choose an integration method and get started; implement POST requests to send events; verify that Meta received events and that deduplication and matching are right. The payload helper and parameter docs help you check event shape.
Using it together with the Pixel is called a redundant setup, and the docs recommend it. Sending the same event down two paths requires deduplication, so read the deduplication entry too. The Limited Data Use data processing option can also be applied through the Conversions API.
When to use
Use it when browser blocking or exits leak pixel events, or when you want offline or CRM conversions to feed ad optimization.