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.

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

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.

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

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.
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 also
- CRMOne person per phone or email, full history, stages, owner and tasks.See details
- AutomationsSMS to new leads, tasks and webhooks, with sending hours and an opt-out list.See details
- Campaign reportingMeta spend joined with CRM stages: cost per lead, per qualified lead and per sale.See details
- For agenciesA separate workspace per client, roles, an all-clients overview and job queues.See details
- Security and privacyEncryption, hashing, roles, retention and self-hosting.See details
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.