> 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/monetization-event.md).

# Monetization Event

## Introduction

Monetisation events are crucial for understanding and optimizing how your game generates revenue. By tracking these events, you can gain insights into player spending behavior, ad interactions, and in-app purchases. This information is essential for maximizing your game's revenue potential and enhancing the overall player experience.

## Ad Events

### Core Ad Events

{% hint style="info" %}
To simplify the management of ad queries, rewards, and events, you can utilize the [Ads Module](/lionsdk-1.x-legacy-docs/ads.md).

This module handles interaction with adverts and automatically tracks the necessary events. **In brackets I have indicated which events are used under the hood of the module.**
{% endhint %}

Core ad events help track basic interactions with in-game advertisements. These events are essential for understanding player engagement with ads and optimizing ad placements for maximum revenue.

#### [**`BannerShowRequested`**](/readme/analytics/api/events/bannershowrequested.md)

Use this event to track when a banner ad is displayed to the player.

#### [**`InterstitialShow`**](/readme/analytics/api/events/interstitialshow.md)

Use this event to track when an interstitial ad is displayed to the player.

#### [**`RewardVideoShow`**](/readme/analytics/api/events/rewardvideoshow.md)

Use this event to track when a rewarded video ad starts playing.

{% hint style="info" %}
For more advanced ad tracking and detailed flow instructions, refer to our [Advanced Ad Documentation](/readme/analytics/advanced-ad-events.md).
{% endhint %}

#### [`RewardVideoCollect`](/readme/analytics/api/events/rewardvideocollect.md)

Use this event to track when a player collects a reward after watching a rewarded video ad. This event **includes a reward parameter**, similar to the [`EconomyEvent`](/readme/analytics/api/events/economy.md) event, which details the reward received by the player. As such, there is no need to fire a separate [`EconomyEvent`](/readme/analytics/api/events/economy.md) event for the reward.

### In-App Purchase Events

{% hint style="info" %}
**IAP Validation Module**: Using this module enhances the reliability of your in-app purchase tracking. For detailed instructions and implementation, refer to our [IAP Validation](/lionsdk-1.x-legacy-docs/purchasing/iap-validation.md) subpage.

This module handles IAPs purchases with validation and automatically tracks the necessary events. **In brackets I have indicated which events are used under the hood of the module.**
{% endhint %}

#### [`InAppPurchase`](/readme/analytics/api/events/inapppurchase.md)

The [`InAppPurchase`](/readme/analytics/api/events/inapppurchase.md) event tracks player transactions involving real money. This event is crucial for understanding player spending habits and optimizing in-app purchase offerings. The [`InAppPurchase`](/readme/analytics/api/events/inapppurchase.md) event inherits logic from the [`EconomyEvent`](/readme/analytics/api/events/economy.md) event, making it essential to understand the logic behind the [`EconomyEvent`](/readme/analytics/api/events/economy.md) event.

On the server side, we parse the [`InAppPurchase`](/readme/analytics/api/events/inapppurchase.md) event similar to the [`EconomyEvent`](/readme/analytics/api/events/economy.md) event with our economy pipeline.

**Product Types:**

* **Items**: Typically boosters / power-ups, and resources (common in idle games).
* **Virtual Currencies**: Includes soft and hard currencies like coins, gems, etc.
* **Real Currencies**: Represents real money transactions (USD, EUR, etc.). Include the following parameters for accurate tracking:
  * `realCurrencyType`: The currency code (e.g., USD, GBP, HKD, etc.). The value must use the ISO 4217 Currency Code for the location of the player.
  * `realCurrencyAmount`: The amount of currency received.

{% hint style="info" %}
For realCurrencyAmount, provide the currency’s actual face value. Lion Analytics then transforms this value into minor units. For example, for an IAP that costs $2.99 USD, provide:

* `realCurrencyType` = ‘USD’
* `realCurrencyAmount` = 2.99
  {% endhint %}

{% hint style="info" %}
Also we perform **currency conversion** in our data pipelines based on the values of realCurrencyType and realCurrencyAmount.
{% endhint %}

#### Other Monetization Events

#### [**`ShopEntered`**](/readme/analytics/api/events/shopentered.md)

Use this event to track when a player enters the in-game shop. This helps understand shopping behavior and optimize the shop layout and offerings.

#### [**`ProductViewed`**](/readme/analytics/api/events/productviewed.md)

Use this event to track when a player views a product in the in-game shop. This event provides insights into player interest and can help in optimizing product placements and promotions.

***

[📺 Advanced Ad Events](/readme/analytics/advanced-ad-events.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/monetization-event.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.