> For the complete documentation index, see [llms.txt](https://docs.candelacharts.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.candelacharts.com/investing/risk-adjusted-performance/monthly-return-heatmap/usage.md).

# Usage

Monthly Return Heatmap Usage

<figure><img src="https://3870127617-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FCBVnUk5c5TVytimjy972%2Fuploads%2FkFkMaZsQ8BNSSSXDA99d%2Fdocs-monthly-returns-heatmap-002.png?alt=media&amp;token=16a76b0e-611a-4adf-b92c-e8a6b0935d85" alt=""><figcaption></figcaption></figure>

To effectively identify seasonal patterns and optimize your entry timing based on historical data, follow these guidelines for using the Monthly Returns Heatmap:

1. **Set Timeframe**: Ensure your chart is set to the **1M (Monthly)** timeframe. A warning will appear on the chart if you are on a lower timeframe.
2. **Analyze Seasonality**: Use the Heatmap Table to spot recurring patterns across multiple years. For example, look for historically weak late-summer months or strong end-of-year rallies that repeat consistently.
3. **Deep Dive**: Switch the UI Mode to the Bar Chart and enter a specific Target Year in the settings. This allows you to visualize the month-by-month return distribution and magnitude for that specific historical period.
4. **Customize Colors**: Adjust the bullish and bearish base colors in the settings to match your personal chart theme or visual preferences.


---

# 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://docs.candelacharts.com/investing/risk-adjusted-performance/monthly-return-heatmap/usage.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.