Meta’s Conversions API Gateway gives you server-side event delivery without writing CAPI code: your pixel traffic routes through a gateway, which forwards events to Meta’s Conversions API and deduplicates them against the browser pixel. Running it on your own subdomain, such as capig.yourbrand.com, means event collection happens on a domain you control.
Deploying and operating a gateway yourself means owning cloud infrastructure, monitoring and cost. With Datahash, the gateway is deployed for you through Meta’s one-click setup and managed as a subscription, and you put it on your subdomain with a short DNS exercise. Here is how.
Prerequisites
You need admin access to Meta Events Manager for the dataset (pixel) you want to connect, your Meta Business ID, and access to your DNS provider so you can add records for the subdomain. Decide the subdomain name up front; a dedicated one like capig.yourbrand.com works well.
Step 1: Start the one-click setup from Events Manager
In Events Manager, start the Conversions API Gateway setup and choose Datahash as the integration. Connect with your Meta Business ID and select the dataset you want to route through the gateway. If you have several unclaimed datasets, you can select more than one and onboard them in a single pass.
Step 2: Complete the gateway setup in Datahash
The one-click flow hands you off to the Datahash platform, where your gateway appears with its own pipeline setup. Every plan starts with a free trial, and billing is per pixel from then on, so you can activate now and decide later. There is nothing to provision on your side: no cloud account, no stack, no instances.
Step 3: Set up your subdomain
This is the step that puts the gateway on your own domain, and it is built into the pipeline setup.
- In the gateway pipeline setup, open Subdomain Setup and enter the subdomain you chose, for example capig.yourbrand.com.
- The platform detects your registered domain and shows a DNS setup screen with the exact records to add, with instructions tailored to your DNS provider. If your provider is not listed, generic instructions cover any registrar.
- Log in to your DNS provider and add the records exactly as shown. Copy-paste them; a stray space or trailing dot is the most common reason validation stalls.
- Return to the platform and finish the flow. The setup shows as in progress while your DNS records propagate and verify, and the subdomain’s status stays visible in the platform’s DNS manager afterwards.
Once verified, your pixel traffic collects on your subdomain and routes through the gateway to Meta.
Step 4: Verify events are flowing
In Events Manager, confirm events now arrive with the server connection channel alongside browser, and that shared events show as deduplicated. In the Datahash platform, the gateway’s Overview screen shows your setup status, subscription and invoices in one place, along with a link to the implementation guide.
Managing the gateway after setup
Everything stays in the Datahash platform. Subscriptions are per pixel: you can add more pixels to the gateway later, upgrade a plan, or cancel an individual pixel from the Overview screen without touching the rest of the setup. If you ever want to change the subdomain, the DNS manager is where you update it; keep in mind that removing the DNS records at your registrar stops event collection on that subdomain, so plan changes rather than deleting records ad hoc.
Troubleshooting
If DNS verification stalls, check the records at your registrar character for character against what the setup screen shows. If events flow but nothing deduplicates in Events Manager, confirm the same dataset ID is live on both the browser pixel and the gateway connection. And for anything else, the support team has done this DNS dance with every major registrar; reach out through the platform.