Stape
Search
Try for free

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

Updated
Feb 17, 2025
Published
Oct 30, 2024

Reporting lead statuses back to your Meta CAPI Gateway, server GTM container, or Signals Gateway from CRM may be overlooked, but it is still essential for optimizing campaigns and improving Facebook conversions. This way, you can enrich Meta with data about your leads' behavior after the first interaction with the ad. Based on this information, the Meta platform will optimize the audience to which they show the ad, improving the quality of leads.

Configuring such data sending to Meta CAPI Gateway, server GTM container, or Signals Gateway may be challenging and require additional technical skills. Still, the Meta Conversions API for Pipedrive makes it much more manageable.

What is the Meta Conversions API for Pipedrive?

The Meta Conversions API for Pipedrive is the method used to set up sending data from CRM to Facebook. To implement such a setup, you can use an app developed by Stape. It tracks Deals' progress and sends the data as conversion events from PipeDrive to the Meta Dataset (Pixel). The app provides seamless integration with existing CRM workflows and precise data tracking as the conversions are tracked on the server side.

The advantages of seamless integration of Pipedrive with Meta Conversions API

Convenient tracking of Deals' progress

Streamline reporting of Deals’ statuses as conversion events to your Meta Dataset (Pixel). With Pipedrive integration in place, the progress of your Deals is automatically sent as conversion events, ensuring accurate and efficient conversion tracking.

Leads quality improvement

Sharing your Deal status information with Meta allows the platform to analyze which ads perform best for different audiences, optimizing ad targeting. This leads to higher-quality leads and an increase in transactions.

Offline and online action tracking

While Facebook Pixel can track only the events that happen online, tracking offline actions can be necessary for some businesses. With the help of the Meta Conversions API for Pipedrive, you can easily set up such integration - once the events appear in your CRM, they will be sent as conversions to your Meta CAPI Gateway, server GTM container, or Signals Gateway.

How to configure Meta Conversions API for Pipedrive CRM

App installation

Install Meta Leads API by Stape by following this link.

Give the app the scopes it requires:

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.

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

App setup

The setting process can be divided into two parts:

  • Meta and Stape accounts data
  • PipeDrive 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.

PipeDrive 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 Deals, whenever a deal 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 a Deal 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 statuses’ checkbox if you want to send all Deal stages as events to Meta. Events are then named automatically and consist of Pipeline + Deals stage name. You can also select statuses 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

- PipeDrive CRM fields

Signals and Stape accounts data

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.

PipeDrive 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 Deals, whenever a deal 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 a Deal 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 statuses’ checkbox if you want to send all Deals stages as events to the Signals Gateway pipeline. Events are then named automatically and consist of a Deal stage name. You can also select statuses 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.

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

App setup

The setting process can be divided into two parts:

- Stape account data

- PipeDrive 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 Deals, whenever a deal 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 a Deal 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 statuses’ checkbox if you want to send all Deals stages as events to server GTM. Events are then named automatically and consist of a Deal 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 your 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 puzzle icon (My apps) in your header menu, pick “Meta Leads API by Stape” and either just click on it or select settings from a contextual menu:

To sum up

The Meta Conversions API for Pipedrive offers a simple and convenient way to send Deals’ status data from Pipedrive to your Meta CAPI Gateway, server GTM container, or Signals Gateway. To get started, you'll need a Stape account and to connect the Meta Conversions API Gateway.

With just a few steps, you can enhance the performance of your Facebook Lead Ads!

Comments

Try Stape for all things server-sideright now!