[Klaviyo] Stape Conversion Tracking App
Updated Jun 26, 2026
Stape created the Conversion Tracking app to simplify the process of reporting your users' progress as conversion events to your CAPI Gateway, Signals Gateway, or server GTM container.
Once configured, the app monitors the user's interactions. It automatically sends the appropriate conversion events to your chosen destination (CAPI Gateway, Signals Gateway, or server GTM container), ensuring accurate lead conversion tracking.
App installation
Get the Stape Conversion Tracking app by following the link on the Klaviyo platform and click Install.
To proceed, you need to have a Stape account and use it during the installation.
If you don't have a Stape account yet, create a free account.
Give the app the scopes it requires:
Integration methods and their differences
The Klaviyo CRM app by Stape provides 3 different integration methods for sending profiles' progress status to your marketing platforms.
| Note: you can configure multiple tabs/methods; each one runs on its own. |
Meta Conversions API Gateway (CAPIG)
This integration is built for Meta platforms such as Facebook and Instagram. It sends CRM event data directly to the Meta Conversions API.
Meta CAPIG is best for users who only need to track offline conversions and events in Meta. It is the most direct and simplest way to connect CRM data to Meta, but it is limited to Meta's ecosystem.
Signals Gateway
Signals Gateway is the unified routing solution. Instead of sending data separately to each platform, you send it once to Stape and then distribute it to multiple destinations.
Signals Gateway is best for users who, besides Meta, want to connect a few other platforms and look for a balance between simplicity and flexibility. Signals Gateway is more powerful than CAPIG (as it provides the option to add other platforms), and easier to configure than server-side GTM.
Server Google Tag Manager (sGTM)
This method integrates directly with your server-side Google Tag Manager container. It gives you full control over how data is processed and routed.
Server GTM is best for tracking setups that require custom logic or integrations with other platforms that Signals Gateway doesn't provide. It offers the highest level of customization and control, but requires more technical setup and ongoing management.
Configure the app based on the configuration method
❗Please note before starting: Stape's app supports multiple integrations simultaneously. Each integration method has its own tab with an Activate integration toggle; switch it on for the integrations you want to send data to.
The integration method depends on your tracking setup and goals, and/or on your current experience with Stape. Click on the section below that corresponds to the tracking method you use:
CAPI Gateway
Before starting
You will need to have an active Stape account with the Meta Conversions API Gateway installed.
Create a Stape account or log in if you already have one. In the main menu, click More Gateways → Meta CAPIG → Create CAPIG on the top right if you need to add Meta CAPIG.
Enter the name, email, and server location for the new CAPIG. Next, select a subscription plan and provide billing information.
Once the Meta Conversions API Gateway is created in your Stape account, connect your Meta Dataset (Pixel) by clicking Add data source → log in to Meta → choose Business Manager, and the Dataset (Pixel) you want to link.
To improve event match quality, please enable Automatic Advanced Matching.
For the detailed instructions on how to set up Meta CAPI Gateway, please check Stape's guide.
App setup
The app configuration process can be divided into two parts:
- Meta and Stape accounts data
- Klaviyo related fields
Meta and Stape accounts data
Fill the fields:
- Integration - switch Activate toggler on to enable the current integration (tab) to run in the background.
- Meta Dataset ID - unique identifier used to set up integrations and monitor events in Events Manager. You can find it in your Facebook Business Manager in the All tools menu section → Event Manager → Data Sources. For step-by-step instructions on how to find your Meta Dataset (Pixel) ID, check Stape's guide.
- CAPIG API Key - an alphanumeric string used to identify your app. It can be found in the CAPIG settings section of your Stape account. For detailed instructions on how to find your CAPIG API Key, see Stape's article.
Klaviyo-related fields
Map your Klaviyo CRM fields to the conversion event parameters.
- (Optional) Select the field where the Meta Lead ID is stored. Note: the dropdown will only display custom fields.
- To send additional user data to Meta, choose a parameter from the left dropdown and match it with the corresponding CRM field using the right dropdown.
- The application sends conversion events based on the user's interactions. Whenever a user performs a specified action, a corresponding event is triggered and sent to your Meta Dataset (Pixel). To set this up, choose one of the following configuration methods:
- In the left dropdown, select the user action that should trigger the event. Then, in the box on the right, enter the event name you want to send to Meta.
- Enable Send all stages if you want to send all user interactions as events to Meta. In this case, events will be automatically named using the status names. You can also choose specific statuses to exclude from being sent.
When you've finished the configuration, click Save and Connect. After the success message appears, the installation is complete, and the application will begin sending conversion events in the background according to your configured settings.
Signals Gateway
Before starting
You will need to have an active Stape account with the Signals Gateway installed.
Create a Stape account or log in if you already have one. In the main menu, click Signals Gateways → Create Signals Gateway on the top right if you need to create a Signals Gateway.
Enter the name, email, and server location for the new Signals Gateway. Next, select a subscription plan and provide billing information.
For the detailed instructions on how to configure Signals Gateway, check Stape's article.
App setup
The app configuration process can be divided into two parts:
- Signals and Stape accounts data
- Klaviyo related fields
Signals and Stape accounts data
You'll need to fill the following fields:
- Integration – turn on the Activate toggle to allow the current integration (tab) to run in the background.
- Signals Gateway Pixel – a unique identifier used to set up integrations and track events within Signals Gateway. You can find it in your Signals Gateway account under the Data Sources tab. For detailed instructions on finding the Pixel ID, check the quick guide on Signals Gateway Pixel ID.
- Signals Gateway API Key – an alphanumeric string required to identify your app. This can be found in the Gateway settings section of your Stape account. Click here for step-by-step instructions on where to find your Gateway API Key.
Klaviyo-related fields
Map your Klaviyo CRM fields to the conversion event parameters.
- (Optional) Select the field where the Meta Lead ID is stored. Note: the dropdown will only display custom fields.
- To send additional user data to Meta, choose a parameter from the left dropdown and match it with the corresponding CRM field using the right dropdown.
- The application sends conversion events based on the user's interactions. Whenever a user performs a specified action, a corresponding event is triggered and sent to your Signals Gateway. To set this up, choose one of the following configuration methods:
- In the left dropdown, select the user action that should trigger the event. Then, in the box on the right, enter the event name you want to send to Meta.
- Enable Send all stages if you want to send all user interactions as events to Meta. In this case, events will be automatically named using the status names. You can also choose specific statuses to exclude from being sent.
When you've finished the configuration, click Save and Connect. After the success message appears, the installation is complete, and the application will begin sending conversion events in the background according to your configured settings.
Server GTM
Before starting
You will need to have an active Stape account with a server GTM container hosted on Stape.
Create a Stape account or log in if you already have one. In the main menu, click sGTM → Create container on the top right.
Add your container name, paste the Container Configuration you copied from your Google Tag Manager Server container, and choose a server location. Then, click Create Container.
For a step-by-step guide, check Stape's article on setting up a Google Tag Manager server container.
App set up
The app configuration process can be divided into two parts:
- Stape account data
- Klaviyo-related fields
Stape account data
Fill in the following fields:
- Integration – turn on the Activate toggle to allow the current integration (tab) to run in the background.
- Container API Key – an alphanumeric string used to identify your app. You can find the Container API Key in the Container Settings section of your Stape account. For step-by-step guidance, check the detailed instructions on how to find the Container API Key.
Klaviyo-related fields
Map your Klaviyo CRM fields to the conversion event parameters.
- (Optional) Select the field where the Meta Lead ID is stored. Note: the dropdown will only display custom fields.
- To send additional user data to Meta, choose a parameter from the left dropdown and match it with the corresponding CRM field using the right dropdown.
- The application sends conversion events based on the user's interactions. Whenever a user performs a specified action, a corresponding event is triggered and sent to your server GTM container. To set this up, choose one of the following configuration methods:
- In the left dropdown, select the user action that should trigger the event. Then, in the box on the right, enter the event name you want to send to Meta.
- Enable Send all stages if you want to send all user interactions as events to Meta. In this case, events will be automatically named using the status names. You can also choose specific statuses to exclude from being sent.
When you've finished the configuration, click Save and Connect. After the success message appears, the installation is complete, and the application will begin sending conversion events in the background according to your configured settings.
Configure sending data to the required platforms
With the current setup, the app will send events to your server GTM container, but to distribute them to platforms like Meta, TikTok, Google Ads, or any other, you need to configure the CAPI tags inside GTM to fire accordingly.
1. Configure the Data Client to claim the JSON requests sent from the CRM app. Go to the Templates → click New → upload the Data Client template you've previously downloaded from GitHub.
2. Go to the Clients section of your sGTM container → click New → select Data Client. That's basically it, your configuration will look like in the screenshot below. Click Save.
2. Select the platforms you need to send data to from sGTM. While setting up server-side tracking with sGTM, you might have already configured the CAPI tags for the required platforms, for example:
Or any other tags for platforms that support server-side tracking. You will need to use them to configure sending data from your CRM to the required platforms.
To give you an understanding of how to configure the tags this way, we will take the Facebook platform as an example. You should map the events according to the requirements of the platforms you use.
4. Create a new Facebook CAPI tag. Go to the Tags section in sGTM → add Facebook Conversion API as tag type.
5. Configure the tag.
Event Name Setup Method: Override
- Event Type: Custom. Select a built-in variable "Event name."
- Action Source: System Generated.
- Add Pixel ID and generate API Access Token: for the detailed instructions on how to find these values, please refer to our guide on where to find Meta Pixel ID and API Token.
Here is an example of how your configuration will look at this point:
- User data section: select properties from the drop-down list - Lead ID, Browser ID, Click ID. These three are basic.
For each property, add a variable that will take the appropriate value from the request sent from the CRM app.
Create a following variable for Lead ID:
- Variable Type: Event Data
- Key Path: lead_id
Create two different variables for Browser ID and Click ID:
- Variable Type: Event Data (for both), as the IDs will be retrieved from the event sent from CRM, not from the cookie.
- Cookie Name: fbp (for Browser ID variable) and fbc (for Click ID variable)
Here is an example of the user data section configuration:
- Custom data section: add a few custom fields to identify the source of the event.
Event_source property name with crm value.
lead_event_source - as property value, add a variable with the following configurations:
- Variable Type: Event Data
- Key Path: lead_event_source
Here is how this configuration will look like in the tag:
6. Add a trigger for a tag.
Use the following configurations:
- Trigger type: Custom
- This trigger fires on: Some events
Besides, add the following conditions for a tag to trigger:
- Client Name equals Data Client
- Action Source equals system_generated
The variable for action source must have configurations as on the screenshot below:
- Event Source equals crm
Configure the variable for the event source as shown in the screenshot:
As a result, your trigger will look similar to the example from the screenshot below:
7. Test the setup.
Since it is, in fact, a webhook that is sent from CRM to the server GTM, you can refer to the article on debugging incoming webhooks in server GTM for the detailed instructions.
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 to Integrations in your Klaviyo account → click three dots next to Stape Conversion Tracking → click Edit integration → click Go to Stape Conversion Tracking.
Was this article helpful?
Comments