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

# 성과 확인하기

## 이 글에서는

이메일 기준에서 통계를 확인하는 방법에 대해 알아봅니다.

***

스티비에서는 개별 이메일 단위, 주소록 단위, 기간별 이렇게 세 가지 관점에서 통계 데이터를 제공합니다. '성과 확인하기' 섹션에서는 개별 이메일 단위의 통계 지표를 어떤 기준으로 측정하는지 살펴봅니다.

아래 도움말을 통해 원하는 내용을 확인해 보세요.

{% content-ref url="/pages/Wkfy6ZawE4zeC5WeRmkw" %}
[통계 기능 이해하기](/email/analytics/understand-statistics-features.md)
{% endcontent-ref %}

{% content-ref url="/pages/ypxWFlxOnvOxxNGSyhXv" %}
[이메일 통계 대시보드](/email/analytics/email-statistics-dashboard.md)
{% endcontent-ref %}

{% content-ref url="/pages/uqLgf1IUouTh8TwpXOJn" %}
[이메일 상세 통계](/email/analytics/email-detailed-statistics.md)
{% endcontent-ref %}


---

# 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://help.stibee.com/email/analytics.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.
