> For the complete documentation index, see [llms.txt](https://lionstudios.gitbook.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://lionstudios.gitbook.io/readme/analytics/interaction-events.md).

# Interaction Events

## Introduction

Interaction events are crucial for understanding how players interact with the user interface and various elements within your game. By tracking these events, you can gain insights into player behavior, user interface efficiency, and overall user experience. This information is essential for optimizing the game's design and improving player engagement.

## Events

#### [**`UiInteraction`**](/readme/analytics/api/events/uiinteraction.md)

Use this event to track interactions with the user interface, such as button clicks, menu selections, and other UI elements. This event helps you understand which UI elements are most frequently used and how players navigate through your game’s interface.

#### [**`Options`**](/readme/analytics/api/events/options.md)

Use this event to track when a player opens the options menu. This event helps you understand how often players access game settings and which settings they modify.

#### [**`NotificationOpened`**](/readme/analytics/api/events/notificationopened.md)

Use this event to track when a player receives or interacts with a notification. This event helps you measure the effectiveness of in-game notifications and their impact on player behavior.


---

# 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://lionstudios.gitbook.io/readme/analytics/interaction-events.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.