> For the complete documentation index, see [llms.txt](https://docs.infotopics.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.infotopics.com/dashboardusage/features/analytics.md).

# Analytics

### Analytics

All Dashboard Usage data will be stored in the (local) database you configured during the Installation process. To help you kick start gathering insights, we prepared a free Tableau analytics workbook. It comes included with in your .zip file when you download the extension.

The workbook connects to our demo database as standard. Credentials are:

username: demodemo\
password: demodemo

The demo database has the exact same structure as the dashboard usage database, so integrating your own data is simple. Just replace the data connection with your own and you’re set.

Dashboards in this workbook are:

* Events
* Client info
* Extensions

These respectively help you gather insights on dashboard events, user information and extension usage.

There is much more information that can be gathered from Dashboard Usage. We’re curious to see what you’ll do with it!

![The new DashboardUsage dashboard usage](https://appsfortableau.infotopics.com/wp-content/uploads/2021/05/analytics-events.png)![Dashboard Usage – Getting Started dashboard usage](https://appsfortableau.infotopics.com/wp-content/uploads/2021/05/analytics-users.png)![Dashboard Usage – Getting Started dashboard usage](https://appsfortableau.infotopics.com/wp-content/uploads/2021/05/analytics-extensions.png)


---

# 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.infotopics.com/dashboardusage/features/analytics.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.