Integrated Webhooks - Advanced tracking, identifying anonymous leads
How to identify and convert anonymous leads via Webhook on a website that has the Sprinthub tracking script.
Identifying the 'shubid' cookie
When inspecting the website page that contains the tracking script, you will see a list of all stored cookies. The cookie used to identify the lead is the shubid.
The image below shows this view in Google Chrome:

Getting the page cookies
To view the cookies via code, use the following JavaScript expression in the browser console:
It will return an object with the page cookies, including the shubid. With that, the desired cookie will be available as a property of this object, as shown below:

Webhook: Where to send the cookie
The shubid can be sent in the request body and must be mapped as the lead identifier in the 'Identifier To' column. In this way, when the integrated Webhook receives the lead data, it will be identified and it will be possible to configure actions for it in 'Extra Actions'.

Webhook: Automatic Lead Creation
For the lead to be identified and updated automatically when the Webhook is sent, simply enable the 'Enable automatic creation?' option, and match the fields with the keys received in the request.

Checking the lead history
To verify whether the lead was successfully linked, the history will show when they accessed a page, as well as information such as their location and the devices used to access the tracked website. It is also worth checking whether the data has been updated, such as name, WhatsApp, email, etc. Now it is possible to verify whether the lead visited specific pages and, based on that, add them to an automation flow or segment, optimizing the customer journey and boosting conversion.

Last updated
Was this helpful?