How to configure Signals Gateway

 

In order to set up Signals Gateway please follow these steps:

1. Create Signals Gateway on Stape.
2. Accept invitation link to access your Signals Gateway environment.
3. Set up your login and password.
4. Add data source and data destination in your Signals Gateway environment.
5. Optional: add custom domain.
6. Test your setup. 

 

Detailed step-by-step guide

 

Step 1. Create Signals Gateway on Stape.

 

If you do not have an account yet:

• Click this link.
• Add your email, Gateway name, and select server location. We offer several server locations: the United States, Europe, South America and Asia Pacific.
• Click “Create”.

We will send you an email with the link to set a password to your Stape account. Follow the link from the email to set a password. 

 

If you already have a Stape account:

• Log in.
• Click Signals Gateways in the main menu, and click Create Signals Gateway.
• Then you can add the Signals Gateway instance name and the email address you'd like to use for managing the Gateway environment (it can differ from your Stape login) and select the server location.
• Click “Create gateway”.

Step 2. Choose a subscription plan and finish the setup on Stape.

2.1. Select the Signals Gateway subscription and add your billing details.

Stape offers a free plan, so you can add your billing later. Click the cross at the top right, if you’d like to continue for free.

2.2. You will see the status of your Gateway - “Deploying”. Refresh the page until the status shows “Running”. 

2.3. We will send you an email inviting you to set a password to your Signals Gateway. Check your mailbox and click Accept Invitation.   

Or you can simply click on Finish Signals Gateway setup.

Step 3. Configure Signals Gateway.

3.1. Add the email address indicated in the email admin on the first step and set a password. Stape does not store passwords to Signals Gateway; please save it to a secure place.
Click “Create Account”. 

3.2. You will gain access to your Signals Gateway environment. Click on “Create data pipeline” to proceed. 

3.3. Select the type of pipeline you’d like to create.

Pick the Data pipeline name and select the desired Data sources and Data destinations.

Data sources - inbound events come through data sources associated with websites, apps, and data files.

Data destinations - outbound events data is sent to a pre-selected destination once it’s been processed.

Click “Continue”.

3.5. Set up Signals Gateway Pixel.

Add a name for your new pixel and indicate whether your website has a Meta Pixel.

If you have a Meta dataset that receives events from your website, a Meta Pixel is installed on the website.

In Additional features you can add Custom data source ID. 

If you already have a Signals Gateway Pixel code installed on your website, you can enter its ID here to continue using its pixel code.

3.6. Add Signals Gateway Pixel and events codes. 

Option 1: Share instructions with a web developer.

Simply click on “Copy instructions” and send a message to your developer. 

Option 2: Add Signals Gateway Pixel to a website yourself.

Copy and paste the base code to a website → Configure conversion events on your website by specifying event names and tagging them in your code.

3.7. We, at Stape, would recommend using Google Tag Manager for this task.
Add a Custom HTML Tag → paste your Signals Pixel base code →  give it a trigger and publish.

3.8. Configure Pixel to control how data for this pixel is gathered and processed.

Choose to enable or disable Data enhancement and choose Contact data treatment.

Data enhancement - send advanced matching data with your events.

Contact data treatment - hash contact data upon collection using the SHA-256 format. Data that is hashed cannot be reverted to its original form and cannot be used by some data destinations or for audience creation. 

3.9. After you click “Continue” you will see that you’ve successfully started the setup for your Signals Gateway Pixel. 

3.10. Connect to Meta with Conversions API.

Option 1: connect Meta dataset.

You can use Facebook Login to automatically connect your Signals Gateway to your Meta Business Account.

Or you can Manually connect your Meta Pixel by filling our the fields using the information from the pixel’s dataset in Events Manager. 

Meta Business ID - the unique number used to identify a groupd of Meta business assets, such as ad account, managed by a business.

Dataset ID - the unique number associated with a dataset in Meta Events Manager. The Meta Pixel associated with the dataset will share the same ID. 

Access Token - the code which is generated automatically to help establish a secure connection with your dataset. 

Option 2: select existing Meta dataset from Signals Gateway. 

Step 4. How a finished setup looks like.

On the dashboard, you will see an overview of your Pipeline.

On this stage you can edit: Data sources, Data destinations and set Pipeline filter.

Step 5. Optional: select another data source or edit it.

When you click on your current Data source, you will be able to adjust any settings according to your preferences.

When you click “+” under the “Data sources”, you will be able to automatically or manually add data from files.

Step 6. Optional: edit Pipeline filter.

When you click on Pipeline filter, you will be able to block selected event types from being sent to all of the pipeline’s data destinations. 

Step 7. Optional: select another data destination or edit it.

When you click on your current Data destination, you will be able to adjust any settings according to your preferences.

When you click “+” under the “Data destinations”, you will be able to automatically or manually add data from files.

Step 8. Optional: add new pipelines.

Click on “Data Pipelines” and then on “Create data pipeline”.

Step 9. Optional: add custom domain.

Using a custom domain or data routing within your Signals Gateway can boost measurement performance. 

Click on “Account settings” → “Data routing” → “Optimize“.

Write down the subdomain and domain names. 

Next step will require you to define DNS settings for the custom domain. Ensure you can make changes through the DNS provider before proceeding.

Data destination: Customized connector.

If you want to send events to a unique endpoint, click on “Customized connector” and create a custom destination name.

Type your destination endpoint URL and choose an Authentication method. 

Configure the settings depending on the method. 

Preview your payload and settings.

And it’s done!

Data destination: Google BigQuery.

If you want to send events to Google BigQuery, click on Google BigQuery and create a destination name. 

Fill out the fields to configure your Google BigQuery destination.

Table ID - find it in the Google cloud with the format schema.dataset.table_id.

Service Account Email - enter the email address associated with your Google Cloud service account.

Private Key - enter your Google Cloud service account private key.

Click “Continue” and go to your BigQuery account to ensure data is collected.

Plugins

On the left menu if you click on “Plugins”, you will see Stape CRM Apps. 

Our Meta Leads API apps automatically report your CRM pipeline as conversion events to your Meta Dataset (Pixel). For now, Stape has developed apps for the following CRMs:

• Zoho CRM
• HighLevel CRM
• PipeDrive
• HubSpot