pixellint

Blog · Signals Gateway

Meta CAPI Gateway only forwards the Pixel. Signals Gateway is the hub. Mixing them is a silent Meta-only pipe.

· 10 min read

Meta shipped two gateway products on the same style of cloud box. Conversions API Gateway takes the Pixel and forwards it to Meta CAPI. Signals Gateway is the hub: pipelines, more sources, BigQuery, custom HTTPS. The first install most stacks will click in Events Manager is CAPI Gateway. That box does not become a multi-vendor CAPI because the admin URL also says /hub/capig.

The install looks the same. You bring AWS or GCP. You get a host in your account. The Pixel starts sending a second copy to your origin. The UI lives at /hub/capig. CAPI Gateway's job, in Meta's own first-release notes, is to forward conversion events from Meta Pixel to Conversions API endpoints on Facebook. Signals Gateway's job is sources to destinations, including Meta as one plugin. Mixing the names is how a TikTok Events API never sees the purchase and Events Manager still looks redundant.

A Gateway that only talks to Meta is a Meta-only pipe. It can be a good Meta-only pipe: no code, auto event_id, pixel plus CAPI on the same dataset. It is not server-side tagging for every ads account you run. That is the news, not a new validator feature.

CAPI Gateway is Pixel-in, Graph-out

Conversions API Gateway is a self-serve option in Events Manager. Meta's page, updated April 30, 2026, still describes it as Pixel plus CAPI in a redundant setup, no dedicated developers, no coding. Speed, cloud cost instead of an integration project, low technical lift, auto updates with host admin consent. Provisioning needs a non-Meta cloud account. The product runs on AWS EKS, AWS ECS Express, or GCP, inside a cloud account the business owns.

Two modules: middleware that receives browser events, transforms them to Conversions API events, and sends them to Meta; and an admin portal. The Pixel JavaScript sends to Meta and to the Gateway over HTTPS every time it fires. event_id is automatically generated and propagated for dedup between both channels. Multiple domains can sit on one instance. Multiple Meta Pixels can too.

The admin UI is https://<your-endpoint>/hub/capig. Connected pixels: open and close connections. Event activity: volume Meta received from pixel and from the Gateway. Conversions API success rate: share of browser events published to Meta. Notifications for software updates. That UI is a Meta health dashboard. It is not a pipeline catalog. If the only destination you can see is Meta, you installed CAPI Gateway, or you installed Signals Gateway and only enabled the Meta plugin.

Signals Gateway is sources, pipelines, destinations

Signals Gateway, page updated December 11, 2025, is a product in your cloud that collects, processes, and transmits first-party data to desired destinations. Meta's changelog introduction is the clean sentence: no pre-defined data purpose. Data pipelines incorporate multiple data sources and destinations. Collection tools include Signals Gateway Pixel and Signals Gateway SDK. Destinations in the architecture diagram are custom domain POST HTTPS, Google BigQuery, and Meta Conversions API. The admin UI is still /hub/capig, which is how the names collapse in Slack.

Pipeline management has two tabs: Signals Gateway data pipelines, and Meta Conversions API data pipelines. Creating a Signals Gateway pipeline that sends to Meta requires enabling the corresponding plugin. Plugins documented on the plugins page: Meta Conversions API plugin, and Google BigQuery plugin. Changelog also describes Custom HTTPS Destination with basic auth, OAuth, or an API key. The Meta plugin is governed by Meta's Business Tool Terms. BigQuery is analytics. Custom HTTPS is the hook people think they can point at Snap or TikTok. A custom HTTPS POST is not automatically a valid TikTok Events API body.

Sources on the architecture diagram are browser events, app events, events file upload, and custom HTTP server events. File-based sources showed up in a later changelog as a pipeline option. That is a wider ingest than CAPI Gateway's Pixel-in path. It is still not 'one JSON for every vendor.' The transformation to Meta CAPI happens when Meta is the destination. The transformation to BigQuery is a table. Neither step emits Pinterest's event_time or OpenAI's timestamp_ms unless you built that mapping yourself on custom HTTPS.

v2.3.0 is still not a Snap CAPI

The latest shared version on the changelog I fetched is v2.3.0, dated September 11, 2025. Signals Gateway Pixel partner-based onboarding during setup, including Google Tag Manager, plus a GTM setup guide. Pagination and search for data sources, destinations, and pipelines. Custom conversions and website custom audiences in Signals Gateway, with matching and enrichment through Events Manager rules, then forward matched events to the Conversions API. That last feature is still a Meta Events Manager loop. It is not custom conversions on Google Ads.

v2.2.0, May 15, 2025 in Meta's own topic notes, added Enhance Events, partner instance setup from the Signals Gateway microsite, GCP setup, and custom destination updates for major providers. I am quoting the changelog's feature bullets, not a lift percentage. Enhance Events enriches with additional possible user data. That is a Meta match-key story when the destination is CAPI. It does not hash emails for Reddit.

CAPI Gateway's first public version is still the right one-line definition: deploy to Amazon AWS cloud and forward conversion events from Meta Pixel to Conversions API endpoints on Facebook. Later CAPI Gateway releases added multi-pixel onboarding from Events Manager, App Runner, Cloudflare domains, Enhance events with advanced matching, batch CSV upload, a server endpoint for non-web events, automatic updates. Those are Meta-pipe features. They are not Signals Gateway pipelines. Installing CAPI Gateway from Events Manager pre-populates the pixel. That convenience is how teams never see the Signals Gateway pipeline tab.

The pipeline people will name first

A CAPI Gateway-shaped path labeled as multi-vendor. The only destination is Meta.

{
  "name": "multi_vendor_capi",
  "source": "meta_pixel",
  "destinations": ["meta_conversions_api"]
}

That config is a legal Meta redundant setup. The Pixel fires, the Gateway transforms browser events to CAPI, Graph gets the event, event_id dedupes. TikTok, Snap, Nextdoor, and OpenAI never see it. Success rate in /hub/capig can be 100 percent. The other ads accounts stay on the browser pixel Safari already blocks.

If you actually wanted the hub, you need Signals Gateway, the pipeline tab that is not the Meta CAPI Gateway tab, plugins enabled for BigQuery and custom HTTPS, and then a real mapping on the custom endpoint. GTM partner onboarding in v2.3.0 is how the Signals Pixel gets onto the page. It is not a tag that emits every vendor's CAPI dialect. The Meta CAPI pack still lints Graph. It does not lint a custom HTTPS body you pointed at another host.

Names that do not translate

Same cloud, different contract

The Gateway Products overview says they share components and infrastructure. Server application receives, transforms, and sends depending on pipeline type. Web UI to administer the instance. That shared foundation is why procurement hears one SKU. The CAPI Gateway page never lists BigQuery. The Signals Gateway page never says its only job is Facebook. If your runbook says 'we installed the Gateway, we have CAPI,' ask which product, which pipeline tab, and which destinations are enabled.

Pixel plus CAPI on Meta remains the right Meta architecture: browser event plus server event, same event_id. CAPI Gateway automates that for Meta without a worker. Signals Gateway can feed that Meta destination and also land a warehouse copy. Neither product is a license to POST Graph JSON to bzr.openai.com or ads.nextdoor.com. The silent failure mode is the Meta-only box with a hub name.

Cost is cloud resources or partner fees. I do not have a dollar figure from Meta and will not invent one. Auto update with consent is how the box picks up v2.3.0. It will not grow a Snap destination while you sleep.

How to tell which box you have

If the UI offers connected pixels, event activity from pixel and CAPI Gateway, and a Conversions API success rate to Meta, you are on CAPI Gateway. If the UI offers pipelines with sources and destinations, and plugins for BigQuery or custom HTTPS, you are on Signals Gateway. If you have both tabs, look at which pipelines actually emit. A Meta Conversions API data pipeline is still Meta.

Events Manager onboarding that pre-selects the pixel is the CAPI Gateway convenience path. Signals Gateway can also be onboarded from Events Manager in later versions. Read the destination list, not the product headline.

This version of Conversions API Gateway allows you to deploy a service environment to your Amazon AWS cloud that will allow you to forward conversion events from Meta Pixel to Conversions API endpoints on Facebook.

Meta Gateway products changelog, first CAPI Gateway release

What to do

If you need Meta pixel plus CAPI with no worker, CAPI Gateway on AWS or GCP is the product Meta documented for that. If you need a hub, Signals Gateway with pipelines, and you still map each ads vendor yourself. Persist Meta event_id as Meta's id. Do not reuse it as the only key on a custom HTTPS fanout.

Do not rename a Meta-only Gateway to multi-vendor CAPI. Lint the Meta body with the Meta pack. Lint any custom HTTPS body against the actual vendor. v2.3.0 GTM onboarding is a Signals Pixel setup path, not a dialect translator.

This post is the market fact: CAPI Gateway only forwards the Pixel, Signals Gateway is the hub, and mixing them is a silent Meta-only pipe. Pixellint is not affiliated with Meta. Passing a linter means the artifact matches a published envelope. It does not mean Events Manager attributed the order, and it does not detect fraud.

Checklist

Sources

Contract pages

The dated argument is above. These pages are the field lists.

Open the Meta CAPI pack Docs