> For the complete documentation index, see [llms.txt](https://docs.whaly.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.whaly.io/data-visualisation/chart-your-data/retention-chart.md).

# Retention chart

Retention chart are a great way to visualize cohorts

<figure><img src="/files/BysZLLBRnOxCvyPLJrSi" alt=""><figcaption></figcaption></figure>

### **Chart usage**

You must select two metrics to use the retention chart :&#x20;

* The first metric is the cohort value, for example the retained users
* The second metric is the cohort size, for example the total number of users in a cohort

You should also select two dimensions  to use the retention chart :&#x20;

* The first dimension is the cohort label, this will be placed vertically
* The second dimension is the step in the cohort, the will be placed as a column

In order to have ordered dimensions you should provide alphabetically ordereable dimension values, for example : &#x20;

Cohort labels:

```
2024-01, 2024-02, 2024-03, 2024-04, ...
```

Cohort steps:

```
Month 00, Month 01, Month 02, Month 03, ...
```

### **Chart characteristics**

* Number of metrics : 2
* Number of dimensions : 2


---

# 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.whaly.io/data-visualisation/chart-your-data/retention-chart.md?ask=<question>&goal=<endgoal>
```

`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.