How to set up Meta Conversions API for HubSpot CRM with Stape’s app

HubSpot integration with Facebook provides numerous advantages such as reporting Contacts' statuses to Meta Dataset for campaign optimization, offline events tracking, creating automated workflow and other benefits you can check on the solution page.

In this article, we will focus on reviewing how you can configure HubSpot server-side integration with Meta using Stape's app.  We will show you:

1. How to install the app for HubSpot.

2. Which integration method to choose so that it works the best for you.

3. How to complete app installation using the method you've chosen.

4. How to edit settings.

Let's get started!

Install the Stape Conversion Tracking HubSpot app on HubSpot's marketplace.

Choose the account to install the app into:

1.3 Confirm access requested by the app and hit “Connect app”:

You will see the following success screen:

Go back to Hubspot CRM and pick an account you need. Then go to Settings → Integrations → Connected Apps.

On the next page click “Add Settings”:

Integration method depends on your tracking setup and goals, and/or on your current experience with Stape. 

Make sure you have an active Stape account with Meta Conversions API Gateway.

If you don’t have an account on Stape, please create one or log in if you already have. In the main menu click “More Gateways” → “Meta CAPIG” → “Create CAPIG” on the top right.

Add name, email, and server location for new CAPIG. Then, choose the subscription plan and add billing details.

After creating Meta Conversions API Gateway in your Stape account, connect your Meta Dataset (Pixel) - just click "Add data source" → authorize in Meta → select the Business Manager and Dataset (Pixel) you want to connect.

To increase the events match quality, please enable “Automatic advanced matching”.

The setting process can be divided into two parts:

- Meta and Stape accounts data

- HubSpot CRM fields

You will need to fill in the following field:

- Meta Dataset (Pixel) ID - unique identifier that is used to configure integrations and view events in Events Manager. You can find it in your Meta account in Data Sources’ “Settings” tab. See the detailed instruction on how to find Meta Dataset (Pixel) ID here.

- CAPIG API Key - alphanumeric string value that is needed for app identification. Find CAPIG API Key in the CAPIG settings section of your Stape account. See the detailed instructions on where to find CAPIG API Key here.

Next you need to map your CRM fields to conversion event parameters.

- (Optional) Pick a field where Meta Lead ID is stored.

- Configure additional User data you’d like to send to Meta, by choosing a parameter in the left dropdown and selecting an appropriate field in the right-side one.

- Application sends conversion Events based on statuses of your Contacts, whenever a deal reaches a status you define, a corresponding event will be sent towards your Meta Dataset (Facebook Pixel). So we need to configure it by choosing one of two approaches:

Once done, click “Save and Connect”. Once you see a success message your installation is complete and the application will send conversion events in the background based on your settings.

Make sure you have an active Stape account with Signals Gateway.

If you don’t have an account on Stape, please create one or log in if you already have. In the main menu click “Signals Gateway” → “Create Signals Gateway” on the top right.

Add name, email, and server location for new Signals Gateway. Then, choose the subscription plan.

The setting process can be divided into two parts:

- Signals and Stape accounts data

- HubSpot CRM fields 

You will need to fill in the following field:

- Signals Gateway Pixel - unique identifier that is used to configure integrations and view events in Signals Gateway. You can find it in your Signals Gateway account in the Data Sources tab. See the detailed instruction on how to find Signals Gateway Pixel ID here.

- Signals Gateway API Key - alphanumeric string value that is needed for app identification. Find Signals Gateway API Key in the Gateway settings section of your Stape account. See the detailed instructions on where to find Signals Gateway API Key here.

Next you need to map your CRM fields to conversion event parameters.

- (Optional) Pick a field where Meta Lead ID is stored.

- Configure additional User data you’d like to send to Signals Gateway, by choosing a parameter in the left dropdown and selecting an appropriate field in the right-side one.

- Application sends conversion Events based on statuses of your Contacts, whenever a deal reaches a status you define, a corresponding event will be sent towards your Signals Gateway Pixel. So we need to configure it by choosing one of two approaches:

Once done, click “Save and Connect”. Once you see a success message your setup is complete and the application will send conversion events in the background based on your settings.

Make sure you have an active Stape account with a server GTM container hosted on Stape.

If you don’t have an account on Stape, please create one or log in if you already have. In the main menu click “sGTM” → “Create container” on the top right.

Add your container name, Container Configuration that you copied from your Google Tag Manager Server Container, and select server location. Click Create Container.

The setting process can be divided into two parts:

- Stape accounts data

- HubSpot CRM fields

You will need to fill in the following field:

- Container API Key - alphanumeric string value that is needed for app identification. Find Container API Key in the Container settings section of your Stape account. See the detailed instructions on where to find Container API Key here.

Next you need to map your CRM fields to conversion event parameters.

- (Optional) Pick a field where Meta Lead ID is stored.

- Configure additional User data you’d like to send to server GTM, by choosing a parameter in the left dropdown and selecting an appropriate field in the right-side one.

- Application sends conversion Events based on statuses of your Contacts, whenever a deal reaches a status you define, a corresponding event will be sent towards your server GTM container. So we need to configure it by choosing one of two approaches:

Once done, click “Save and Connect”. Once you see a success message your installation is complete and the application will send conversion events in the background based on your settings.

If you are using Customer Match as a configuration method for the Stape Conversion Tracking HubSpot app, once configured, a new Customer List will be created in Google Ads. Please note, only Customer Lists created automatically by the Stape connection are supported.

Manually created or pre-existing lists in Google Ads will not be populated. For more info on Customer List, please check our article.

Make sure you have an active Stape account with a server GTM container hosted on Stape.

If you don’t have an account on Stape, please create one or log in if you already have one. In the main menu, click “sGTM” → “Create container” on the top right.

Add your container name, Container Configuration that you copied from your Google Tag Manager Server Container, and select the server location. Click Create Container.

The setting process can be divided into two parts:

- Stape and Google Ads accounts data

- HubSpot CRM fields

You will need to fill in the following field:

- Container API Key - a string used for app identification. Find Container API Key in the Container settings section of your Stape account. See the detailed instructions on where to find Container API Key here.

Please make sure to remove hyphens before using the string as the Operating customer ID.

- If you’re using your customer account, use the customer account ID.

- If you access the customer account through a manager account, use the manager account ID.

Please make sure to remove hyphens before using the string as the customer ID.

Next, you need to map your CRM fields to audience member identifiers.

Please note: Address data will be included only if all four fields (First Name, Last Name, Region, Postal Code) have values.

Please note: stape_ is always appended, and the name of the list must always start with “stape_”, e.g., “stape_hubspot_purchasers”.

Once done, click “Save and Connect”. Once you see a success message, your installation is complete, and the application will send conversion events in the background based on your settings.

If you have some changes in the funnel or you want to change the events sent to your CAPI Gateway, server GTM container, or Signals Gateway, you can always edit your app configuration.

To do this, go to Settings → Integrations → Connected Apps and follow the steps from section 1 of this manual.

Using the Meta (Facebook) Conversions API for HubSpot CRM is a convenient and easy way to configure sending data on Contacts’ statuses from HubSpot to your Meta CAPI Gateway, server GTM container, or Signals Gateway. To start using the app you need to have the Stape account and connect Meta Conversions API Gateway. Start with a free trial to see how the HubSpot integration can boost the performance of Facebook Lead Ads!