/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Steam Spy now operating in a limited capacity as it switches to a new algorithm after Valve's changes to the Steam Web and Store API

What happened?  —  As you might know, on 11th of April, 2018 Valve has made changes to their Steam Web API, removing owned games from user's information, unless they actively opt-in.

Steam Spy Sergey Galyonkin

Context & Ripple Effects

Steam Spy had shut down entirely on April 11 after Valve's API change stopped exposing users' owned games by default, cutting off the public data the sales-estimation service was built on. Two weeks later it is back, running a new algorithm in a limited capacity against whatever data remains accessible through the Steam Web and Store API.

The episode sits alongside earlier account-privacy lapses at Valve, including the 2015 caching bug that let users view others' profile pages, which pushed the company toward locking down what its APIs expose about individual accounts.

First-order effects

  • Steam Spy's sales and player-count estimates now cover less of the Steam catalog and rest on a smaller sample, so developers and publishers who used the service for market sizing get sparser, less precise numbers.
  • Valve's opt-in default means any third-party service built on scraping user libraries faces the same rebuild-or-die choice Steam Spy just made.

Second-order effects

  • Competing Steam analytics providers must either shift to opt-in data collection or accept shrinking coverage, concentrating reliable sales intelligence among services with direct developer relationships.
  • Developers lose an independent cross-check on how their own games sell relative to rivals, increasing dependence on Valve's own private reporting.

Third-order effects

  • If platform owners keep tightening default API access, third-party estimation services across gaming will consolidate around officially sanctioned data channels, and independent market transparency becomes something publishers pay for rather than scrape for free.
  • Privacy-by-default settings on user profiles set a template other game platforms can follow, raising the cost of building any analytics business on top of someone else's store.

The trend: Game platform owners are tightening default privacy and API access, forcing third-party analytics services to rebuild on opt-in data or fade out.