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

# Essential Guides

Master the core Analytics functionality with these essential guides. Learn to    create different chart types, configure KPIs, and apply filters effectively.

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Configure Big Number KPIs</strong></td><td>Display key performance indicators with comparisons and alerts for executive dashboards</td><td></td><td></td></tr><tr><td><strong>Create Line Chart for Trends</strong></td><td>Build time series visualizations to track performance trends and patterns</td><td></td><td></td></tr><tr><td><strong>Setup Bar Chart Comparisons</strong></td><td>Compare categories, products, or segments with effective bar chart visualizations</td><td></td><td></td></tr><tr><td><strong>Configure Dashboard Filters</strong></td><td>Apply smart filters and segments to focus analysis on specific data subsets</td><td></td><td></td></tr></tbody></table>


---

# 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.crobox.com/how-to-guides/analytics/essential-guides.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.