> 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/technical-documentation.md). # TECHNICAL DOCUMENTATION - [Integrations](https://docs.crobox.com/technical-documentation/integrations.md): Connect Crobox with CRM platforms and external product-data sources. - [CRM Integrations](https://docs.crobox.com/technical-documentation/integrations/crm-integrations.md): Connect your Crobox experiences to your Customer Relationship Management (CRM) platform to capture user preferences and enable personalized follow-up communications. - [Data Integrations](https://docs.crobox.com/technical-documentation/integrations/data-integrations.md): Import external product data into Crobox as properties for use across experiences. - [Crobox MCP](https://docs.crobox.com/technical-documentation/crobox-mcp.md) - [Custom Themes and CSS](https://docs.crobox.com/technical-documentation/custom-themes-and-css.md) - [Set Custom Visitor Properties with the Pageview API](https://docs.crobox.com/technical-documentation/setting-custom-visitor-properties-with-pageview-api.md): Send custom visitor properties to Crobox through the pageview API for targeting, analytics, and advanced personalization. - [Product Finder Event Tracking Integration](https://docs.crobox.com/technical-documentation/product-advisor-event-tracking-integration.md): This guide explains how to integrate the Product Finder event to send analytic information to your analytics platform. - [Pre-selecting Finder Questions](https://docs.crobox.com/technical-documentation/pre-selecting-advisor-questions.md): Learn how to use the function crobox.setFinderState to control the state of the Finder via our JavaScript API. You can pre-select answers for specific questions, and control question page navigation. --- # 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/technical-documentation.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.