2. Automatic logs

Currently, the SDK has 2 logs that are automatically implemented:

• RetentionLog: player retention statistics, processed through the RetentionCounter class.

• UserTotalTimeLog: statistics of the player's total game time per play, processed through the TotalUserTimeCounter class.

1. RetentionCheckService

• Make a log call once a day when the player logs in, the player's retention is calculated by subtracting the current date from the first login date (For example, the player is entering for the first time on March 2, quitting the game on March 3 and March 4, then logging in again on March 5, then a player's retention on March 5 will be calculated as 5-2 = 3).

Note:

• Retention information is stored on the player's local machine and is lost if the player uninstalls the game.

• For games that have just integrated the SDK for the first time, all old devices when updated will be counted as retention = 0 because there is no data on the device to calculate. It will take a fair amount of time for the data to stabilize (about 1 week).

• If you want to change the player retention count, refer FPlayerInfoRepo

VD:

Debug.Log("Retention of the player is: " + RetentionCheckService.Retention);
if(RetentionCheckService.RetentionChanged) {
        Debug.Log("This is the player's first login of the day");
} else {
        Debug.Log("This isn't a player's first login of the day");
}
Debug.Log("The player's first login date is: " + RetentionCheckService.FirstLoginDate);

2. PlayTimeCheckService

• Perform a count of the player's total playing time in 1 playthrough, the game time counting does not count the amount of time the player exits the game window (when the player presses the home/app overview button on the phone).

• The player's current session playtime will be loaded and sent at the beginning of the player's following login session, i.e. playing time in the last session of the player lifecycle will not be recorded.