> 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-tracking-work.md). # How Website Tracking Works HockeyStack's website tracking is not magic, although it certainly feels like that. It happens through a script file hosted through a CDN network, much like any other web analytics tool out there. What separates HockeyStack from the general pack is that it listens to all events registered on your website so that it can track clicks, submissions, and searches, as well as pageviews. The tracking script is at the time of this writing about 8.5 kilobytes. Although byte size definitely matters, an addition of this small magnitude would not affect your site speed at all. A few notes: * HockeyStack does not collect passwords or any other sensitive information from form submissions. * HockeyStack —by default— does not use cookies to save identifiers. Collected data: * Website visit behavior, including pageviews, sessions, referrers, clicks, scrolls, form submissions * Emails from forms submitted * Geolocation data at the city granularity * Device and browser metadata Tracking & Cookie Consent: * **Users Accept Cookies:** Full website tracking and attribution. * **Users Decline Cookies:** No website tracking, but lifecycle data from HubSpot and purchase numbers remain accurate. * HockeyStack ensures privacy compliance while maintaining key insights. --- # 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-tracking-work.md?ask=&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.