How can we help?

[HighLevel] Meta Leads API by Stape

Uliana Lesiv
Uliana Lesiv
  • Updated

Stape developed the Meta Leads API app to help you easily report your Opportunities' progress status as conversion events to your CAPI Gateway, server GTM container, or Signals Gateway.

With this app, you can configure the relevant fields once, and it will automatically monitor the stages of your Opportunities. It will then send the corresponding conversion events to CAPI Gateway, server GTM container, or Signals Gateway, ensuring accurate and efficient tracking of your lead conversions.

 

App installation

Before you start

Make sure you have sub-account on HighLevel

You can find your sub-account on the left-hand side of the panel in the section “Sub-Accounts”.

If the page “Sub-Accounts” is empty, click the “Create Sub-Account” button in the top-right corner → choose account type → choose a snapshot → add your client’s address → “Save”.

 

Installation process

Install Meta Leads API by Stape on the HighLevel’s marketplace.

Select a sub-account you want to install the app on.

 

Select an Account.png

 

Integration methods: CAPI Gateway, Signals Gateway or server GTM

 

 

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

 

App configuration | CAPI Gateway

Before you start

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.

 

add data source.png

 

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

 

Business manager.png

 

 

App setup

The setting process can be divided into two parts:

  • Meta and Stape accounts data
  • HighLevel CRM fields

 

 

Meta and Stape accounts data

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.

If you haven’t set up Meta Conversions API Gateway yet, see the section above.

 

AD_4nXcBYURGVn6qJQKEu5dOGWRKMH96u2r5hPVr--Ky2I9k68eVLCm485ctN6dItFhaQi7Jo6it1IiLd2TzHUyVZdwVszh7um7HLdSzmG6gFUbJygtn0Yf33Jjz.png

 

HighLevel CRM fields

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

- (Optional) Pick a field where Meta Lead ID is stored. Note dropdown will only reflect custom fields.

- 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 stages of your Opportunities, whenever an opportunity reaches a stage you define, a corresponding event will be sent towards your Meta Dataset (Pixel). So we need to configure it by choosing one of two approaches:

  • In the left-side dropdown, select an Opportunity stage to trigger an event. In a box to the right, type the event name you’d like to send to Meta.

 

 

  • Select the ‘Send all stages’ checkbox if you want to send all Opportunity stages as events to Meta. Events are then named automatically and consist of Pipeline + Opportunity stage name. You can also select stages to ignore in this case.

 

 

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.

 

 

App configuration | Signals Gateway

Before you start

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.

 

 

For more detailed instructions, check Stape’s article on how to configure Signals Gateway.

 

App setup

The setting process can be divided into two parts:

  • Signals and Stape accounts data
  • HighLevel CRM fields

 

 

Signals and Stape accounts data

You will need to fill in the following field:

- Signals Gateway Pixel ID - 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.

 

 

 

HighLevel CRM fields

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 stages of your Opportunities, whenever an opportunity reaches a stage 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:

  • In the left-side dropdown, select an Opportunity stage to trigger an event; in a box to the right, type the event name you’d like to send to Signals Gateway pipeline.

 

 

  • Select the ‘Send all stages’ checkbox if you want to send all Opportunity stages as events to Signals Gateway pipeline. Events are then named automatically and consist of an Opportunity stage name. You can also select stages to ignore in this case.

 

 

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.

 

 

App configuration | Server GTM

Before you start

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.

 

Create container.png

 

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

 

For more detailed instructions, check Stape’s article on how to set up a Google Tag Manager server container.

 

App setup

The setting process can be divided into two parts:

- Stape account data
- HighLevel CRM fields

 

 

Stape account data

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.

 

 

HighLevel CRM fields

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 stages of your Opportunities, whenever an opportunity reaches a stage 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:

  • In the left-side dropdown, select an Opportunity stage to trigger an event; in a box to the right, type the event name you’d like to send to server GTM.

 

 

  • Select the ‘Send all stages’ checkbox if you want to send all Opportunity stages as events to server GTM. Events are then named automatically and consist of an Opportunity stage name. You can also select stages to ignore in this case.

 

 

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.

 

  

Settings editing  

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

To do this, go back to settings page via a dedicated item in the side menu or go to “Installed Apps” section of the App Marketplace:

 

27fde0c0-5970-4cf6-93f6-54ad1c1ef9b5.png

 

FAQ

- Is there a subscription involved to use the application?

Application is distributed for free, but you will need a functioning Stape account with active CAPI Gateway, GTM Container or Signals Gateway. It depends on your tracking setup and/or current experience with Stape.

 

- How does the app trigger conversion events?

Application will react to stage changes of your Opportunity entities. Triggers are configured in app settings.

 

- How can I make sure the app actually works?

With CAPI Gateway integration you should see events you’ve configured in your Events Manager. Please note the user interface may take up to 30 min to reflect most recent events sent.

With Signals Gateway integration you should see events you’ve configured in your Signals Gateway Data Source. Please note the user interface may take up to 30 min to reflect most recent events sent.

With server GTM integration the assumed approach for debugging is webhooks. 

 

- Do you provide templates for server GTM integration?
Yes, you can find a pre-built server container template in our GitHub

 

Was this article helpful?

1 out of 1 found this helpful

Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.