> For the complete documentation index, see [llms.txt](https://docs.crobox.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.crobox.com/getting-started.md). # GETTING STARTED - [First Steps](https://docs.crobox.com/getting-started/first-steps.md): Everything you need to know about integrating Crobox on your website. - [Crobox Snippet Implementation](https://docs.crobox.com/getting-started/first-steps/get-started-with-crobox.md): Integrating Crobox on your website is lightweight and fast. All you need to get started is to implement the Javascript Snippet (i.e., tag) manually or in your tag manager. - [Event Tracking Implementation](https://docs.crobox.com/getting-started/first-steps/event-tracking-implementation.md): After adding the Crobox snippet to your website, the next step is to implement event tracking by implementing the Javascript API snippets listed in this document. - [Cookie Wall Settings](https://docs.crobox.com/getting-started/first-steps/cookie-wall-settings.md): This document explains how to implement Crobox according to your cookie policy. - [Content Security Policy Header](https://docs.crobox.com/getting-started/first-steps/content-security-policy-header.md): In this article we will describe the necessary steps your team will need to take in order to whitelist Crobox in your Content Security Policy header. --- # 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.crobox.com/getting-started.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.