> For the complete documentation index, see [llms.txt](https://docs.chatlayer.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chatlayer.ai/navigation/analytics/dashboard.md). # Dashboard The dashboard is the main page in our Analytics. It shows a lot of important information about your bot in a quick and simple overview. If you don't see any data in the overview, you might be viewing the **DRAFT** data of your unpublished bot. Your customers are interacting with the [**LIVE** or published version](/publish/publishing-your-bot.md). Switch your filter to **LIVE** to see actual customer data. {% hint style="info" %} Not familiar with analytics? We recommend that you have a look at our [Analytics concepts](/bot-answers/definitions.md). {% endhint %} ## Filtering

Filtering features for your Analytics dashboard.

Use these filters to customize the dashboard view and create specific insights for your bot, helping you monitor its progress over time: * **All channels** allows you to filter on specific channels. * **All languages** shows information about your bot in different languages. {% hint style="info" %} The timestamp of the data you see in the analytics dashboard is based on the timezone of your browser. {% endhint %} ## Analytics overview ### Customers The [**Customers**](#customers) tab in Analytics allows you to check your new and returning customers.

### Conversations The [**Conversations**](/navigation/analytics/conversations.md) tab shows the distribution of bot conversations in all available languages. {% hint style="info" %} [Switching from **Languages** to **Channels** ](#filtering)will show the use of the bot over different channels (if these are used of course). {% endhint %}

[**Conversations**](/navigation/analytics/conversations.md) also display the proportions of conversations with handover, average number of messages and time spend.

{% hint style="warning" %} Is the number of conversations in the Dashboard different from the number of conversations in the conversation [**History**](/navigation/history.md)? That's because in **Analytics**, we show all conversations, whereas in the **History** overview, we only include conversations where the user actually replied. {% endhint %} ### User messages

The **User messages** tab takes you to the [Conversations](/navigation/analytics/conversations.md) page with an overview of how many messages are understood, not understood, or clicked. ### Top intents The top intents tab is showing the top 5 triggered intents most often, including the number of calls and their percentages. Clicking on **Details** in the right upper corner will bring you to the [**Intents** ](https://docs.chatlayer.ai/bot-answers/analytics/intents)page.

### Customers activity Customers activity gives an idea of when your users are interacting the most with the bot throughout the day.

### Customer flow The [**User flow**](/navigation/analytics/user-flow.md) tab gives an overview of the user journey through the bot.

--- # 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.chatlayer.ai/navigation/analytics/dashboard.md?ask=&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.