> 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/hockeystack-101-navigating-the-platform.md).

# HockeyStack 101: Navigating the Platform

Walkthrough of HockeyStack's Platform: Atlas, Deals/Companies, Odin, Analytics, Settings

{% embed url="<https://www.loom.com/share/21b1f1474d4742308c6845f8f4f083e6>" %}

Note: your instance may look different from what's shown in the video, depending on your access level and plan

**Atlas** - The data foundation. Atlas connects every source in your stack, unifies identities, and applies your business rules (funnel stages, goals, touchpoints, breakdowns) so your data is clean and consistent across the entire platform.

**Deals/Companies** - Where you explore your deals, companies, and people. See every touchpoint across a deal's journey, filter and segment accounts by engagement or stage, and save views or export to CSV.

**Odin** - The AI analyst. Ask Odin any question about your marketing and sales performance in plain English and get instant answers, visualizations, and recommendations.

**Analytics** - Reports, dashboards, attribution views. Build custom reports using breakdowns, goals, and touchpoints to get full-funnel visibility from first touch to closed revenue, across every attribution model. Dashboards let you organize and view your reports in one place.


---

# 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/hockeystack-101-navigating-the-platform.md?ask=<question>&goal=<user_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.