← All articles

Conversions API Gateway: What It Really Costs and When to Use Something Else

Meta's own answer to "how do I set up the Conversions API without a developer" is the Conversions API Gateway. It's free in the sense that Meta doesn't send you an invoice. It's not free in the sense that someone pays for the servers it runs on — and that someone is you.

This article explains what the Gateway actually is, what it costs, and the one big thing it doesn't do that matters a lot for businesses selling through a sales team.

What the Conversions API Gateway is

The Gateway is a small server application that Meta maintains, but that runs in your own cloud account — AWS or Google Cloud. You deploy it from Events Manager, point a subdomain at it (something like capig.yoursite.com), and connect your pixel.

From then on, every event your pixel sees in the browser is also sent to Meta from the Gateway server. The Gateway generates a shared event_id so Meta can deduplicate the two copies. In short: it's a mirror. It takes what the pixel already sees and sends it a second time over a channel ad blockers can't easily cut.

If you're new to the topic, start with What Is Meta Conversions API — it explains why the server-side copy matters at all.

What it costs

Meta charges nothing for the Gateway software. You pay for the cloud resources it uses. In its architecture documentation for the AWS version, Meta lists these estimated base costs (US-West region):

Events per month Estimated AWS cost per month
10 million≈ $39
250 million≈ $84
2.5 billion≈ $600

Two things are worth noticing. First, there's a floor: even a small site with a few thousand visitors a month pays roughly the base amount, because the infrastructure (containers, load balancer, CDN, database, logging) runs whether traffic is high or not. Second, the setup creates a long list of AWS services — ECS containers, a load balancer, DynamoDB, S3, CloudFront, Cognito, CloudWatch, Lambda and more. If nobody on your team has opened an AWS console before, that list is the real cost.

There's also a middle option: hosting partners that run the Gateway for you. Pricing varies; for example, Stape lists plans from free (up to 10,000 events) to around $17/month for up to 1 million events and more for higher volumes. You avoid managing AWS, but you add another vendor.

What the Gateway does well

What it can't do

The Gateway is built around browser events. It mirrors what the pixel sees. So everything the pixel can't see, the Gateway can't see either:

For an online store where the purchase happens on the site, that's fine. For a clinic, a real-estate agency, a school or a B2B company, it's the whole point. The event Meta most needs to learn from — "this lead became a paying customer" — lives in the CRM, and the Gateway has no connection to it. Meta keeps optimizing for form fills, including the fake numbers.

Gateway vs other options

CAPI Gateway (self-hosted) Direct integration LeadMe
Website eventsYesYesYes (site script, WordPress plugin, forms)
CRM stages and offline salesNoIf you build itYes
Other ad platformsMeta onlyEach one built separatelyTikTok, Google Ads, Snapchat, Pinterest, Reddit and more
You manage serversYes (AWS/GCP)YesNo
Typical monthly costFrom ≈ $39 in cloud feesDeveloper time + hostingFrom $11

So which one should you pick?

Choose the Gateway if you sell online, the purchase happens on your website, you (or someone on your team) are comfortable in AWS or Google Cloud, and Meta is your only ad platform.

Choose a direct integration if you have developers, a custom backend and unusual requirements — and someone who'll maintain it when Meta changes API versions.

Choose a CRM-based integration like LeadMe if your sales close outside the website: by phone, in a CRM, in messengers. LeadMe connects to AmoCRM (Kommo), Bitrix24, HubSpot, Pipedrive, Google Sheets, Stripe, Shopify or any CRM through a webhook, and sends each deal stage you choose to Meta through the Conversions API — with hashing, deduplication and click IDs handled for you. No cloud account, no subdomain, no containers.

You can also combine them: Gateway for on-site events, LeadMe for CRM stages. Just make sure the event names don't overlap, so Meta doesn't count the same lead twice.

Quick answers

Is the Conversions API Gateway free?

The software is. The cloud hosting isn't — Meta's own estimate starts around $39/month on AWS for up to 10 million events.

Do I need a developer to set up the Gateway?

Meta says marketers "with some technical expertise" can do it. In practice you need access to a cloud account with billing, permission to create a DNS record, and patience with the AWS console.

Can the Gateway send offline or CRM conversions?

It's built to mirror browser events from your pixel. Sales that happen in a CRM or offline need a different integration.

Related: Conversions API vs Meta Pixel · How to send CRM sales to Meta · Set up Conversions API without a developer