Send CRM events to Tracklution using Zapier (example used: Hubspot)

You can use Zapier to send data from a CRM like HubSpot to Tracklution. This is useful for tracking conversions, syncing deal updates, or enriching events - without writing any code. Follow these steps to send any events from any system to Tracklution. As an example this guide explains how to send data to Tracklution when a HubSpot deal stage is updated. The trigger can also be from another system than Hubspot.

What You Need

• Access to HubSpot or another CRM
• A Tracklution Tracking container
• Zapier account

Step-by-step instructions

1. Create a New Zap

• Zapier's instructions (opens in a new tab)

2. Add Trigger to your Zap

• App: Choose the CRM you are using, in this example we will be using HubSpot (opens in a new tab)
• Choose a Trigger: The trigger will determine when the data is sent to Tracklution.
  • In the example we are using “Deal Stage Changed”. This 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 Hubspot (or the CRM of your choice) is able to send the data to Zapier

3. Add Action to your Zap

• Setup:
  • App: Webhooks by Zapier
  • Action event: POST
• Configure:

• URL: Add the following URL: https://main.trlution.com/collect/hook?k=LS-1234567-3&track=QualifiedLead , but change the placeholder key (example: LS-1234567-3) to the unique container key 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 (example: QualifiedLead)
• Payload Type: json
• Other Configuration steps are optional. If you want to determine what data is sent to Tracklution, you can edit it in the “Data” step. Tracklution is able to parse the data and only use the important parameters such as email
• Test
  • We recommend testing with data that is fetched from the CRM in Step 2.

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

5. 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 our article about ContactData.
  • 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