> 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.md).

# Website Tracking

- [How Website Tracking Works](https://docs.hockeystack.com/technical-details/tracking/how-does-tracking-work.md)
- [Implementation](https://docs.hockeystack.com/technical-details/tracking/implementation.md)
- [Google Tag Manager](https://docs.hockeystack.com/technical-details/tracking/implementation/google-tag-manager.md)
- [WordPress](https://docs.hockeystack.com/technical-details/tracking/implementation/wordpress.md)
- [React](https://docs.hockeystack.com/technical-details/tracking/implementation/react.md)
- [GDPR Compliance](https://docs.hockeystack.com/technical-details/tracking/implementation/fingerprinting-is-gdpr-compliant.md)
- [Cookieless Tracking](https://docs.hockeystack.com/technical-details/tracking/how-does-cookieless-tracking-work.md)
- [Reverting to Cookie-Based Tracking](https://docs.hockeystack.com/technical-details/tracking/how-does-cookieless-tracking-work/reverting-to-cookie-based-tracking.md)
- [Identifying Users](https://docs.hockeystack.com/technical-details/tracking/identifying-users.md)
- [Enhanced Fingerprinting](https://docs.hockeystack.com/technical-details/tracking/identifying-users/enhanced-fingerprinting.md): Enhanced Fingerprint add-on for advanced VPN and cross-device visitor tracking.
- [Bot Traffic](https://docs.hockeystack.com/technical-details/tracking/identifying-users/about-bot-traffic.md)
- [What Creates a Tracked User](https://docs.hockeystack.com/technical-details/tracking/what-creates-a-tracked-user.md): This article details how HockeyStack determines and counts a tracked user.
- [Tracking Custom Goals](https://docs.hockeystack.com/technical-details/tracking/tracking-custom-goals.md)
- [Piggyback scripts](https://docs.hockeystack.com/technical-details/tracking/piggyback-scripts.md): HockeyStack can detect and piggyback on a number of third‑party embeds and load the corresponding helper script. Below is everything you need to know.
- [Bypassing Adblockers](https://docs.hockeystack.com/technical-details/tracking/bypassing-adblockers.md)
- [Troubleshooting](https://docs.hockeystack.com/technical-details/tracking/why-is-my-hockeystack-integration-failing.md)
- [Privacy Policy](https://docs.hockeystack.com/technical-details/tracking/how-does-hockeystack-affect-my-privacy-policy.md)
- [Why Website Tracking via HockeyStack’s JS Snippet Outperforms CDP Data](https://docs.hockeystack.com/technical-details/tracking/why-website-tracking-via-hockeystacks-js-snippet-outperforms-cdp-data.md): Cookieless Fingerprinting Captures Real Customer Behavior Your CDP Never Sees
- [Customize Your Tracking](https://docs.hockeystack.com/technical-details/tracking/customize-your-tracking.md): This document describes how the HockeyStack website tracking pixel is deployed and emphasizes the customer's complete control over when and how the pixel fires.


---

# 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.hockeystack.com/technical-details/tracking.md?ask=<question>&goal=<endgoal>
```

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