Signals Gateway is a powerful data management solution that allows you to centralize, process, and route data from various sources to your desired destinations.
Currently, the following data sources are supported:
• Signals Gateway Pixel — captures website events, ensuring high-quality data collection.
• Automated and manual upload — lets you upload offline data to the cloud on a scheduled basis (from an AWS S3 bucket) or manually.
• Server-side event forwarding — send events directly to a specific endpoint.
Signals Gateway offers flexible data routing. Supported destinations include:
• Any destination — send data to internal systems, ad networks, analytics platforms, or data warehouses through custom connectors.
• Google BigQuery (via the Google BigQuery plugin) — integration for detailed data analysis in Google’s data warehouse.
• Meta (via the Conversions API plugin) — send data to Meta via the Conversions API (CAPI) with granular control over what data gets shared.
It’s important to note the differences between Signals Gateway and Meta Conversions API. Signals Gateway is a cloud-based platform with its own data sources, like the Signals Gateway pixel, automated uploads, and CRM integrations (via partners). It transmits data directly to your cloud instance. Meta will only access this data if you enable transmission via the Conversions API connector.
There are several options for setting up Signals Gateway:
Partner-hosted
• Stape (cheers!)
• Madgicx
• Datahash
Self-hosted
• AWS EKS
•AWS App Runner
• GCP
Additionally, you can integrate with two plugins — Meta Conversions API and Google BigQuery (to send events to a specific dataset). Custom domains and CDNs are also supported.
If you work with GA4 to BigQuery exports, be sure to check out my SQL cheat sheet.
