Analytics
How your game is doing, day by day, from page views to play time. Anonymous counts, so you see what players do but never who they are.
The Analytics tab on each game in the dashboard shows how players find, get and play it. The numbers are counts per day. Depot doesn't track individual players for them, and you never see who did what.
What you see
- Page views and visitors on the game's store page, and the sites visitors came from (the domain only, such as
reddit.com). - How players got it: purchases, free claims, key redemptions and grants. These come from your own records, so they're exact.
- Installs and updates finished in the Depot launcher.
- Launches, players and play time, and which build players are on.
- Countries and platforms.
- Revenue after refunds, per currency. The Sales page has every order.
Numbers update every night (UTC). rolled_up_through in the API is the last day included.
Small numbers are hidden
A count under 5 shows as <5 (or null in the API). Otherwise, with three testers, you could work out what one person did. Purchases, claims, keys and grants aren't hidden: you already see each one.
How it's counted
- The launcher reports finished installs and updates, launches, and how long each session lasted. Players can turn this off in the launcher's Settings, and then nothing is sent.
- The store page counts views on Depot's servers. Crawlers aren't counted.
- Unique visitors and players are counted with a key that changes every day (and every month, for monthly players) and is deleted afterwards. Nothing in the stats can be tied back to a person, including by Depot.
- Your game doesn't report anything. You don't need the SDK for analytics.
From the API, CLI or an agent
curl -H "Authorization: Bearer $DEPOT_TOKEN" \
"https://api.depot.games/v1/organizations/my-studio/games/my-game/stats?from=2026-11-01&to=2026-11-30"GET /v1/organizations/{org}/stats gives every game's totals. Both need the analytics:read permission, which owners, admins and publishers have. An API key needs it granted. An agent connected over MCP can read them with depot_get_stats.