> 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/controls.md).

# Controls

Find definitions of each control section below. Let us know if we missed anything!

## FAQ

<details>

<summary>How do my cohorts automatically include the most recent cohort?</summary>

You can select a time range in the future to include recent months.&#x20;

Example: Today is September. I want to make sure March cohort is included in my 180 Days LTV report.&#x20;

You can just select Jan-Dec 2025 in the absolute date picker and every time you re-access the report in the future it will include the matured cohorts -> e.g. March next month. *Users can select months in the future to avoid having the problem of including future matured cohorts, as you described: They could also select Jan 2025 - Dec 2026 if they want.*

You could also create a relative lookback window if you don't want to look at YTD but the last 12 months maybe by selecting "Last 12 months" and then they will see Oct, Nov, Dec, Jan, Feb today and next month "March" (remove Oct), etc. So you basically create a relative lookback period that moves with time.

</details>

<details>

<summary>What are Breakdowns, Metrics and Filters?</summary>

### Breakdown

Segment to group your data into different categories.

### Metrics

Add an event to analyze. You can select one or multiple metrics depending on the report.

### Filters

Filter to include or exclude specific data.

</details>

{% content-ref url="/spaces/GWP01Uan8w7wePRkCAQS/pages/JIL9p5hP3IZ9pTXZcuqP" %}
[Contact Us](/help-1/contact-us.md)
{% endcontent-ref %}


---

# 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/controls.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.