> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/analytics/navigation.md).

# Navigation

<figure><img src="https://3403191029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYsCUHima0FilwMqIJBnV%2Fuploads%2Fgit-blob-087d8df4aa8832a07ce8ef1ae76ed93bee270671%2FToolbar%20(1).png?alt=media" alt=""><figcaption></figcaption></figure>

CRAFTSMAN ANALYTICS is accessible directly from your main dashboard and provides two primary views: the [**Listing View**](/analytics/analytics-tab/listing-view.md) (multi-project comparison) and the [**Analytics Dashboard**](/analytics/analytics-dashboard/overview.md) (deep-dive into a single playable). This section walks through how to access both and what you’ll see when you arrive.

### **Navigating to Analytics**

To open Analytics:

{% stepper %}
{% step %}

#### Log in to CRAFTSMAN+ and find the top navigation menu.

{% endstep %}

{% step %}

#### Click the **Analytics** tab.

{% endstep %}

{% step %}

#### The Listing View opens, with a summary of all your creatives and a table to compare them.

{% endstep %}
{% endstepper %}

Click any creative in the list to open its Analytics Dashboard.

{% hint style="info" %}
The **Analytics** tab appears for companies with ANALYTICS enabled. If you don't see it, contact your account manager.
{% endhint %}


---

# 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://help.craftsmanplus.com/analytics/navigation.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.
