> 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-tab/listing-view.md).

# Listing View

Learn what the ANALYTICS Listing View shows: an account-level summary of your creatives, and a table to compare them side by side.

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

The **Listing View** is the first page you see in ANALYTICS. It opens with a summary of how all your creatives are performing together, then lists each creative so you can compare them side by side.

Everything on the page reflects the [Date Range](/analytics/analytics-tab/adjusting-the-date-range.md) and [Partners](/analytics/analytics-tab/filtering-searching-and-sorting.md#partners) filter in the header.

### Summary

The row of metrics at the top adds up every creative in the list:

* **Total Impressions** – How many times your creatives were viewable.
* **Total Engaged** – Impressions where users engaged with a creative.
* **Total Captured** – Impressions where users clicked a CTA.
* **Average Engaged Rate** – Total Engaged as a percentage of Total Impressions.
* **Average Captured Rate** – Total Captured as a percentage of Total Impressions.

When you search the list, the summary recalculates for just the creatives that match.

### Creatives

Below the summary, the **Creatives** table lists every creative with analytics in the selected range:

* **Name** – A thumbnail of the creative, with the project name above the variant name.
* **Impressions** – How many times the creative was viewable.
* **Engagements** – Engaged impressions, with the engaged rate in brackets.
* **Captures** – Captured impressions, with the capture rate in brackets.
* **First Event** – The date the creative first recorded analytics in the range.
* **Last Event** – The date it most recently recorded analytics.

The list is sorted by **Last Event** by default, so the creatives with the most recent activity are at the top. See [Filtering, Searching, and Sorting](/analytics/analytics-tab/filtering-searching-and-sorting.md) to change it.

Use **Rows per page** below the table to show 25, 50, or 100 creatives at a time.

Click any row to open that creative's [Analytics Dashboard](/analytics/analytics-dashboard/overview.md).

{% hint style="info" %}
If nothing has recorded analytics in the selected range, the page shows **No Analytics**. Widen the Date Range or clear the Partners filter to see more.
{% 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/analytics-tab/listing-view.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.
