Meta Signals Gateway
Signals Gateway boosted with the edge, the only way of collecting first party
Find it on GitHub: /edgee-cloud/meta-signals-gateway-component
Meta Signals Gateway is a server-side tagging solution that enables you to create data pipelines, perform data processing, and send signals to various destination and advertising platforms (including Meta’s platforms). With Edgee, there’s no need to host Signals Gateway servers on your own infrastructure - this Component works seamlessly with instances that Edgee hosts for you.
Additionally, with Edgee’s edge integration, you can now send these events directly from the edge, significantly improving both reliability and performance.
Getting Started
To integrate Meta CAPI into your Edgee project:
- Open the Edgee console and navigate to your project’s Components.
- Select “Add a component” and choose
edgee/meta-signals-gatewayfrom the list of available components. - Choose your servers location based on the location of most of your clients (
EUorUS). Location can not be changed later. - Click Save
Edgee will create an account for you in our Signals Gateway instance, and you’ll receive an email invitation to join your tenant. Click the link in the email to create your password. Once logged in, you can begin building your pipelines.
To connect Edgee to a Signals Gateway pipeline, you’ll need to create a Meta Pixel and obtain its Pixel ID. For more information about Signals Gateway capabilities, please refer to Meta’s documentation.
After obtaining your Pixel ID, return to your Edgee component and enter it in the designated field.
Data Collection Method
Choose how you want to collect data for this component:
If you select “Edge component” as your data collection method, follow these instructions. If you prefer to use “Javascript SDK”, proceed to this section.
Edge Component Mode
In Edge Component mode, Edgee automatically handles data collection and event forwarding to Signals Gateway, just as it does with other components. This approach provides efficient, fast, and unblockable data transmission.
Edgee seamlessly maps its standard event structures (page, track, user) to the corresponding Signals Gateway event format.
Event Mapping
Here’s how Edgee events map to Meta Signals Gateway events:
| Edgee Event | Meta Signals Gateway Event |
|---|---|
| Page | PageView |
| Track | Name of the event |
| User | Lead |
User Identification
When you make a user call, Edgee securely stores the user’s data (user_id, anonymous_id, and properties) on their device. This ensures proper attribution for all subsequent page views and events.
Component Name
To configure the component in your Edgee Data Layer or SDK calls, use edgee/meta-signals-gateway as the component name.
Javascript SDK Mode
“Javascript SDK” mode allows you to use your Meta Pixel on your site in a fully first-party way, hosted on your main domain. While server-side tagging typically operates behind a subdomain, this unique integration allows Edgee to improve these technologies and make them run at the edge. With this approach, Edgee acts as a proxy to your Signals Gateway tenant and forwards events to it, and you can use the Meta client-side SDK as you would normally do.
Path Prefix
When using Javascript SDK data collection mode, you need to specify a custom path prefix for the Meta Pixel to serve your pixel on your main domain. This helps prevent ad blockers from detecting and blocking the pixel. You can change this value at any time to maintain effectiveness. We automatically generate one for you, but feel free to modify it if needed.
For example, if you choose /foo as a path prefix, all requests coming to www.yourdomain.com/foo/something will be forwarded to your Signals Gateway.
Automatic Meta Pixel Injection
When enabled, the Meta Pixel will be automatically added to your website. If disabled, you’ll need to add the Meta Pixel code to your website manually and handle its initialization based on user consent. This setting only applies when using the ‘JS’ data collection method.
Mode
The mode determines when the Meta Pixel is injected based on the user’s consent.
- Safe: The Meta Pixel will be injected into the website only when the user consent is
granted. - Strong: The Meta Pixel will be injected into the website when the user consent is
pendingorgranted. - Always: The Meta Pixel will be always injected into the website regardless of the user consent state.