> For the complete documentation index, see [llms.txt](https://docs.devtodev.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.devtodev.com/reports-and-functionality/project-related-reports-and-fuctionality/smart-view/cohort-analysis.md).

# Cohort analysis

{% embed url="<https://youtu.be/SbaVr0rxpmg?feature=shared>" %}
Cohort analysis overview
{% endembed %}

This report shows the dynamics of quality metrics for different cohorts based on install date.&#x20;

There are two pages available:

1. Custom cohorts
2. Weekly cohorts

The **Custom cohorts** report presents quality metrics data grouped by 3 cohorts.&#x20;

<figure><img src="https://2105883905-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnGcP_ZeRJ1ipj9O8dF%2Fuploads%2FJs3lPZcahrd31KCy2Xvk%2Fimage.png?alt=media&amp;token=bb3a7b0c-33df-4bb9-adeb-2aa787e7ce1f" alt=""><figcaption></figcaption></figure>

Default cohorts are calculated based on install dates only, but additional filters can also be used.

If you have data for the period of more than 3 days and less than the period of 28 days, the following cohorts are shown:

* Cohort 1 – users who installed the app yesterday
* Cohort 2 – users who installed the app 2 days ago
* Cohort 3 – users who installed the app 3 days ago

If you have data for the period less than 3 days, you will need to wait for cohorts to appear.

It is also possible to create custom cohorts that are based on a certain period of install date. Also, you can add available filters to them. Use the "+ Cohort" button to create a custom cohort.

There are 3 main widgets on this page:

* Table
* Retention line chart
* Cumulative ARPU line chart

With the table widget you can select and track up to 5 quality metrics. The following metrics are shown by default:

* Tutorial Conversion
* Retention Day 1
* Retention Day 7
* Paying Conversion
* Cumulative ARPU for 7 days

To build the report, click the “View result” button. If you would like to build the report after changing settings, use the “Refresh” button.

<figure><img src="https://2105883905-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnGcP_ZeRJ1ipj9O8dF%2Fuploads%2FElTYOL9FFo9spWiioNOG%2Fimage.png?alt=media&amp;token=fe441dbe-09f7-4828-9ead-d28c928375fc" alt=""><figcaption></figcaption></figure>

The **Weekly cohorts** page shows the audience and gross structure grouped by the week when the app was installed. It is possible to select the type of data display –  in absolute or percentage values.

<figure><img src="https://2105883905-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-LnGcP_ZeRJ1ipj9O8dF%2Fuploads%2FUYFVllskca3Lhtzahfrf%2Fimage.png?alt=media&amp;token=cf623d95-a209-48ad-836f-624b3b4ba618" alt=""><figcaption></figcaption></figure>


---

# 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.devtodev.com/reports-and-functionality/project-related-reports-and-fuctionality/smart-view/cohort-analysis.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.