Data Structure

Structure and list of collected data

# Open Data Portal

Want to explore or download our data directly? Check out our Open Data portal.

Visit Open Data Portal

Players & Teams Structure

01. Players

Main Information

id

Unique identifier assigned to a player (Visible in URL)

handle

Username
Additional Information

first_name

First Name

last_name

Last Name

country_code

Country Code (FR = France, US = United States, etc.)

bio

Biography

socials

Social Media (Twitter/Instagram/Twitch/Youtube/TikTok)

vlr_id

Player's VLR ID

liquipedia_link

Link to the player's Liquipedia page
Confidential Information

discord_id

Discord ID (Private information, used to validate a player's identity when modifying their profile)

val_id

Riot ID (Private information, identified and assigned by our team from Riot match data, used to link match statistics with a player)

Link

Player_Team

player_id

Unique identifier for a player

team_id

Unique identifier for a team

role

Player/Coach/Manager/etc.

joined_at

Date joined the team

left_at

Date left the team

02. Teams

Main Information

id

Unique identifier assigned to a team (Visible in URL)

name

Team Name
Additional Information

country_code

Country Code (FR = France, US = United States, etc.)

website

Website

socials

Social Media (Twitter/Instagram/Twitch/Youtube/TikTok)

bio

Biography

vlr_id

Team's VLR ID

liquipedia_link

Link to the team's Liquipedia page

Each team/player must have a name and an identifier; other information is added by the team/player or by administrators via tournament data.
Players/teams have the right to modify/delete 'Additional Information'.

The val_id and discord_id are not displayed or shared. They are provided by the player via Discord.

Tournaments Structure

03. Tournaments

Main Information

id

Unique tournament identifier

name

Competition Name

region

World Region (EMEA, NA, etc.)

category

Tournament Category (e.g., Challengers, Game Changers)

status

Current Status (Upcoming, Live, Finished)
Additional Information

prize_pool

Total Prize Pool

location

Physical Location

start_date

Start Date

end_date

End Date

vlr_id

data.tournaments.vlr_id

liquipedia_link

Link to the tournament's Liquipedia page

04. Tournament_phases

Technical Structure

name

Phase Name (e.g., Playoffs, Group A)

format

Game Mode (e.g., Single Elimination, Round Robin)

order

Phase display order

parent_id

Link to a parent phase (for subgroups)

Participants

Tournament_Teams

List of teams registered for the event

Each tournament must have an identifier, a name, dates, a region, a category, and a status. They are collected by our team or upon request during a tournament addition request.

Matches Structure

05. Matches

tournament_id

phase_id

round_number

round_name

match_order

team_a_id

team_b_id

scheduled_at

status

team_a_score

team_b_score

best_of

patch

06. Match_Vetos

match_id

team_id

map_name

type

order

07. Game_Maps

api_match_id

match_id

map_name

team_a_score

team_b_score

order

is_completed

08. Game_Player_Stats

match_id

game_map_id

player_id

team_id

agent_name

kills

deaths

assists

acs

adr

kast_percentage

first_kills

first_deaths

headshot_percentage

09. Game_Player_Advanced_Stats

game_map_id

player_id

agent_name

clutch_1v1_won

clutch_1v1_total

clutch_1v2_won

clutch_1v2_total

clutch_1v3_won

clutch_1v3_total

clutch_1v4_won

clutch_1v4_total

clutch_1v5_won

clutch_1v5_total

multikill_2k

multikill_3k

multikill_4k

multikill_5k

trade_kills

traded_deaths

plants

defuses

pistol_won

pistol_played

eco_won

eco_played

force_won

force_played

full_buy_won

full_buy_played

post_plant_won

post_plant_played

atk_rounds

atk_rounds_won

atk_kills

atk_kast_percentage

def_rounds

def_rounds_won

def_kills

def_kast_percentage

10. Game_Map_Rounds

game_map_id

round_number

winning_team

win_type

11. Game_Map_Round_Player_Stats

game_map_round_id

player_id

kills

assists

score

economy_spent

economy_remaining

weapon_id

armor

We collect a lot of match information to provide detailed statistics. We retrieve:
- Basic match information (Mandatory)
- Match vetos
- Played maps, with results, stats and advanced stats (in a separate maps dataset, referenced by map id)
- Each round's result (Who wins, and how)
- Each player's stats per round (KDA/Economy/Weapon/Armor/etc)

These stats are not always collected, but we strive to obtain them to display the most complete statistics possible.

News Structure

12. News

Main Information

id

Unique news identifier (Visible in URL)

author

Author name

title

News title

content

News content
Additional Information

status

News status (draft/published/archived)

is_featured

Whether news is displayed on the homepage

published_at

Publication date

Link

news_relations

Link between news and a tournament/team/player, allows display on profile.

Each news item must have an identifier, a title, content, and an author.

The status is hidden but allows for display (Draft = In progress, Published = Visible on site, Archived = Hidden on site but accessible via API).

Other Data Structure

13. Page_views

Main Information

uri

Page URL

viewed_at

Time of viewing

count

Number of views

We store the number of visits per page per hour; we do not store who visited, from which region, or the exact time.

This data is stored and private. It is never shared; we use it to visualize site usage and adapt our infrastructure as needed.