Tracklution webhook - Basics
Tracklution's webhook provides a seamless and efficient way to enrich data with information from various external systems, including CRM, booking systems, billing systems, ERP, and calling systems.
Webhook enables to effortlessly bring additional tracking data to Tracklution, such as offline conversions and additional conversion data. Whether it's obtaining insights from sources that may not be directly linked to the website or safeguarding sensitive information, Tracklution's webhook offers a user-friendly and powerful solution for optimising data flow.
Basic process
- Decide if you want to enrich already existing data in Tracklution or send new events to Tracklution with Webhooks.
- Navigate to the external systems Webhook settings and follow the instructions of the external system on how to set up a webhook. Follow these instructions if you want to send data from Stripe.
- Once needed, get Tracklution Webhook Endpoint URL from your Tracklution account under "Webhook":
- Edit the Webhook Endpoint URL query parameters according to your needs (more on these under "Webhook query parameters" below)
- Continue with the external system's instructions to finish up the set up.
- Once the setup is finished, you will be able to see successful webhook import events at the end of the "Webhook" -page in your Tracklution account (screenshot in step 3).
Webhook Endpoint URL
The URL for the Webhook endpoint is:
https://tracking.leadspark.io/collect/hook
Webhook query parameters
When making a GET request to the endpoint, following query parameters need to be set:
Parameter | Description | Required |
---|---|---|
k | Your Tracking Container Key | yes |
track | If you want to record an event, e.g. “Purchase” or “BookingComplete”, send the event name in this field. Without ‘track’ parameter the incoming data is handled as additional information and Tracklution tries to match it into an existing session data without adding a new event to the session. | no |
value | If you are bringing in a Purchase event with the ‘track’ parameter, and you want a value being recorded to this event, insert the value in this field | no |
currency | If you are bringing in a Purchase event with the ‘track’ parameter including ‘value’ parameter, insert currency in this field | If ‘value’ parameter is used, then required |
url | The URL of the page where event happened or additional data was obtained | no |
email | no | |
phoneNumber | Phone number | no |
firstName | First name | no |
lastName | Last name | no |
birthday | Birthday, example input: 1985-06-17 | no |
gender | Example input: ‘male’ or ‘female’ | no |
address | Street address | no |
postCode | Postal code | no |
city | City | no |
country | Country | no |
externalId | External ID that could be any unique identifier | no |
gclid | Google Click ID, if available | no |
fbclid | Meta Click ID, if available | no |
The Tracking Container Key
is a unique identifier for your Tracking Container.
You can find it on the "Your Tracking Containers" view in the Tracking
section of the Tracklution Dashboard.
Request examples
Remember to set up Webhooks according to our onboarding guide inside your Tracking Container. The examples below include test data only for demonstration purposes.