> 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/filtering-searching-and-sorting.md).
# Filtering, Searching, and Sorting
Search for creatives, sort the Listing View, and filter ANALYTICS by partner.
The Listing View header has tools to find specific creatives, order the list, and narrow your data to the partners you care about. From left to right: search, sort, **Partners**, and **Date Range**.
***
### Search
Type in **Search Analytics...** to filter the list by project or variant name as you type. The summary at the top of the page recalculates for just the creatives that match.
***
### Sort
The sort dropdown sets the order of the list. It defaults to **Last Event**, newest first. You can sort by:
* **Name**
* **Impressions**
* **Engagements**
* **Captures**
* **First Event**
* **Last Event**
**Engagements** and **Captures** sort by rate rather than count, so creatives that convert best rise to the top regardless of traffic.
Click the arrow next to the sort dropdown to switch between ascending and descending order.
***
### Partners
The **Partners** filter narrows ANALYTICS to the ad networks you choose. It defaults to **All Partners**.
* Type to search the list. Only partners with data in the current date range appear.
* Tick one or more partners to include them. Selected partners move to the top of the list.
* Choose **All Partners**, or click the **x** in the field, to go back to every partner.
With partners selected, every number on the page reflects only those partners. The same filter is available on the [Analytics Dashboard](/analytics/analytics-dashboard/overview.md) and in the [Spreadsheet](/analytics/analytics-dashboard/export.md) view.
{% hint style="info" %}
Partners appear by name, like **AppLovin** or **Digital Turbine**. Traffic that can't be matched to a partner is grouped as **Other**.
{% 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/filtering-searching-and-sorting.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)