> For the complete documentation index, see [llms.txt](https://docs.hockeystack.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hockeystack.com/technical-details/tracking/how-does-cookieless-tracking-work.md).

# Cookieless Tracking

In this day and age, opting out of cookies has become the default and tracking tools switching to cookie-less alternatives has become the fashion. Thankfully, the HockeyStack team follows the fashion trends.

The HockeyStack snippet that you receive when you sign up by default is modified for cookieless tracking:

Copy

```javascript
<script async data-apikey="YOUR_API_KEY" data-cookieless src="https://cdn.jsdelivr.net/npm/hockeystack@latest/hockeystack.min.js"></script>
```

The `data-cookieless` attribute runs the script under cookieless tracking and removing that would automatically switch you to cookie-based tracking.

## But then how do you track unique visitors? <a href="#block-1a18d5f71c7b4cf792b0e7e398993949" id="block-1a18d5f71c7b4cf792b0e7e398993949"></a>

Although we can't disclose all the details, we use a fingerprint generated at the server and hashed (sha256) with a unique salt so that it would be impossible to obtain the original data from the fingerprint.

To create this fingerprint, we use data such as but not limited to:

* Device type
* Screen height, width, and depth
* Browser
* OS
* Browser language
* Browser version
* Plugins installed
* Extensions
* Country and city-level geolocation data
* Timezone

All this data is gathered through the browser, and its variety ensures that the fingerprint created is as unique as possible.

It is important to note that HockeyStack does not in any way store IP addresses or other PII (personally identifiable information) to create this fingerprint. The validity of the fingerprint relies on the combination of all these different datapoints. When hashed, it gives no one, including HockeyStack itself, to attain any further information about the visitor. `ec5d7eb1-4c2b-4da0-a214-c7059f1fa9e6` This is an example user id that was generated from the system. As you can see, it is impossible to decrypt but gives you an opportunity to record unique traffic.

If you have any concerns about how this fingerprinting technology complies with GDPR, you can read more about it here:

[🍪Reverting to Cookie-Based Tracking](/technical-details/tracking/how-does-cookieless-tracking-work/reverting-to-cookie-based-tracking.md)


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hockeystack.com/technical-details/tracking/how-does-cookieless-tracking-work.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.