Skip to content
Meta Conversions API

Server-side events for Meta, none lost and none doubled

Convs takes in submissions from Meta forms, Google Sheets and your shop, then sends them to the Meta Conversions API. Every delivery has its own result, and failures go back to the queue.

List of Meta deliveries with the result of every event (Polish interface)

Screenshots from a demo organisation. People and numbers are fictional.

Three sources, one queue

Connect a Meta form, a Google sheet or a shop. Each source can send to several Meta datasets, and each destination has its own delivery status.

  • Meta forms: polled every 5 minutes, with an optional Page webhook
  • Google Sheets: pick a tab and map columns, synced every minute
  • Shop: your shop’s server sends paid orders to the hub, the browser script runs only after consent
Connected sources and Meta destinations (Polish interface)

Turn a status or stage into an event

A flow says what goes to Meta and under which name. For example, “paid” in a sheet becomes Purchase, and the “Qualified” stage becomes QualifiedLead.

Flow editor mapping statuses to Meta events (Polish interface)

Connection map

Campaigns, forms, flows and datasets on one graph. Scan one chosen ad account and see right away what is missing.

Connection map: campaigns, forms, flows and datasets (Polish interface)

Nothing lost, nothing sent twice

Events wait in a durable queue until Meta accepts them. A server restart does not drop them.

  • Deduplication by source, external ID and status
  • A second guard: dataset, event name and event_id
  • Email and phone normalised and hashed with SHA-256 before sending
  • Test mode with an Events Manager test code and separate deduplication

Meta accepting an event through the Conversions API does not prove your campaign optimises for it, or how Meta attributes conversions. You check that in Events Manager and Ads Manager.

Meta Conversions API

Frequently asked questions

Can’t find your question? Write to us

No. The Pixel and the Conversions API can run together. If both send the same event, use the same event name and event_id, and Meta counts it once.

The delivery is marked as failed with Meta’s description. Temporary errors are retried automatically, and you can retry the rest by hand after fixing them.

Yes. A destination in test mode sends events with a test code, so you see them in Events Manager before anything reaches production.

See what Meta sees

Connect your ad account and see which forms are ready and which need fixing. Free up to 100 leads a month, no card required.