Two gateways, one lineage
CAPI Gateway arrived first: a self-hosted package that receives your web events and forwards them to Meta’s Conversions API, deployed in your own cloud account with minimal configuration. Signals Gateway is the newer, broader offering: self-hosted first-party signal infrastructure that collects events on your domain and processes them before delivery. Think of CAPI Gateway as a dedicated pipe and Signals Gateway as a hub you operate.
Where they differ
Scope is the main line. CAPI Gateway does one job, moving web events to Meta CAPI, and does it simply. Signals Gateway takes on more of the collection layer itself: first-party event capture on your subdomain, processing controls, and room for signal types beyond the classic web pixel event. With the broader scope comes more surface to configure and operate. Both run in your cloud, on your bill, under your team’s monitoring.
What they share
Both are Meta infrastructure for Meta outcomes. Both improve signal durability by moving collection to a domain you control. And both leave every other ad platform unsolved: your Google, Snap, TikTok, and LinkedIn signal still needs its own answer. For a single-platform advertiser with an infrastructure team, that trade can be fine. For a multi-platform advertiser it means running Meta’s stack and still needing a plan for everyone else.
How Datahash fits
Datahash supports both paths. If self-hosted is a requirement, we deploy and manage Meta gateway infrastructure on your own subdomain, so you get the ownership without the pager duty. If the goal is every platform from one integration, Signals delivers deduplicated, hashed events to Meta and every other major platform from a single setup that is live in about 15 minutes. The right answer depends on your compliance posture and how much infrastructure you want to own.