Key takeaways
- A conversions API gateway is a hosted forwarder that sends events to Meta's Conversions API on your behalf, with no custom server code.
- It sits between your site and Meta, receiving pixel events and relaying them server-side, usually from your own subdomain.
- It handles hashing, deduplication, and the connection, which is the work a manual Conversions API build otherwise requires.
- Meta offers a gateway you self-host on cloud infrastructure; managed providers run it for you.
- It is a delivery mechanism, not a data strategy: it forwards whatever the pixel sends, well or badly.
- The trade-off against a custom build is control: a gateway is faster to stand up but less bespoke.
- Showmax went live on Meta Web CAPI in about 15 minutes, the kind of speed the gateway model is built for.
What is a conversions API gateway?
A conversions API gateway is a piece of hosted infrastructure that does the server-side half of Meta tracking for you. Running the Conversions API directly means standing up a server, writing the code that formats and hashes events, opening the connection to Meta, and keeping it all alive. A gateway packages that into a deployable service. Your pixel points at the gateway, the gateway forwards the events to Meta through the Conversions API, and you never touch server code. Meta for Developers documents an official Conversions API Gateway that a business can deploy on its own cloud instance, and managed providers offer the same pattern as a service. Either way, the gateway is the thing that turns browser events into reliable server-side events.
How does a conversions API gateway work?
A conversions API gateway works by intercepting the events your pixel already produces and relaying them to Meta server-side. The flow runs in order:
- Your Meta Pixel fires in the browser as usual when a customer acts.
- The events are also routed to the gateway, typically hosted on a subdomain of your own site.
- The gateway normalises and SHA-256 hashes the customer identifiers on each event.
- It forwards the events to Meta through the Conversions API, attaching the shared event ID.
- Meta deduplicates the pixel and gateway versions on that event ID, keeping one.
Hosting the gateway on your own subdomain matters, because a first-party domain is treated more favourably by browsers than a third-party one, which protects the identifiers the events carry. Datahash offers a Meta CAPI gateway with one-click setup and a guide to deploying the Meta CAPI gateway on your own subdomain.
How do you set up a conversions API gateway from Meta Events Manager?
Setting up a conversions API gateway starts in Meta Events Manager, where the pixel and its events already live, and ends with the gateway relaying those events. The steps run in order:
- In Meta Events Manager, identify the pixel and the events you want to send server-side.
- Deploy the gateway, either self-hosted on a cloud instance or through a managed provider, on a subdomain of your site.
- Connect your pixel to the gateway so events route through it as well as firing in the browser.
- Confirm identifiers are normalised and hashed, and that each event carries a shared event ID for deduplication.
- Verify in Events Manager that server events arrive and deduplicate cleanly against the pixel before scaling.
The same gateway pattern exists beyond Meta. Datahash also runs a Snap CAPI gateway set up from Ads Manager, and the wider picture is covered in what the Conversions API is on every platform.
Gateway or custom build: which should you use?
Choosing between a conversions API gateway and a custom Conversions API build comes down to speed against control. A gateway is faster to stand up and needs no engineering to maintain; a custom build gives you full control of the payload and logic but is yours to keep alive. The comparison below lays out the trade-off.
| Option | What it gives you | What it costs | When to use |
|---|---|---|---|
| Hosted gateway | Server-side events fast, no code to maintain | Less control over custom event logic | You want reliability without an engineering project |
| Custom CAPI build | Full control of payload, routing, and logic | Engineering to build and maintain it | You have unusual events or in-house engineering |
| Managed gateway | Gateway plus a provider running it | A dependency on the provider | You want the speed and none of the upkeep |
What are the limits of a conversions API gateway?
A conversions API gateway solves delivery, not data quality. It forwards the events your pixel produces, so if the pixel sends thin or wrongly formatted events, the gateway forwards thin, wrongly formatted events, only more reliably. It does not decide which events matter or enrich them with identifiers you did not capture. A self-hosted gateway is also real infrastructure: it runs on a cloud instance you pay for and are responsible for, so it is lower effort than a full build but not zero. And it is Meta-shaped. The gateway pattern covers the Conversions API, but sending offline sales or CRM outcomes still needs the matching server-side connection for those. A gateway is the fastest path to server-side web events. It is not a complete measurement stack by itself.
What Datahash does about this
Datahash runs the conversions API gateway as a managed service, so a business gets server-side events without deploying or maintaining anything. It stands the gateway up on your own subdomain, handles the SHA-256 hashing and normalisation, and configures deduplication against the pixel so numbers stay honest. The same first-party data layer also carries app, offline, and CRM events, and extends the gateway pattern to Snap, so one setup covers more than Meta web. Because the hashing happens before anything leaves your systems, the flow stays consistent with GDPR and DPDP. Showmax went live on Meta Web CAPI in about 15 minutes on this infrastructure, and KFC recorded 5% additional purchases running the Conversions API alongside the pixel, because the gateway made the server path reliable without a build. Delivery and deduplication are visible in Events Manager, so you can confirm it is working.