> For the complete documentation index, see [llms.txt](https://developers-apps-in-toss.toss.im/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://developers-apps-in-toss.toss.im/documentation/sdk/domains-api/analytics.md).

# Analytics

화면 진입·노출·클릭 등 사용자 행동을 기록하고 분석하는 기능을 제공해요.

### API 목록

| API                    | 설명                      | 상세                                                                            |
| ---------------------- | ----------------------- | ----------------------------------------------------------------------------- |
| `Analytics.log`        | 앱에서 발생하는 이벤트를 기록해요      | [REFERENCE](/documentation/sdk/domains-api/analytics/analytics.log.md)        |
| `Analytics.screen`     | 화면 진입 시점의 분석 로그를 남겨요    | [REFERENCE](/documentation/sdk/domains-api/analytics/analytics.screen.md)     |
| `Analytics.impression` | 요소가 노출되면 분석 로그를 남겨요     | [REFERENCE](/documentation/sdk/domains-api/analytics/analytics.impression.md) |
| `Analytics.click`      | 터치나 클릭이 발생하면 분석 로그를 남겨요 | [REFERENCE](/documentation/sdk/domains-api/analytics/analytics.click.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 dynamically by asking a question.

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

```
GET https://developers-apps-in-toss.toss.im/documentation/sdk/domains-api/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 `build a script that syncs our docs to a CMS` 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.