Meta’s Conversions API Gateway sends a server copy of your Pixel’s web events to Meta without a custom API integration. Your browser Pixel keeps firing, and Meta counts the browser and server copies as one event when they share an event name and event ID. You connect the Pixel to a Gateway that runs on a server you pay for. Meta’s software is free; the hosting is not.

The Gateway makes delivery more reliable. It does not make the event more truthful. It carries an existing web event through a second path, with better matching and automatic deduplication, but it cannot confirm that a payment went through, that the buyer was unique, or that the business had permission to send the data.

I run tracking implementations for clients, and I built Advanced Tracking Academy around the server containers I deploy in production. This page covers the Gateway on its own: how it works, what you need first, the setup on a managed host, how to test it, what it costs and what it leaves unsolved. The decision between the Gateway and a full container has its own comparison page.

How the Conversions API Gateway works

The Gateway is one way to send events through the Conversions API. Your Meta Pixel stays the source of the web event. Meta’s Gateway documentation says that once the Pixel is configured, it sends each event “to both Meta and the Conversions API Gateway”. The Gateway then forwards a server copy to Meta, and the event_id used for deduplication is generated and passed along automatically.

Flow diagram showing a website event taking a browser route and a first-party Gateway route to Meta, where a shared event name and event ID mark both copies as one event.
The Gateway adds a server route to an event the Pixel already knows. A shared event name and event ID keep the two deliveries from becoming two conversions.

Compared with a hand-built integration, you don’t write each request, keep an access token in custom code, or build the deduplication logic. The trade-off is scope and control. The Gateway only sends to Meta, and its controls are basic: turn an event on or off, allow or block a domain, choose which customer fields automatic advanced matching may share. It has no per-event conditional logic, no free payload transformation and no check against your business systems. For the payload fields and the matching rules, see the Facebook Conversions API guide.

Why a server route helps the Pixel

The browser Pixel is not a complete record. Ad blockers and browser tracking protection can stop the Pixel script or its request for some visitors. Safari deletes script-set cookies such as _fbp after seven days without user interaction with the site, and caps them at 24 hours when the visit came through a link decorated by a site WebKit classifies as a tracker (WebKit tracking prevention, checked 2026-10-17). Apple’s App Tracking Transparency is a separate, app-side problem that a web Gateway does not touch.

When the Pixel still fires, sending a copy through a first-party server path can recover part of what the browser loses, because that copy does not travel to a domain blockers target. The ceiling is hard. The Gateway only receives what the Pixel sends, so if the Pixel script never loads, there is nothing to route. A purchase sent from your backend, such as a processor webhook, is the only path that does not depend on the browser firing at all.

Match quality is a separate question. Event Match Quality is Meta’s per-event score out of 10 for how useful the customer information on a web event is for matching, and the EMQ score guide covers how to read it. It does not measure how many events were recovered. Judge recovery by received-event counts and by reconciling against your order system.

What you need before setting up a CAPI Gateway

A working Pixel comes first. The Gateway cannot discover a Purchase the site never fires, and it cannot fix a wrong value or currency at the source.

You also need access to the Business Manager and the dataset your Pixel reports into, DNS access if you want a first-party subdomain, and a hosting region close to your visitors. Decide who owns the Gateway after handoff.

The ownership question has a domain side that is easy to miss. Stape’s setup guide says a hub with several Pixels uses one custom domain. Take an agency hub with a custom domain under client A’s site, say capig.client-a.com, and client B’s Pixel added to the same hub. On client B’s site, the Gateway requests now go to a hostname under client A’s domain, which is third-party traffic and defeats the reason for the subdomain. With that one-domain setup, client B needs its own Gateway under its own domain, and a client-owned Gateway with the client’s admin email is usually the cleaner handoff anyway. Stape also sells setups that avoid this: its Gateway page advertises several domains and custom subdomains within one hub or cluster, and its setup guide offers a private multiuser hub at $500 a month for up to 1 billion requests (both checked 2026-10-17).

Finally, audit the site for any existing Conversions API integration. An old plugin or server tag left running sends a third copy outside the browser and Gateway pair, and Meta’s documentation only describes deduplicating a browser copy against a server copy, not two server copies against each other.

Use this preflight list before opening the setup screen:

  • The Meta Pixel fires the intended standard or custom events.
  • value and currency are correct on revenue events.
  • The operator has access to the Business Manager and dataset.
  • The admin email and long-term owner are decided.
  • DNS access is available if you plan to use a custom subdomain, one per client site.
  • Any existing Conversions API plugin, direct integration, or server tag is documented.
  • Consent behavior has been tested for accepted and declined states.

Setting up the Gateway on a managed host

The steps below follow the managed-host path, with Stape as the example because this site is a Stape affiliate and knows that flow. If you deploy on your own cloud, Meta’s documentation lists three targets for a cloud account the business owns: AWS EKS, AWS ECS Express, or GCP (checked 2026-10-17). The hosting steps differ there; the connection and validation steps stay the same.

  1. Create the Gateway. Enter a descriptive name, a unique admin email, and the server location closest to your main audience.
  2. Activate the host. Select the plan, wait until the Gateway shows a running state, and accept the hub invitation sent to the admin email.
  3. Add the data source. Connect the Business Manager and select the intended dataset or Pixel.
  4. Review matching parameters. Enable automatic advanced matching only after deciding which customer fields the business may share.
  5. Add a custom domain (recommended). The default URL works, but a first-party subdomain makes the request read as first-party traffic and helps it avoid some blocking. Create the supplied DNS record and complete verification in the hub.
  6. Control the event set. Let the Gateway detect Pixel events, then disable any event that should not travel through the server route.
  7. Run a real validation. Trigger a lead or a low-risk purchase, then check the browser request, the Gateway receipt, the server delivery and the deduplication result.
Illustration of a Gateway data source panel showing a connected Pixel, selected matching parameters, a verified custom domain and received events.
Illustration of the Gateway data source state, not a capture. A connected account is only the start; the custom domain and incoming events still need verification.

The hub labels change over time, so follow the live screen rather than an old screenshot. The steps describe what each part is for, which stays stable when button names move.

Testing whether the Gateway works

Test the chain in layers, not by one green status. In the browser network panel, confirm the event reaches the configured Gateway URL. In the hub, check the event name and receipt state. Stape’s guide says the count should be above zero within 30 minutes. In Events Manager, confirm that normal traffic produces browser and server deliveries that deduplicate into one event.

Check Where to inspect What a pass looks like
Pixel source Browser and Pixel tooling Correct event name, value, currency and identifiers
Gateway route Browser network panel Request reaches the first-party Gateway URL
Hub receipt Gateway data source view Expected event appears and the domain is allowed
Server delivery Events Manager Browser and server channels are visible on normal traffic
Deduplication Events Manager diagnostics One real action is counted once, with no extra copy
Business truth CRM, order system or processor Tracked outcomes reconcile with the system that records the result

A pass on the first five rows without the sixth is a setup that looks done and is not.

One trap from our own lab testing applies here. In a reproduction on 2026-10-06, with a real dataset’s signals configuration, Meta’s Pixel library (fbevents.js as served that day) sent nothing while the browser’s user agent contained HeadlessChrome. The same headless Chromium with an ordinary Chrome user agent sent the PageView at once. A test Pixel ID hides the problem, because it has no configuration to filter on. If you check the Gateway with an automated browser, an empty hub may be your test rig, not the Gateway.

How much the Conversions API Gateway costs

Meta charges nothing for the Gateway software. Its documentation says the only cost is “the associated cloud resource or partner fees”. Self-hosting means paying for the compute you provision in your own cloud account. Managed hosting trades that administration for a fixed plan.

Stape’s Gateway page, checked 2026-10-17, lists two plans:

Plan Price Limits
Pay as you go $10 a month per Pixel, or $8 a month billed annually Up to 10 million events per month per Pixel
Unlimited $100 a month, or $83 a month billed annually Up to 100 Pixels, up to 200 million events per month per Pixel

Both plans start with a 7-day free trial. Stape’s older help article on Gateway cost (last updated May 30, 2025) still quotes $100 a year for one Pixel and describes the top plan as unlimited Pixels, so quote the product page and recheck it before sending a client a number.

The rest of the cost is setup time, validation and ownership. For an agency, price the work around the result you can verify. Connecting a Pixel is quick. Auditing event quality, removing duplicate paths, documenting access and reconciling a real outcome are the parts the client is paying for.

Affiliate note: Advanced Tracking Academy is a Stape affiliate and may earn a commission. If Stape is the host you choose, the code MRPV20 takes 20 percent off the first three months.

What the Gateway leaves unsolved

The Gateway can The Gateway cannot
Route an existing Pixel event through a server path Confirm that a real payment went through
Deduplicate the browser and server copies by event name and event ID Stop a duplicate, a test, or a bot that fired the Pixel
Improve matching with hashed customer data Grant consent the visitor never gave
Recover some Pixel events through a first-party server path Send the same event to Google Ads, GA4 or TikTok
Update itself when Meta changes the API Replace backend logic such as webhook validation

If the Pixel fires Purchase on a confirmation page before the payment is captured, the Gateway delivers that premature event more reliably. It is still premature. If a blocker stops the Pixel, the Gateway has nothing to forward. If the business advertises on several platforms, the Meta Gateway does not fan the event out to them.

Consent works the same way. The Gateway carries whatever the Pixel sends, so the Pixel’s consent handling decides what reaches the server route. In a consent test on a client site on 2026-10-09, fbq('consent','revoke') held PageView and Lead, but Meta’s automatic events still sent four SubscribedButtonClick hits. Calling fbq('set','autoConfig',false,PIXEL_ID) before init switches those automatic events off. Test the declined state on the Pixel, again after any change, before you trust the Gateway with it.

The purchase case is covered end to end in the Stripe conversion tracking guide, which shows why a backend confirmation beats a page-load event however well that event is transported.

When the Gateway fits your stack

Choose the Gateway when Meta delivery is the narrow problem, the Pixel source is already sound, and a fast managed setup matters more than custom logic. It suits an advertiser focused on Meta, or an agency that wants data-source management without a direct integration per account, as long as each client keeps its own domain.

Choose a server-side GTM container when the same confirmed event must reach several platforms, when field-level control matters, or when the flow needs backend logic such as webhook validation. Some teams start with the Gateway and add a container later. That works if you decide which system owns each Meta event before both send. The Gateway versus server-side GTM comparison has the decision table, and the Meta Conversions API with GTM guide walks through the container route.

If you want webhook-validated purchases without the Gateway, ATA Edge sends them to Meta’s Conversions API from your own Cloudflare account. The membership includes a library of server GTM containers as a bonus.