> For the complete documentation index, see [llms.txt](https://docs.coda.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.coda.co/coda-portal/key-features/data-insights/2.-overview-of-the-dashboard-details-page.md).

# 2. Overview of the Dashboard Details Page

## <mark style="color:purple;">Overview</mark>

Once inside the <mark style="color:purple;">**Overview**</mark> dashboard, you will see a range of filters at the top.\
Select the start and end date to view your data within a specific time period.<br>

<figure><img src="https://files.readme.io/28e3b2b-image7.png" alt=""><figcaption></figcaption></figure>

## <mark style="color:purple;">Filters</mark>

There are many filters to assist you in slicing through the messy data and finding valuable insights.

You can view the TPV by country, top-performing payment types, top-performing payment methods, and Payment Success rates over a time period.

By using the filters properly, you can discover insights about your customers such as being able to check how the new payment methods are performing from the date of launching!<br>

<figure><img src="https://files.readme.io/cfdf228-image6.png" alt=""><figcaption></figcaption></figure>

Happy exploring!


---

# 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.coda.co/coda-portal/key-features/data-insights/2.-overview-of-the-dashboard-details-page.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.