Meta Conversions API Gateway alternative: Meta and eight more ad platforms, with no server to host
Meta's Conversions API Gateway is a server you run for Meta: the Meta Pixel sends each event to Meta and to the gateway, which passes it on to the Conversions API. It runs in your own AWS or Google Cloud account, or with a partner such as Stape at $10 a month per pixel; Meta says its only cost is cloud or partner fees (as of 7 November 2026). AgentFirstStack Tags sends the same server-side copy to Meta and eight more ad platforms with nothing to host, and an AI agent sets it up. Pick the gateway to keep Meta's software in a cloud account you control, or Meta's no-hosting Conversions API with Meta if Meta is all you need.
Set it up with one prompt
Paste this into your coding agent. It finds out how the site sends Meta events today first, and keeps the old setup running until you say so.
Send this project's Meta conversions server-side with AgentFirstStack Tags, instead of hosting Meta's Conversions API Gateway. It's a free, open-source tag manager built for agents that calls Meta's Conversions API, and other ad platforms' APIs, itself, and you can do the setup yourself: there is no signup form. 1. Read https://agentfirststack.com/llms.txt and https://tags.agentfirststack.com/llms.txt. 2. If this project's .env already has AGENTFIRSTSTACK_API_KEY, use it and read AGENTFIRSTSTACK.md. Otherwise get a key: curl -X POST https://agentfirststack.com/v1/signup, and save api_key in .env as AGENTFIRSTSTACK_API_KEY and in the production secrets. 3. Find out how the site sends Meta events today: a hard-coded Meta Pixel, Google Tag Manager, a pixel pointed at a Conversions API Gateway, a partner's gateway or a plugin. Create a tags container for the production domain, run scan, and tell me what you found before you change anything. 4. Serve the container from our own domain: a first-party domain (POST https://agentfirststack.com/v1/first-party-domains with a neutral subdomain such as edge.<our domain>; add the one CNAME it returns if you can change our DNS, otherwise give me the record), or meanwhile the path proxy from GET /v1/containers/:id/install?proxy=1 with its proxy key kept server-side. Put the snippet in the head of every page. 5. Run setup with meta, analytics and any other ad platform this business uses, and the conversions that matter here (purchases, leads, sign-ups). Ask me for the Meta pixel id, a Conversions API access token (Events Manager > the dataset > Settings > Conversions API > Generate access token) and a test event code (the Test events tab), unless you have tools that can get them. 6. Test the Meta destination and show me Meta's answer, open a preview and read its log, then publish. Send conversions only the backend knows (a paid order) with POST /v1/containers/:id/events, with the browser's afst('get','event_id') and visitor_id. 7. Leave the old pixel and the gateway running until I say so. When I do, remove the hard-coded pixel in the same change that publishes, so Meta doesn't count conversions twice, and tell me how to uninstall the gateway. 8. Write the container id and the env var name (never the key) in AGENTFIRSTSTACK.md, and create a claim link for me with POST https://agentfirststack.com/v1/claim-link. Tell me what you set up, what Meta's test returned, what's waiting on me, and give me the claim link.
What the Conversions API Gateway is
Meta calls it "a self-serve configuration option in Events Manager" that sends events with the Meta Pixel and the Conversions API "in a redundant set up" (Conversions API Gateway, as of 7 Nov 2026). The pixel on your site is configured with the gateway's endpoint, so each time it fires it sends the event to Meta and to the gateway. The gateway turns those browser events into Conversions API events and sends them to Meta, and the event_id for deduplication "is automatically generated and propagated".
It's "a standalone Meta product" with two parts: the server that receives and forwards events, and an admin UI that shows the connected pixels, event activity from both channels and the Conversions API success rate. One instance can serve several domains and several pixels. From version 1.6.0 it also takes events from a server, such as offline, app or CRM events, at /capi/{PIXEL_ID}/events on the gateway (Sending events directly from a server).
It sends to Meta. Meta's other gateway product, Signals Gateway, uses the same infrastructure to "create flexible events pipelines" with other sources and destinations (Gateway products). And for the simplest case Meta now points elsewhere: both gateway pages open with a note that, if you have a Meta Pixel and only need website events in Meta, Conversions API with Meta does it "without you having to host or maintain anything", turned on in Events Manager.
Where it runs and what it costs
Meta lists three cloud setups, "AWS EKS, AWS ECS Express, or GCP", provisioned within "a cloud provider's account owned by the business". You need admin access to that cloud account and to the Meta Pixel (Configuration). Setup starts in Events Manager's Settings tab, opens a prefilled AWS stack that takes "approximately 30 to 40 minutes", and ends with an admin account in the gateway's UI; a custom domain is recommended and needs access to your DNS provider (Setup guide, as of 7 Nov 2026). On Google Cloud, the install creates Cloud Run, Cloud Storage and Cloud Build resources in your project (GCP host onboarding).
On cost, Meta says the only one is "the associated cloud resource or partner fees". Its pages give no dollar figure for running it yourself; the ECS Express setup "can offer a lower fixed monthly cost", and the admin UI has a cost page with a budget and alerts (AWS ECS Express). Partners price it per pixel or by volume:
| Option | Who runs it | Price, as of 7 Nov 2026 |
|---|---|---|
| Your AWS account (EKS or ECS Express) | You | AWS's charges for the resources; Meta publishes no estimate |
| Your Google Cloud project | You | Google Cloud's charges for the resources; no estimate from Meta |
| Stape | Stape | $10 a month per pixel, or $8 billed annually; up to 10 million events a month per pixel; 7-day free trial |
| Datahash | Datahash, "a Meta-listed provider" | $10 a month up to 10M monthly events, after a 28-day free trial |
| Conversions API with Meta | Meta | Nothing to host; website events to Meta only |
How AgentFirstStack does it
AgentFirstStack Tags is a tag manager whose service calls the conversion APIs itself, so there's no gateway server in between and nothing for you to run.
- One container snippet fires the Meta Pixel, and any other pixels you use, with one
event_idper conversion, and posts the conversion to AgentFirstStack. - The service calls Meta's Conversions API with your pixel id and access token and the same
event_id, so Meta counts it once. It sends the hashed email and phone,_fbpand_fbc, and the visitor's IP and user agent that Meta matches on. The same conversion goes to every other platform you added. - Your backend reports what the browser can't see, a paid order or a qualified lead, with
POST /v1/containers/:id/events. Sent with the browser'svisitor_id, it's joined to the visitor's stored click ids, so it still credits the ad click days later. - Testing uses Meta's own test events. The destination test sends an event with your
test_event_codeand returns Meta's answer; test traffic is never sent to Meta as a real conversion. - Every delivery is logged for 7 days with Meta's answer:
GET /v1/containers/:id/events. - It runs on your own domain. A first-party domain is one CNAME from a subdomain such as
edge.example.comtofp.agentfirststack.com; the container loads fromhttps://edge.example.com/_t/, with no server code. Where DNS can't change, a path proxy on your own server does the same.
Meta needs two values from the owner: the pixel id and a Conversions API access token (Events Manager, the dataset, Settings, Conversions API, Generate access token), plus a test event code from the Test events tab for testing. The Meta Conversions API guide covers deduplication in detail, and conversion tracking lists every platform.
Side by side
| Meta Conversions API Gateway | AgentFirstStack Tags | |
|---|---|---|
| What it is | A Meta server application in your cloud account, or a partner's | A hosted tag manager that calls the conversion APIs itself |
| Where it runs | AWS EKS, AWS ECS Express or Google Cloud | Our hosted service, or self-hosted on Cloudflare Workers |
| Platforms | Meta | GA4, Google Ads, Meta, TikTok, LinkedIn, Pinterest, Reddit, Snap, X, analytics, webhooks |
| Browser events | The Meta Pixel sends each event to Meta and to the gateway | One container fires the pixels and posts each conversion to the service |
| Deduplication | An event_id generated and passed on automatically | One event_id per conversion, used by the pixel and the API |
| Backend events | A server endpoint on the gateway, from version 1.6.0 | POST /v1/containers/:id/events, joined to the visitor's click ids |
| Setup | Events Manager, a cloud stack (about 30 to 40 minutes on AWS), an admin account, and a recommended custom domain | POST /v1/signup, a container, the snippet, setup; a test against Meta's test events |
| Your own domain | A custom domain, recommended | A first-party domain (one CNAME) or a path proxy |
| Monitoring | Admin UI: event activity, Conversions API success rate | Delivery log for 7 days with each platform's answer; the setup check |
| API | A GraphQL control plane API on the instance, for partners managing accounts and data sources (Control plane API) | Signup, setup, test and publish over REST and MCP |
| Price | Cloud resources, or a partner's fee (Stape from $8 a month per pixel billed annually) | Free hosted service with fair-use limits (5 conversion APIs per container) |
| Source | Meta's software | AGPL-3.0; the browser runtime is MIT |
When to choose which
Use Meta's Conversions API Gateway if
- Meta is the platform that matters and you want Meta's own software, which updates itself with your admin's consent.
- Events should pass only through a cloud account your business owns, on AWS or Google Cloud.
- You host the gateway for many advertisers as an agency or partner: Meta's host onboarding is written for that.
Use Conversions API with Meta if
- You have a Meta Pixel and only need website events in Meta. Meta's note says it needs no hosting or maintenance: you turn it on in Events Manager.
Use AgentFirstStack Tags if
- You advertise on more than Meta: GA4, Google Ads, TikTok, LinkedIn, Pinterest, Reddit, Snap or X get the same conversion with the same event id.
- Conversions only your backend knows should credit the ad click that started them.
- An agent should set it up, test it against Meta's test events and read the delivery log, with no server to host or update.
- You want it open source, or self-hosted on your own Cloudflare account.
Moving from the gateway
There's nothing to import: on our side, Meta is a pixel id and an access token. scan finds the Meta Pixel on your pages and its id, and setup adds the pixel tag and the Meta destination.
Keep the gateway running until the delivery log shows Meta receiving the same conversions. Then, in one change, publish the container and remove the hard-coded pixel: two pixels firing one conversion with different event ids count it twice. Then uninstall the gateway with Meta's uninstall guide (delete the CloudFormation stack on AWS, or run its script in Cloud Shell on Google Cloud) and delete the CNAME records it used.
FAQ
What is the Meta CAPI Gateway?
The Meta Conversions API Gateway, often called the Meta CAPI Gateway, is Meta's server application for sending Meta Pixel events to the Conversions API from a server. Meta describes it as a self-serve option in Events Manager that runs in a cloud account the business owns, on AWS or Google Cloud; partners such as Stape and Datahash also host it for a fee.
How much does the Conversions API Gateway cost?
Meta's docs say its only cost is the cloud resources or a partner's fees, and give no dollar figure for self-hosting. As of 7 November 2026, Stape hosts it for $10 a month per pixel ($8 a month billed annually), and Datahash for $10 a month up to 10 million monthly events after a 28-day trial. AgentFirstStack's hosted service is free with fair-use limits.
Is the Conversions API Gateway the same as the Conversions API?
No. The Conversions API is Meta's API for sending events from a server. The gateway is one way to call it: a server that receives the pixel's browser events and sends them on to the Conversions API. Your own backend, a tag manager such as AgentFirstStack Tags, and Meta's Conversions API with Meta are others.
Does the Conversions API Gateway send to Google Ads or TikTok?
No. It forwards Meta Pixel events to Meta's Conversions API. Meta's Signals Gateway, built on the same infrastructure, sets up pipelines with other data sources and destinations. AgentFirstStack Tags sends each conversion to GA4, Google Ads, Meta, TikTok, LinkedIn, Pinterest, Reddit, Snap and X.
Can AgentFirstStack send Meta events from my own domain?
Yes. Add a first-party domain: POST https://agentfirststack.com/v1/first-party-domains with a subdomain such as edge.example.com, then the one CNAME it returns, to fp.agentfirststack.com. The container then loads and collects from that subdomain, with no server code. Where DNS can't change, a path proxy on your own server does the same.
Related
- Meta Conversions APIPixel and server, deduplicated by event id.
- Conversion trackingNine ad platforms, browser and server, one event id.
- Server-side conversion trackingHow each platform counts a conversion once.
- Stape alternativeConversion APIs without hosting a GTM server container.
- Server-side GTMWhat it is, what it costs to run, and the same result without it.
- Google Ads conversion trackingBrowser tag and server upload, tested before it counts.