> 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.md).

# Analytics

Welcome to the Analytics section of the LionSDK documentation. As one of the key features of LionSDK, our analytics tools empower you to track, analyze, and optimize the performance of your mobile games. By leveraging comprehensive data collection and analysis, you can gain deep insights into player behavior, game progression, and monetization strategies.

#### Key Features:

* **Data Filtering and Validation**: Manage and filter the most relevant events, ensuring you focus on critical data points. Use robust validation tools to ensure the accuracy and reliability of your data, providing confidence in your analytics and decision-making processes.
* **Event Tracking**: Monitor a wide range of in-game events, from game starts and progression milestones to monetization activities and social engagements. Detailed tracking helps you understand player interactions and optimize gameplay experiences.
* **Comprehensive Event Categories**: Track various types of events, including game progression, economy interactions, monetization activities, and social engagements. This holistic approach allows for a detailed understanding of all aspects of your game.
* **A/B Testing**: Conduct experiments to test different game elements and strategies, enabling data-driven decisions to enhance player engagement and retention.

#### Benefits:

* **Deep Insights**: Gain a comprehensive understanding of player behavior and game performance, enabling informed decision-making.
* **Optimization**: Identify areas for improvement and optimize game design, progression, and monetization strategies based on detailed analytics.
* **Data-Driven Decisions**: Leverage robust data collection and analysis to drive your game's success and enhance the player experience.

Explore each subsection to learn how to implement and make the most of LionSDK’s analytics features, and take your game to the next level with data-driven insights.

{% hint style="warning" %}
Before proceeding, please request an Event Specs document from us. This document contains only the necessary events for your game. Not all projects require deep analytics; it depends on the game's stage. We aim to ensure that the game only triggers necessary events with correct parameters and logic. If you have already received such a document, welcome to the analytics section of the documentation!
{% endhint %}

[Progression Events](/readme/analytics/progression-event.md)

[Economy Events](/readme/analytics/economy-event.md)

[Monetization Events](/readme/analytics/monetization-event.md)

[Interaction Events](/readme/analytics/interaction-events.md)

[Social Events](/readme/analytics/social-events.md)

[Debug Events](/readme/analytics/debug-events.md)

[Other events](/readme/analytics/other-events.md)

[Custom Events](/readme/analytics/custom-events.md)

***

[Validation](/readme/analytics/validation.md)

[A/B Testing](/readme/analytics/a-b-testing.md)

[API](/readme/analytics/api.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 current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://lionstudios.gitbook.io/readme/analytics.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.