How to set up Klaviyo app
Updated Aug 7, 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, ensuring accurate lead conversion tracking. With the app, you can also sync data with Google Ads Customer Match or automatically update Meta Custom Audiences.
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 5 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. |
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.
Customer Match (Google Ads)
It sends CRM audience and contact data directly into Google Ads, where it is used to create and update Customer Lists for targeting and remarketing.
Customer Match is best for users who run Google Ads campaigns and want to build and automate Google Ads audiences based on CRM activity, such as leads, opportunities, and customer lifecycle stages.
Meta Custom Audiences
The method focuses on syncing CRM data to Meta Custom Audiences for retargeting and segmentation. Once configured, it sends data about users who have already interacted with your website or CRM into Meta, so you can target them based on their stage in the customer journey.
Meta Custom Audiences is best for advertisers who want to retarget and re-engage users who have already interacted with their business.
Meta Conversions API Gateway (CAPI Gateway)
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.
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:
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.
Customer Match
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 one. In the main menu, click sGTM → Create container on the top right.
Add your container name, the Container Configuration that you copied from your Google Tag Manager Server Container, and select the 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 setup process can be divided into two parts:
- Stape and Google Ads account data
- Klaviyo CRM fields
Stape and Google Ads account data
You will need to fill in the following fields:
- Integration - switch the Activate toggle on to enable the current integration (tab) to run in the background.
- Container API Key - a string used for app identification. Find the Container API Key in the Container settings section of your Stape account. See the detailed instructions on where to find the Container API Key.
- Google Ads Operating customer ID - the ID of the Google Ads account where the Customer List will be created or updated. To get it, sign in to your Google Ads account → in the top right corner, click on your picture → copy the value.
Please make sure to remove hyphens before using the string as the Operating customer ID.
- Google Ads customer ID - stands for the ID of the account that you're using for authorization. Based on the type of account, you should copy the following values.
- 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.
Klaviyo CRM fields
Next, you need to map your CRM fields to audience member identifiers.
- User data - choose the data you want to fill the Customer List in Google Ads with, and specify user and ads data consent status from the drop-down list.
Please note: Address data will be included only if all four fields (First Name, Last Name, Region, Postal Code) have values.
- Actions & triggers - choose Action, Contact Status, and name a Customer List to be synced to. After configuring Customer Match in the Klaviyo app, a Customer List will be created in Google Ads.
Please note: stape_ is always appended, and the name of the list must always start with "stape_," e.g., stape_klaviyo_purchasers.
- Backfill - if you check this box, the app will sync existing contacts using the settings in the app above. When the unchecked box is selected, it will sync only new contacts that reach the configured statuses. Unchecking later doesn’t remove contacts already synced.
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.
Meta Custom Audiences
If you are using Meta Custom Audiences as a configuration method for the Stape Conversions Tracking Klaviyo CRM app, once configured, you will send data on users who have already interacted with your website to Meta. The platform will use the data to target users based on their specific stage in the customer journey.
Before you start
1. 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, the Container configuration that you copied from your Google Tag Manager Server Container, and select the server location. Click Create Container.
For more detailed instructions, check Stape's article on how to set up a Google Tag Manager server container.
2. Create a custom audience in Meta.
We show how to do it in detail in our guide on Meta Custom Audiences in step 1.
3. Enable the Meta Connection in your Stape admin account.
Open the required container, go to the Connections tab, and click Sign in next to Meta. Use an account that has access to the Meta Ads where you need to update the custom audience.
App setup
The setup process can be divided into two parts:
- Stape account data- Klaviyo CRM fields
Stape account data
You will need to fill in the following fields:
- Integration - switch the Activate toggle on to enable the current integration (tab) to run in the background.
- 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 the Container API Key.
Kalviyo CRM fields
Next, you need to map your CRM fields to audience member identifiers.
- User data - choose the data you want to fill the Custom Audience in Meta with, and specify user and ads data consent status from the drop-down list.
- Triggers & actions - choose Action, Profile Status, and Audience ID to be synced to (the custom audience you’ve created in Meta).
To find Audience ID - go to the Audiences section in Meta Ads, click Columns, enable Audience ID, then copy the ID of the required custom audience once the column appears.
- Backfill - if you check this box, the app will sync existing contacts using the settings in the app above. When the unchecked box is selected, it will sync only new contacts that reach the configured statuses. Unchecking later doesn't remove contacts already synced.
Once done, click Save and Connect. Once you see a success message, your installation is complete, and the application will sync audience members to your Meta custom audience in the background based on your settings.
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.
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 in the top right.
Add a name, email, and server location for the 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 setup process can be divided into two parts:
- Signals and Stape accounts data
- Klaviyo CRM fields
Signals and Stape accounts data
You will need to fill in the following 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.
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