Meta Conversions API Gateway: Cost, Setup & Alternatives (2026)

What is the Meta Conversions API Gateway?

The Meta Conversions API Gateway (often shortened to CAPI Gateway) is a self-serve option in Meta Events Manager that deploys a small server inside your own AWS or Google Cloud account. Your Meta Pixel sends events to that server, and the server forwards them to Meta's Conversions API using a shared event_id, so Meta can deduplicate the browser and server copies of the same event. You don't write code.

Meta's documentation (last updated April 2026) describes it as a way to get a redundant Pixel + Conversions API setup running "without dedicated developer resources". That's a fair summary. What the summary leaves out is that you still own the infrastructure, the bill, and a single-destination pipeline.

This guide covers how the Gateway works, what it actually costs using Meta's own AWS numbers, the setup steps, where it falls short, and when another route is the better fit.

The Conversions API Gateway at a glance

Conversions API vs. Conversions API Gateway vs. Signals Gateway

These three names get mixed up constantly, and they are different things:

If you only need Meta conversion tracking, the Conversions API Gateway is the focused option. Signals Gateway is a data-routing hub and takes more configuration.

---

How the Conversions API Gateway works

The Gateway sits between your Pixel and Meta's Conversions API:

Visitor's browser
   └─ Meta Pixel (configured with your Gateway endpoint)
        ├────────────► Meta                       (browser event)
        └──► Conversions API Gateway              (your AWS / GCP account)
                  └──► Meta Conversions API       (server event, same event_id)

Meta's documentation breaks it into two modules running in your cloud account:

1. A middleware module that receives events from browsers, converts them into Conversions API events, and sends them to Meta.
2. An admin portal where you manage and monitor the instance. It lives on your own Gateway domain under /hub/capig.

The admin portal shows the connected Pixels, event activity from both the Pixel and the Gateway, the Conversions API success rate (the share of browser events successfully published to Meta), and notifications when a software update is available.

A single Gateway instance supports multiple Pixels and multiple domains. For events that never pass through the Pixel, such as offline or CRM data, Meta also lets you upload them by CSV or automatically from an Amazon S3 bucket, and provides an API endpoint for sending non-web events to the Gateway from your own server. Those are extra pipelines you build and maintain, separate from the Pixel flow.

---

How to set up the Conversions API Gateway

What you need before you start

• An AWS account (or Google Cloud) with permission to create CloudFormation stacks
• Admin access to the Meta Pixel in Events Manager
• DNS access to create a subdomain on your own domain for the Gateway endpoint
• An hour or two to deploy and verify

Step-by-step setup (AWS)

1. In Meta Events Manager, open the Settings tab and click Get started under "Set up with Conversions API Gateway".
2. Choose your cloud setup and a hosting region. You can only set up the Gateway in one region.
3. Click Next to open AWS, or Copy URL to hand the link to whoever administers your AWS account.
4. On the pre-filled CloudFormation quick-create page, leave the ProvisioningData field alone and click Create stack.
5. Wait for the stack to finish. Meta says this takes roughly 30-40 minutes; you'll see the status CREATE_COMPLETE when it's done. Then open the Outputs tab and note the CapigSetupURL.
6. Open the CapigSetupURL to reach the admin UI and finish provisioning. Set up a custom domain here. Meta recommends it because it "may help optimize data routing and may reduce costs", and you'll need a certificate through AWS Certificate Manager.
7. Connect your Pixel and domain, then verify delivery.

Verify it's working

Use this checklist once the Gateway is live:

• Events Manager shows events arriving from both the Pixel and the Conversions API
• Test Events shows server events with matching event_id values and a deduplication status
• The Gateway admin UI shows a healthy Conversions API success rate
• Event Match Quality is stable or improving after 24-48 hours
• An AWS budget alert is set so a traffic spike doesn't surprise you with the bill

Not seeing deduplication? Read What is Event Deduplication? before you assume the Gateway is broken.

---

How much does the Conversions API Gateway cost?

Meta doesn't charge for the Gateway. Its documentation says the only cost is "the associated cloud resource or partner fees". So the real question is: what will your cloud provider bill you?

Meta publishes estimates for the AWS ECS Express deployment (calculated with the AWS pricing calculator in the us-west-2 region):

Meta notes that the default setup supports up to 250 million events per month, and that auto scaling must be enabled for higher volumes. It also configures a default AWS Budget alert of $50 per month.

What drives the bill

Looking at Meta's line items, the largest costs are the load balancer ($17.13 at 10M events) and two always-on ECS containers ($8.51 each). Monitoring, logging, key management and a handful of small services make up the rest. Almost every one of those lines is identical at 10M and 250M events; only data transfer and the load balancer grow meaningfully.

That matters for small stores. The cost is mostly fixed infrastructure, not per-event usage, so a store sending 100K events a month should expect to land in the same ballpark as Meta's $39 figure rather than a fraction of it. That's my reading of Meta's table, not a quote, and AWS Free Tier credits can shift it either way.

Other deployment options

• AWS EKS is also supported. Meta's reference design runs dedicated EC2 instances around the clock, so it costs materially more than ECS Express.
• Google Cloud is the third supported option.
• Partner-hosted is a different route: companies such as Stape run a Gateway for you and charge a fee instead of you paying AWS directly. Our server-side tracking pricing comparison lists their Meta CAPI Gateway add-on at $8 per pixel per month on top of a plan.

The costs that aren't on the AWS invoice

• Your time. Roughly an hour to deploy and verify, plus ongoing monitoring.
• Account ownership. Someone has to own the AWS account, billing alerts, and access.
• Updates. The Gateway updates automatically, but only with the host admin's consent, so someone has to approve them.

---

What the Conversions API Gateway does well

It earns its place for a reason. Here's where it's strong:

• Fast compared with a hand-built integration. Meta says it can cut integration time from weeks to hours or even minutes.
• Meta-supported. It comes from Meta, so it tracks changes to the Conversions API.
• Automatic deduplication. The event_id is generated and propagated for you, which removes the most common source of double-counted conversions.
• Multi-Pixel and multi-domain. One instance can serve several Pixels and domains.
• Visibility. The admin UI shows event volume and the Conversions API success rate in one place.
• Non-web events. CSV and S3 uploads let you add offline or CRM events.

---

Where the Conversions API Gateway falls short

1. It only sends to Meta

The Gateway is a Meta-to-Meta pipeline. If you also run Google Ads, TikTok or GA4, you need Google Enhanced Conversions, the TikTok Events API and so on set up separately. Signals Gateway can route to other destinations, but it's a different product with its own pipelines to configure.

2. Web events start with the Pixel script

Meta's architecture is explicit: a Pixel configured with the Gateway endpoint sends events to the Gateway through the Pixel script. So the Gateway can only forward what the browser sends. If a visitor's ad blocker stops the Pixel from loading, or consent settings stop it from firing, there is nothing for the Gateway to forward. Its job is to make the server leg reliable, not to recover events the browser never produced.

3. You run the infrastructure

An AWS account, one hosting region, a DNS record, a certificate, billing alerts, and update approvals. None of it is hard, but all of it is yours. If nobody on your team is comfortable in AWS, this is where the "no-code" label gets tested.

4. The cost has a floor

As covered above, the bill is mostly fixed. For a small store, a roughly $39 monthly floor for Meta alone is a meaningful line item.

5. It forwards; it doesn't judge traffic quality

Meta's documentation presents the Gateway as a delivery and deduplication tool. It doesn't describe bot detection as part of it. If bots trigger your Pixel, those events are forwarded like any other, and Meta's optimization learns from them. We cover how much that costs in How Bot Traffic Wastes Ad Spend.

---

Conversions API Gateway vs. the alternatives

For the wider field, see Best Facebook CAPI Tools and Best Server-Side Tracking Tools.

When the Conversions API Gateway is the right choice

• You advertise only on Meta, now and for the foreseeable future
• Someone on your team is comfortable in AWS and will own the account
• You want a Meta-supported route rather than a third-party tool
• Your event volume is high enough that the fixed cost is small relative to your ad spend

In that situation the Gateway is a reasonable choice, and it can come out cheaper than a managed platform. We'd rather say so plainly than pretend otherwise.

When an alternative fits better

• You run Google Ads, TikTok or GA4 alongside Meta and don't want one pipeline per platform
• Nobody wants to own cloud infrastructure
• You want bot traffic filtered before conversions reach Meta and train its algorithm
• Your event volume is modest, so a roughly $39 floor is a large share of your tracking budget
• You want events captured in a way that doesn't rely only on Meta's Pixel loading

---

How SignalBridge compares

SignalBridge is a managed alternative. It runs the server-side infrastructure for you and sends the same events to several platforms from one integration. The setup is:

1. Install one tracking script on your site, or use the Shopify app
2. Connect your Meta account with one-click OAuth and pick your Pixel
3. Choose the events to send; deduplication is handled automatically
4. Verify in Events Manager

There's nothing to host and no AWS account to manage. Bot filtering is on by default, so fake conversions are stopped before they reach Meta, Google Ads or TikTok. Plans start at $29/month with a 14-day free trial; see the full SignalBridge pricing breakdown for how that stacks up.

Prefer to compare the no-code route in more depth? Read How to Set Up Facebook CAPI Without GTM or SignalBridge vs. Stape.

Start your 14-day free trial - no credit card required.

---

FAQ

What is the Meta Conversions API Gateway?

The Meta Conversions API Gateway, also called the CAPI Gateway, is a self-serve option in Events Manager that deploys a server in your own AWS or Google Cloud account. It receives events from your Meta Pixel and forwards them to Meta's Conversions API with automatic deduplication, without requiring you to write code.

Is the Conversions API Gateway free?

Meta doesn't charge for it, but it isn't free to run. You pay your cloud provider for the infrastructure. Meta's published estimate for the AWS ECS Express deployment is $39.27 per month at 10 million events, and most of that cost is fixed, so smaller stores should expect a similar baseline. Partner-hosted versions charge a fee instead.

What is the difference between the Conversions API and the Conversions API Gateway?

The Conversions API is Meta's endpoint for receiving events directly from a server. The Conversions API Gateway is a Meta-built forwarder that you host yourself: it takes events from your Meta Pixel and sends them to the Conversions API for you. Both end up in the same place; the Gateway just saves you from building the server integration.

Do I still need the Meta Pixel if I use the Conversions API Gateway?

Yes. The Gateway is designed for a redundant setup in which the Pixel keeps running. Web events reach the Gateway because the Pixel is configured with the Gateway endpoint, so without the Pixel there are no web events to forward.

How long does it take to set up the Conversions API Gateway?

Meta says the AWS stack takes approximately 30 to 40 minutes to create. Add time for setting up a custom domain and its certificate, connecting your Pixel and domain, and verifying events in Events Manager, so plan for an hour or two in total.

Can the Conversions API Gateway send events to Google Ads or TikTok?

No. The Conversions API Gateway forwards to Meta only. To send events to Google Ads, TikTok or GA4 you need other tools. Meta's separate Signals Gateway can route to other destinations such as Google BigQuery or a custom HTTPS endpoint, but it is a different product with its own configuration.

What is the difference between the Conversions API Gateway and Signals Gateway?

The Conversions API Gateway is a focused pipeline from your Meta Pixel to Meta's Conversions API. Signals Gateway is a more general self-hosted data hub that collects events from several sources, including web, app, offline and custom HTTP, and routes them to several destinations through configurable pipelines. Use the first for Meta-only tracking and the second when you need one hub for multiple destinations.

Is the Conversions API Gateway cheaper than SignalBridge?

It can be, for the right setup. If you advertise only on Meta and already run AWS, a roughly $39 monthly cloud bill can undercut SignalBridge's Growth plan. SignalBridge starts at $29 per month, includes bot filtering, and sends to Meta, Google Ads, TikTok and GA4 from one integration without any infrastructure to manage, so the better value depends on how many platforms you use and who maintains the setup.

Does the Conversions API Gateway filter bot traffic?

Meta's documentation doesn't describe bot detection as part of the Gateway. It forwards the events your Pixel sends, so bot-triggered events pass through like any other. If bot traffic is a concern, filter it before events reach Meta, for example with server-side bot filtering.

---

Related reading

• What is CAPI? Meta CAPI (Conversions API) Explained - the fundamentals behind everything the Gateway forwards
• Meta CAPI vs. Facebook Pixel - why Meta recommends running both
• Best Facebook CAPI Tools in 2026 - compare every way to send events to Meta
• How to Set Up Facebook CAPI Without GTM - the no-code route in detail
• Facebook Conversions API Setup for E-Commerce - an e-commerce focused walkthrough
• Server-Side Tracking Cost in 2026 - what each approach really costs
• SignalBridge vs. Stape - managed platform vs. partner-hosted infrastructure
• What is Event Deduplication? - the part the Gateway automates
• Bot Traffic in Google Ads: How It Wastes Your Ad Spend - why filtering matters before events reach any ad platform