> For the complete documentation index, see [llms.txt](https://docs.drivepoint.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.drivepoint.io/using-the-web-app/reports/cohort-analysis.md).

# Cohort Analysis

Reports included: Customer Retention, LTV by Dimension, Cohorted Financials and more.

## Definitions

* Cohorts are groups of customers who purchased your product(s) within the same month. The goal of this bundle is to uncover which months have been more lucrative for the business
* Customer lifetime value (LTV) is a measure of the average customer’s revenue generated over their entire relationship with a company. Learn more [here](https://www.netsuite.com/portal/resource/articles/ecommerce/customer-lifetime-value-clv.shtml).&#x20;

## Pro Tips

* You can sort columns by clicking on the header row

*💡1 click = sort descending, 2 clicks = sort ascending, 3 clicks = back to original*

* You can drag and drop columns in tables to compare them side by side

*💡 Your changes won’t be saved so once you navigate away, the table turns into its default again. Great for screenshots though!*

<br>


---

# 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.drivepoint.io/using-the-web-app/reports/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.
