[Klaviyo] Stape Conversion Tracking App

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

Install the Stape Conversion Tracking app by following the link on the Klaviyo platform.

Give the app the scopes it requires:

Integration methods: CAPI Gateway, Signals Gateway, or server GTM

You can select the method you currently use or would like to install:

• If you would like to integrate the Stape Conversion Tracking app with CAPI Gateway, please follow these steps.
• If you would like to integrate the Stape Conversion Tracking app with Signals Gateway, please follow these steps.
• If you would like to integrate the Stape Conversion Tracking app with the server GTM, please follow these steps.

App configuration | 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.”

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:

• 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.

Klavio-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 statuses” if you want to send all user interactions as events to Meta. In this case, events will be automatically named using the Pipeline and user stage 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.

App configuration | 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 CAPIG. Next, select a subscription plan and provide billing information.

App setup

The app configuration process can be divided into two parts:

• Signals and Stape accounts data
• Klaviyo relanted fields

Signals and Stape accounts data

You’ll need to fill the following fields:

• 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 a 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.

Klavio-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 statuses” if you want to send all user interactions as events to Meta. In this case, events will be automatically named using the Pipeline and user stage 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.

App configuration | Server GTM

Before starting

You will need to have an active Stape account with 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.

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 field:

• 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 to the detailed instructions on how to find the Container API Key.

Klavio-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 statuses” if you want to send all user interactions as events to Meta. In this case, events will be automatically named using the Pipeline and user stage 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.