> For the complete documentation index, see [llms.txt](https://docs.sprinthub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sprinthub.com/en/topics/api/api-advanced-advanced-tracking-via-tracking-script.md). # API - (Advanced) Advanced Tracking via Tracking Script Go to **System Settings > System > Tracking**:

```javascript ``` You will have access to your Tracking Script as shown above. You can insert this Script into any website or web system, always within the tag **\** and or before closing the **\**. With this script, you will send your Leads' browsing information into your **SprintHub**. Any Lead that accesses a site containing this Script will generate an Anonymous Lead within the **SprintHub**, which will track all pages this Lead visited. If on the same day or after a few days, this Lead returns to your site and decides to sign up in some form, where this Lead registration will be sent into your **SprintHub**, the system will make a *Merge* between the Anonymous Lead from the past and the new Lead that just signed up. In other words, you can know exactly what this Lead did on your site even before it became an identified Lead in the **SprintHub**. Therefore, if you are not using a Landing Page created in the **SprintHub**, it is highly recommended that you add this script to your site and or system. ### Now for the most advanced part! (For developers) Let's say you have an E-commerce or your own System where your Leads log in with username and password. It is possible, via tracking script, to create and or identify the Lead that logged in, using the email or username. Obviously you need to have access to the variables in your system that bring this information to the browser. With these variables in hand, you can send to SprintHub, via tracking script: **Example**: ```javascript ``` The variables within **{{ }}**, are examples of any system. You will need to know the system to know how and what those variables are. This script above must come **AFTER** the main tracking script. But both need to be inside **\**. Once that's done, you will be identifying your Lead within the **SprintHub**, since they may enter your system through a browser/device that is not being tracked. If the Lead above has the same email as an existing Lead, you can merge the information from both within the **SprintHub** automatically or manually. The method of ***Advanced Tracking*** above can be used, for example, for cart recovery. **Imagine the following hypothetical situation, but one that commonly occurs**: The Lead enters your site (ecommerce), logs in, and starts adding products to the Shopping Cart. They reach Checkout and when they see the shipping price, they give up on completing the purchase. With ***Advanced Tracking*** of the **SprintHub** properly configured, you are already sending this information to the **SprintHub**. The cart items, for example, you can send as Tags or as Custom Objects. Thus, you can create an Automation flow where the **SprintHub** can send an email or WhatsApp to this Lead after 1 hour of cart abandonment, containing a discount coupon so they come back and complete their purchase. This is just **ONE example**, but the possibilities are numerous. **NOTE:** If you use proprietary systems such as Woocommerce, Magento, Hotmart, Vtex, where you will probably not know the variables to send to SprintHub, we recommend doing this via API, using systems like N8N, Zapier, or Make. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.sprinthub.com/en/topics/api/api-advanced-advanced-tracking-via-tracking-script.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.