What is Meta Signals Gateway¶
Meta Signals Gateway is a managed, cloud‑hosted data pipeline for first‑party marketing signals. It centralizes multiple inbound sources (web pixel, app/SDK, CRM and file uploads) and lets you process and forward events to one or more outbound destinations such as Meta (via Conversions API), Google BigQuery, or a custom HTTP endpoint.
Signals Gateway doesn’t require technical resources or coding. It's an easy to use yet powerful server‑side tracking platform that lets customers preserve control over what is collected and where it goes.
Usercentrics makes it easy to host a Signals Gateway instance.
What you can do with Signals Gateway¶
The functionality of Signals Gateway can be grouped into three broad functions you can do with data.
| Function | Description |
|---|---|
| Collect | Collect data from one or more sources like browser events captured by the Signals Gateway Pixel, mobile app events captured by Signals Gateway SDK, offline conversions from CRMs and point-of-sale systems through manual or automated file uploads. |
| Process | Apply basic filtering and enrichment (e.g., hashing contact fields, advanced matching) before dispatch. |
| Distribute | Stream the same standardized events to multiple destinations: Meta datasets, BigQuery, Custom destinations, Audiences |
What is the Signals Gateway Pixel and how is it different from the classic Facebook/Meta Pixel?¶
The classic Facebook/Meta Pixel is a code snippet integrated into your website that collects events happening on the page and sends them to Meta’s platform. The code is loaded from Meta, which means it’s coming from a third-party source. Some years ago, Meta also created the Conversions API Gateway (CAPI Gateway), which allowed businesses to connect their pre-existing pixels with the Conversions API. This allowed advertisers to improve their data volume and quality, by sending data to a first-party server in parallel to Meta.
Recently, Meta launched Signals Gateway: an updated and future-proof version of the CAPI Gateway. It has the same functionality, and much more. Most importantly, it allows advertisers to generate a new kind of pixel, called the Signals Gateway Pixel. Like the classic Meta Pixel, it’s a code snippet that integrates with the website. However, it has two key distinctions:
-
The script code is served from a sub-domain of the website: this makes it first-party and more resilient to ad blockers than the traditional Meta/Facebook pixel, which in turn means there will be more data volume with better quality, thus improving CPAs and EMQ scores;
-
The code communicates only to the gateway, not directly to Meta — the gateway then forwards events to the chose destinations. This means the business is in control of the data that gets sent.
Typical architectures¶
Signals Gateway can be deployed in multiple ways.
Most Common¶
The most common and easy to setup scenario is to generate the first-party Signals Gateway pixel and send data to a Meta dataset.
Advanced¶
More advanced scenarios involve combining multiple data sources, filters, and sending data to more than one destinations. This consolidates first‑party data collection and minimizes vendor‑specific code on the site.
