SteamStats docs
These pages explain how SteamStats works in practice: connecting a Steamworks financial key and traffic reports, how often each source refreshes on each plan, how the forecast is built, how days are counted in your time zone, and how trials, billing and team access work. Each page starts with a short answer.
Last reviewed · SteamStats team
- Connect SteamworksCreate a Steamworks Financial API key, add it to SteamStats and get wishlist and sales reports on your plan's schedule, with history backfilled from Steam.
- Connect trafficSend Steamworks traffic, UTM, refund and wishlist cohort reports to SteamStats with the browser extension or a service account with one permission.
- Data freshnessRefresh intervals for wishlists, sales, reviews, players, Community Hub, followers and store visibility on every SteamStats plan, plus the launch window.
- Forecast methodHow SteamStats forecasts net to studio over any horizon: Low, Expected, High and Viral, learning daily from your sales, planned discounts and kept past runs.
- Day definitionSteamStats counts every day from midnight in your organization's time zone, across charts, tables, exports and alerts. How Steam's own days fit in.
- Billing and beta accessHow SteamStats billing works: one price per tracked game, free access for invited studios in the beta, Radar free, and Paddle as merchant of record.
- Team and seatsEvery SteamStats plan has unlimited seats. How owners, admins and members differ, how invitations work and what happens when someone leaves the team.