Progression Event

Introduction

Progression events are crucial for understanding how players move through and engage with your game. By tracking these events, you can gain insights into player behavior, identify areas where players may struggle, and optimize game design to enhance player experience and retention.

In mobile games, it's common to have core gameplay and additional activities. We use mission events to track main progression, side activities such as challenges, side quests, and paid levels. Our data analysts will provide specific instructions tailored to your game.

Previously we had level events, but due to repetitive parameters with mission events, we decided to mark them as deprecated. However, developers do not need to worry about refactoring their existing code. On the server side, we will convert level events to mission events to support old events and games with the new analytics framework.

Game Events

GameStarted

This event is triggered automatically upon Lion Core initialization to track the total number of game sessions, providing a basis for measuring player engagement.

FeatureUnlocked

Use this event when a player unlocked a level, item, badge, level, skills or anything else.

Mission Events

Events

MissionStarted

Use this event when a player starts a mission.

Note: Ensure that you fire the mission_start events only after LionSDK initialization. Failing to do so can lead to incorrect funnel and retention analysis.

MissionCompleted

Use this event when a player successfully completes a mission.

MissionStep

Use this event when a player reaches a significant step or checkpoint within a mission.

MissionAbandoned

Use this event when a player abandons a mission before completion or presses the restart button.

MissionFailed

Use this event when a player fails a mission.

Main Parameters

Both level and mission events share similar parameters:

  • missionID: Identifier for the level or mission.

  • missionAttempt: Count of attempts for the level or mission.

  • missionType: Type of mission.

  • missionName: Name of the mission.

Event Categories

Each mission should have opening and closing events. Intermediate events are optional:

Opening Events

  • MissionStarted: Marks the beginning of a new level or mission attempt.

Intermediate Events

  • MissionStep: Indicates a significant step or checkpoint within a level or mission.

Closing Events

  • MissionCompleted: Signifies the successful completion of a level or mission.

  • MissionAbandoned: Indicates the player left the level or mission without completing it.

  • MissionFailed: Marks the end of a level or mission attempt with an unsuccessful outcome.

Event Implementation Flow

Ensure the parameters in opening, intermediate and closing events are consistent to match these events and calculate metrics on the server.

  1. Opening Event: Each level or mission should start with an opening event.

  2. Intermediate Events: Track significant steps or checkpoints within the level or mission.

  3. Closing Event: Finish with a closing event unless the player quits or closes the app.

Handling Attempts

Increment the attempt parameter each time you fire a MissionStarted event.

Edge cases will be analyzed and provided in the event specifications after discussions with developers.

By effectively tracking these progression events, you can gain valuable insights into player behavior and make data-driven decisions to improve your game design and player retention.

PreviousAB Test Tips (Experiment Best Practices)NextEconomy Event

Last updated