Platform Concepts
TRACKTICS organizes all data around a hierarchy of clubs, teams, players, trackers, and sessions. Understanding this model is the foundation for working effectively with the API.
Overview
Club
├── Roles (access control for users)
├── Teams
│ └── Players (members of the team)
├── Players (all players of the club)
├── Trackers (GPS devices belonging to the club)
│ └── Player association (which tracker a player is currently wearing)
└── Sessions (training sessions and matches)
└── Markers (in-session events: goals, fouls, etc.)
Club
A club is the top-level entity in TRACKTICS. Everything — players, trackers, sessions, and team structures — belongs to a club.
Clubs are created and managed by the TRACKTICS team. To obtain a club account, contact info@tracktics.com.
Each club has:
- A unique club ID (UUID)
- A display name
- A set of roles that govern what users can do within the club (see Roles below)
Teams
A team is a named group within a club. Clubs typically operate multiple teams (e.g., first team, U17, U19, women's team).
Teams are used to organize players and filter session statistics by squad. A player can be a member of multiple teams.
Players
A player is an athlete registered to a club. Players are independent of teams — they are added at the club level and then optionally assigned to one or more teams.
Each player has:
- A unique player ID
- A name and optional avatar
- Membership in zero or more teams
During a session, a player can be paired with a tracker device so their GPS position data is captured and attributed to them.
Trackers
A tracker is a physical GPS device that records a player's position in real time. Trackers are registered to a club and can be re-assigned between players across sessions.
Key characteristics:
- Each tracker has a unique tracker ID and a human-friendly name (e.g., "Tracker 01")
- A tracker is associated with a player inside a session to link position data to that player
- Multiple trackers can be active simultaneously in a single session
The association between a tracker and a player is managed per session: before a session starts, coaches assign which tracker goes to which player.
Sessions
A session represents a single training session or match. All position data and event markers are recorded within the context of a session.
Sessions belong to a club and can optionally be linked to a team. A session captures:
- Start and end times
- Real-time GPS position data — streamed live via the WebSocket API and stored for replay
- Markers — discrete in-session events such as goals, fouls, or coach annotations, each with a timestamp and position
Position data can be accessed live during an active session via WebSocket, or historically via the REST API after the session has ended.
Roles
Access to a club is controlled through roles. A user's role within a club determines what they are permitted to read or modify.
| Role | Permissions |
|---|---|
club admin | Full access: manage club settings, users, players, trackers, and sessions |
club editor | Create and modify players, trackers, teams, and sessions; cannot manage users or club settings |
club viewer | Read-only access to club data, sessions, and position history |
A single user can hold multiple roles simultaneously (e.g., club admin and club editor).
To request role changes or to invite additional users to your club, contact info@tracktics.com.
Putting it together
A typical workflow looks like this:
- Your club is provisioned by TRACKTICS and you receive login credentials.
- You create teams and players within your club.
- Before each session you associate trackers with players.
- You start a session — live position data begins flowing over the WebSocket.
- Coaches create markers (goals, highlights) during the session.
- After the session ends, you retrieve position history and markers via the REST API for analysis.