> 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/adjusting-the-date-range.md).

# Adjusting the Date Range

Choose the time window ANALYTICS reports on.

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

The **Date Range** dropdown in the top right of ANALYTICS sets the time window for every metric on the page. It's available on the Listing View, the Analytics Dashboard, and the Spreadsheet view.

Choose a preset:

* **1 Day**
* **1 Week**
* **1 Month** (the default)
* **3 Months**
* **Custom**

Choose **Custom** to pick your own start and end dates. A custom range can go back up to six months, and must be between 3 days and about 3 months long.

Changing the date range updates every metric right away. Charts group data by day for ranges up to a month, and by week for longer ranges.


---

# 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/adjusting-the-date-range.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.