> For the complete documentation index, see [llms.txt](https://support.charlla.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.charlla.io/userguide/statistics.md).

# 통계

통계탭에서는 라이브러리 모든 동영상의 통계를 합산하고, 분석한 자료를 볼 수 있어요. 각 비디오, 커머스 통계별로 동영상 순위 Top 10을 확인하세요. 비교일을 추가하여 주 별, 월 별 추이도 비교할 수 있어요.

[통계 알아보기](https://support.charlla.io/userguide/statistics/intro.md)

[비디오-로드수 통계](https://support.charlla.io/userguide/statistics/load.md)

[비디오-업로드 통계](https://support.charlla.io/userguide/statistics/upload.md)

[커머스-상세페이지 전환율 통계](https://support.charlla.io/userguide/statistics/conversion.md)

[커머스-시청자 참여수 통계](https://support.charlla.io/userguide/statistics/share.md)


---

# 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://support.charlla.io/userguide/statistics.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.
