Must-have Analytics Events

The three methods must be implemented into games before launching on Pley, as the commercial funnel analytics depend on them. These should preferably be implemented to fire only once per game session. These events are available to send to the analytics service of your choice through our Playable API (read more here).

Through the Pley SDK in the game code, you can trigger gameplay and player behavior-related events.

1. Use Pley.AnalyticsKit method to trigger analytics events in the game code, providing the correct data to the method.
2. Fire the three mandatory events through the Pley SDK's analytics kit (example below).
3. Fire all gameplay events relevant to your game to the game code (see all events here).
4. Optional: Catch the events through the game site which has the Web Playable embedded on it, and send them to the analytics service of your choice. (Read more here)

Example:

//Initialize analyticsKit with player properties
Pley.AnalyticsKit.Initialize(config);

//Example of how to fire an event
PleyResult result = Pley.AnalyticsKit.GameLoaded();

if (result != PleyResult.OK)
{
Debug.LogError("Failed to fire Pley analytics event game_loaded.");
}

/////////////////////////////////////////////////////////////////////////

//Example of how to fire an event with parameters
int playerLevel = 3;
PleyResult result = Pley.AnalyticsKit.LevelAdvanced(playerLevel);

if (result != PleyResult.OK)
{
Debug.LogError("Failed to fire Pley analytics event level_advanced");
}

game_load_started

No implementation.

Triggers as soon as the loading begins (before the game code begins to execute). This occurs after the "start"-button is clicked or the game automatically starts.

playable_loaded

No implementation.

Triggers when the Web Playable completes its initialization. When playable_loaded fires, the game takes over and continues loading. Web Playable is loading in necessary assets (cached or downloaded) for the game and game engine to launch.

game_loaded

Called from within the game code.

AnalyticsKit.GameLoaded(); should be called whenever the game finishes the initial loading, and the game is interactable for the player. Simply call this method whenever the loading screen is complete.

game_user_interacted

Called from within the game code.

AnalyticsKit.UserInteracted(); should be called whenever the player takes their first meaningful action in the game, such as clicking a button or taking their first game action. This is often game-specific. Recommended places are:

• User harvest a resource.
• User clicks a game button.
• User moves the camera.
• User starts a level.

game_user_engaged

Called from within the game code.

AnalyticsKit.UserEngaged(); should be called whenever the user is considered engaged. This event is up to each game studio themselves to define. Recommended places are:

• Default: The user plays the game for 5 minutes without a break longer than 15 seconds.
• User completes a level.
• User completes a tutorial.
• User gains a level or buys an upgrade.
• User plays for 5 minutes.