> 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/data/chart-types.md).

# 차트 유형

핵클 데이터 분석에서 제공하는 차트 유형을 소개합니다. 분석 목적에 맞는 차트를 선택해 사용자 행동을 다양한 관점에서 분석하세요.

<table data-card-size="large" data-view="cards"><thead><tr><th>차트 유형</th><th data-hidden data-card-target data-type="content-ref">바로가기</th></tr></thead><tbody><tr><td>인사이트 분석<br>지표를 다양한 차트로 시각화하고 비교합니다.</td><td><a href="https://docs.hackle.io/data/chart-types/data-insight-analysis.md">인사이트 분석</a></td></tr><tr><td>퍼널 분석<br>단계별 전환율과 이탈률을 분석합니다.</td><td><a href="https://docs.hackle.io/data/chart-types/funnel-analysis.md">퍼널 분석</a></td></tr><tr><td>리텐션 분석<br>사용자의 재방문과 재사용 추이를 확인합니다.</td><td><a href="https://docs.hackle.io/data/chart-types/retention-analysis.md">리텐션 분석</a></td></tr><tr><td>유저패스 분석<br>사용자의 이동 경로와 이탈 지점을 파악합니다.</td><td><a href="https://docs.hackle.io/data/chart-types/user-path-analysis.md">유저패스 분석</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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.hackle.io/data/chart-types.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.
