> For the complete documentation index, see [llms.txt](https://docs.hackle.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hackle.io/en/data/chart-types.md).

# Chart Types

This page introduces the chart types available in Hackle Data Analytics. Select the chart that fits your analysis purpose and analyze user behavior from multiple perspectives.

<table data-card-size="large" data-view="cards"><thead><tr><th>Chart Type</th><th data-hidden data-card-target data-type="content-ref">Go to</th></tr></thead><tbody><tr><td>Insight Analysis<br>Visualize and compare metrics across various charts.</td><td><a href="/en/data/chart-types/data-insight-analysis.md">Insight Analysis</a></td></tr><tr><td>Funnel Analysis<br>Analyze conversion and drop-off rates at each step.</td><td><a href="/en/data/chart-types/funnel-analysis.md">Funnel Analysis</a></td></tr><tr><td>Retention Analysis<br>Check trends in user revisits and repeat usage.</td><td><a href="/en/data/chart-types/retention-analysis.md">Retention Analysis</a></td></tr><tr><td>User Path Analysis<br>Identify the paths users take and where they drop off.</td><td><a href="/en/data/chart-types/user-path-analysis.md">User Path Analysis</a></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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.hackle.io/en/data/chart-types.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
