> 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/marketing-intelligence/odin-ai.md). # Odin AI Odin is your AI analyst inside HockeyStack. It helps go-to-market teams get fast, accurate answers and take action with confidence. Once your GTM data is ingested by HockeyStack, Odin analyzes everything — from CRM activity and campaigns to ads and web traffic. It answers questions in plain language and recommends next steps like rerouting the budget, prioritizing segments, or channel optimization. Common use cases include: * Funnel analysis * Lift reports * Attribution breakdowns * Spend optimization You can use Odin in the HockeyStack UI or [directly in Slack](/integrations/other/slackbot-for-odin.md) by tagging `@hockeystackodin` in any channel or DM. Every output is tested, structured, and auditable. Odin doesn’t guess — it follows your logic, runs thousands of internal checks, and stays tightly scoped to your data and definitions. Odin is the first thing you’ll see in HockeyStack. It’s your starting point for context-aware guidance, is aligned to your GTM strategy, and is always ready to provide insights and analyses. **Want to go deeper?** Explore Odin’s capabilities in here! --- # 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/marketing-intelligence/odin-ai.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.