> For the complete documentation index, see [llms.txt](https://tembi.gitbook.io/tembi-knowledge-base/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tembi.gitbook.io/tembi-knowledge-base/product-news/market-intelligence/dashboards.md).

# Dashboards

Insights from MIA can easily be turned into dashboards.

You can either build your own dashboards or use Tembi’s library of pre-made dashboards, designed around common jobs and recurring questions.

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

**Custom dashboards** allow you to:

* Track the metrics that matter to your role
* Combine market, competitor, and account-level views
* Monitor changes over time in a consistent format
* Share a single source of truth across teams

**Pre-made dashboards** are built by Tembi and cover common use cases such as:

* Market overviews and country comparisons
* Competitive benchmarking
* Checkout positioning and visibility
* Portfolio performance and risk monitoring

All dashboards are powered by the same underlying dataset and update automatically as new data is collected.

This makes it easy to move from one-off analysis to repeatable monitoring - without rebuilding views every time a question comes up.


---

# 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:

```
GET https://tembi.gitbook.io/tembi-knowledge-base/product-news/market-intelligence/dashboards.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.