---
title: "CRM integrations"
description: "Send CRM events to Tracklution In the video below, we show how to send offline conversions with a webhook in two ways: 1. Using the platform’s own automation tool (example from Zoho CRM) 2. Using Zapier as a middleware (starting from 15:30) alt text{height=315 width=560} Send CRM events to Tracklution (example: using Zapier) You can send data from a CRM to Tracklution either directly through the CRM's native webhook functionality (if your subscription supports it) or by using…"
description_short: "Send CRM events to Tracklution In the video below, we show how to send offline conversions with a webhook in two ways: 1."
slug: "crm-integrations"
category_slug: "data-sources"
category_name: "Data Sources"
order: 4000000002
published_at: "2025-06-25T09:53:32+00:00"
updated_at: "2026-06-04T17:47:59+00:00"
language_code: "en-US"
tags: []
---
## Send CRM-events to Tracklution
In the video below, we show how to send offline conversions with a webhook in two ways:
1. Using the platform’s own automation tool (example from Zoho CRM)
2. Using Zapier as a middleware (starting from 15:30)
{height=315 width=560}
## Send CRM-events to Tracklution (example: using Zapier)
You can send data from a CRM to Tracklution either directly through the CRM's native webhook functionality (if your subscription supports it) or by using an automation platform such as Zapier. This is useful for tracking conversions, syncing deal updates, or enriching events without custom development.
This guide uses Zapier in the middle as the automation tool as an example, but the same approach works with any CRM or system capable of sending webhook requests. If your CRM subscription includes webhooks, you can send events directly from the CRM to Tracklution without Zapier as an intermediary.
As an example, this guide explains how to send data to Tracklution when a CRM deal stage is updated. The trigger can also come from another event in HubSpot or from a completely different system.
### Prerequisites
- Access to a CRM
- A Tracklution tracking container
- Zapier, or another automation platform account (if you don't send the webhook directly from your CRM)
### Step-by-step instructions
#### Create a new Zap
- Zapier's instructions [here](https://zapier.com/blog/get-started-with-zapier/).
You can also start creating the automation inside your CRM if you prefer not using Zapier.
#### Add a trigger to your Zap
- **App:**Choose the CRM you are using
- **Choose a trigger:**The trigger will determine when the data is sent to Tracklution.
- For example, you can use “Deal Stage Changed”. Then the automation runs whenever a deal moves to a new pipeline stage.
- Configure the Trigger according to your use case (choose the Deal pipeline and stage for example).
- Test the action to ensure the CRM of your choice is able to send the data to Zapier.
Similar automation can be created inside your CRM automations.
#### Add action to your Zap
1. Setup:
- **App:**Webhooks by Zapier
- **Action event:**POST
2. Configure:
- - **URL:**Add the webhook URL:
- Example: **https:/** **/****tralut.YourDomain.****com/collect/hook?k=LS-12345678-1&track=QualifiedLead**,
- Change the placeholder in URL & unique container key to the one's found in your Tracklution dashboard’s Webhook-tab, and the placeholder event name to the name you want the Event to appear in Tracklution with.
- Here's instructions where to find your unique url -> [Documentation](https://support.tracklution.com/kb/article/15/send-events-from-any-platform-with-a-webhook#how-to-send-events-to-tracklution-with-webhooks-%28where-to-get-the-webhook-url%29 "https://support.tracklution.com/kb/article/15/send-events-from-any-platform-with-a-webhook#how-to-send-events-to-tracklution-with-webhooks-(where-to-get-the-webhook-url)").
- **Payload type:**json
- **Data**: Add the key-value pairs you want to send with the webhook, such as email, event value, currency, or other event details.
- **Test:** We recommend testing with data that is fetched from the CRM in Step 2.
#### Validate the setup
- Once the automation sends data to Tracklution, you will be able to see those in the webhook tab of Tracklution.
- Wait for a couple of minutes after sending the event, then go to the Webhook-tab in the Tracklution container dashboard and scroll to “Webhook Import Events” and see if the event appears on the list.
- If you don’t see an event, it means there is a mistake in your Zapier setup, review the steps 2 & 3.
- You should be able to see the event name (QualifiedLead in the example), and what data was parsed from the payload by clicking “view” on the event row.
- By clicking the Show Import Content, you will be able to see what data was sent from Zapier
## Match the event with existing website sessions
- It is crucial that the CRM-event is matched to an existing website session.
- Tracklution links CRM-events (like "QualifiedLead") to real website visitors by matching the webhook data - typically using email, phone, or other identifiers. If the CRM-event is not matched to an existing session, the ad platforms will not have any other data of the conversion other than what you send from the CRM (Click ID’s and other session data is lost).
- To make matching work:
- Make sure the CRM event AND the website session both include a common identifier (like email or external ID), and it is sent to Tracklution. To track identifiers like emails from the website session, please refer to this article about ContactInfo-event:
- [https://support.tracklution.com/kb/article/13/event-tracking-guide#contactinfo-event](https://support.tracklution.com/kb/article/13/event-tracking-guide#contactinfo-event)
- You don't need to configure anything extra: if the data includes matchable info, Tracklution will handle the rest.
- To ensure the event is matched to a session, go to the session log on the Tracklution dashboard, search for the event and see if it was tied to a website session, or if the event appears as an individual event without other session data or a link to a parent session.
- Event that is not linked to any session:
- - Event that is linked to a parent session:
- If no match appears:
- Double-check that the CRM event and the website session includes matchable data (like email)
- Ensure the visitor has been tracked on the website