> For the complete documentation index, see [llms.txt](https://docs.adalysis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.adalysis.com/tools/performance/segments/hour-of-the-week.md).
# Hour of the week
Adalysis visualizes your PPC performance based on the hours of the week, so you can optimize your ad schedules and bids. You can find the heatmap and comparison charts under **Segments** > **Hour of week**.
### Hour of the week heatmap
#### Customize your analysis
* [x] Filter your data by campaign, campaign type, or label.
* [x] Choose to segment your performance data by device.
* [x] Change the time frame on the right-hand side (default: last 30 days).
* [x] Switch between **14 different performance metrics**, incl. impressions, conversions, and lost impression share.
#### Compare your performance for key factors
Scroll down for two further performance graphs:
* [x] Track up to four performance metrics across the week. (Click on the down arrows to choose the metrics you need.)
* [x] Compare **weekday and weekend** performance for impressions, clicks, and conversions.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.adalysis.com/tools/performance/segments/hour-of-the-week.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.