> 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/analytics-dashboard/sessions.md).

# Impressions

Track playable reach and traffic sources with total impressions, leading partner and platform, and trend graphs over time.

<figure><img src="https://3403191029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYsCUHima0FilwMqIJBnV%2Fuploads%2Fgit-blob-77a3616cbc4f4c86fbf14b714a94b3b0ad5253d2%2FSessions.png?alt=media" alt=""><figcaption></figcaption></figure>

The **Impressions** section shows how many times your playable was viewable, where that traffic came from, and how it trended over time.

### Key Metrics

* **Total Impressions** – The number of times the playable was viewable. This is the broadest measure of reach.
* **Leading Partner** – The partner with the most impressions.
* **Leading Platform** – The device type with the most impressions.

### Impressions by Partner

<figure><img src="https://3403191029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYsCUHima0FilwMqIJBnV%2Fuploads%2Fgit-blob-e55c3fccec758f79c8f7116f2600fbc942187c09%2FSessions%20by%20Partner.png?alt=media" alt=""><figcaption></figcaption></figure>

A line chart with a line for each partner, showing impressions over the selected date range. Use it to spot:

* Traffic spikes from campaign launches
* Which partners drive the most volume
* Day-to-day changes, drop-offs, or plateaus

The chart plots by day for ranges up to a month, and by week for longer ranges.

### Impressions by Platform

<figure><img src="https://3403191029-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FYsCUHima0FilwMqIJBnV%2Fuploads%2Fgit-blob-7df69e08e7d97667183298cff5d35455998f81ec%2FSessions%20by%20Platforms.png?alt=media" alt=""><figcaption></figcaption></figure>

A line chart with a line for each device type. Platforms include:

* Mobile
* Tablet
* Desktop
* Television
* Wearable
* Other, for devices that can't be identified

Knowing where your audience plays helps inform creative format, controls, hotspot sizes, and overall user experience.


---

# 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/analytics-dashboard/sessions.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.