Go to the Settings tab of the Activity Manager and you may see this tab in the Transform API…
Now there are two options:
- The conversion API gateway has been around for several years
- Signal gateway
So…What is a signal gateway?
What’s this?
This is how Meta is defined:
Build data pipelines, send data to multiple destinations, and unlock additional features to control how first-party marketing data your business collects.
The API gateway sends web events. The signal gateway is wider and can send multiple types of events to different destinations.
This is a visualization of Stape, one of the third-party integrations you can use.
Signal gateway allows you to send pixels, file uploads, CRM events, and application events to the pipeline filter used for processing. Once processed, it can be sent to your metadata set or elsewhere, such as a large query.
The signal gateway also requires a separate pixel, but you don’t need to set up a new event. I can’t say for sure, but it feels like Meta’s step to push data responsibilities to advertisers and ultimately eliminates the Meta Pixel without compromising attribution.
Should you use it?
If you are currently sending events from multiple sources, consider signal gateway. Setting up this problem is very simple if these separate datasets already exist. Here are a few links that might be helpful:
If you only send web events, you may not need it. It’s not clear whether there is any advantage to using signal gateways only for web events rather than API gateways (I’m using statee for API gateways).
Will you set up a signal gateway?
