Documentation Index

Fetch the complete documentation index at: https://docs.xtremepush.com/llms.txt

Use this file to discover all available pages before exploring further.

Leaderboards

Prev Next

Overview of leaderboards and a comparison of different leaderboard scoring types

Leaderboards create competition between users by ranking them against each other based on a score, and rewarding top performers. They're a good way to drive engagement around a specific action or metric over a set period.

Some examples of leaderboards include the following:

  • A weekly leaderboard that ranks users by how many qualifying bets they place.

  • A VIP-only leaderboard that ranks users by their total lifetime deposits.

Leaderboards Overview

Leaderboards represent a user's rank relative to other users, based on a score you define. Unlike levels, which reflect a user's permanent status, or quests, which reward one-off actions, leaderboards continuously rank users against each other over a period of time, and rewards can rotate at set intervals.

There are three types of leaderboard scoring you can configure:

  • User Attribute value: Users are ranked in leaderboards based on a user attribute value, like total_tokens_won.

  • +1 with every event: Users are ranked based on the number of times they trigger an event. For example, if you select the bet_executed event, a user's score increases by 1 every time they place a bet, and users are ranked by their total score.

  • Accumulative (by event field): Users are ranked based on the sum of a numeric field from an event. You specify an event, and then specify the path inside that event for the field you want to accumulate. For example, if your selected event is bet_executed and the field is amount, then users are ranked on the leaderboard based on the amount added up across every bet they place.

The following table compares the different leaderboard scoring types.

User Attribute value

+1 with every event

Accumulative (by event field)

Based on

The current value of a user attribute

How many times a user triggers the event

The total value added up from a field in the event

Requires a Desired Action (event)

No

Yes

Yes

Resets on rotation

No, since it reflects a live attribute value

Yes

Yes