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

# Client tracking

### Client tracking

In the Dashboard Usage configuration, you will find a card with the title ‘Client Information’. This configuration section will give you the choice to toggle on or off the following tracking options:

1. Operating System (OS and OS version)
2. Browser (browser, browser version and browser major version)
3. Screen (color depth, current resolution, available resolution, device XDPI and device YDPI)
4. Timezone
5. Language (language and system language)
6. Plugins (plugins, Java version, Flash version and Silverlight version)
7. Fonts (installed fonts)
8. Device (device, device type and device vendor)
9. Mobile (is mobile, is mobile Android and is mobile iOS)
10. CPU

For font information you can specify how to store the data. As standard, all installed fonts are stored in a single row (record). However, you can choose to only store the number of fonts installed or to store every font on a new row. When storing all fonts on a single row, fonts will be separated by a **comma**.

![Client information](https://appsfortableau.infotopics.com/wp-content/uploads/2021/04/client-information.jpg)


---

# 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/client-tracking.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.