Ownership Topology Dataset

The Publisher Ecosystems Dataset

A graph of game nodes and shared-ownership edges, derived from real player libraries across five publishers.

30 sampled players|18 game nodes|76 overlap edges|3 organic clusters

Overview

What You Get

An ownership-topology graph: game nodes connected by shared-owner edges, with derived graph-centrality scores and organically detected clusters.

This sample is a curated five-publisher cut. It demonstrates the structure — it is not full-market coverage.

18

Game nodes

76

Overlap edges

1,448

Ownership edges

3

Organic clusters

Structure

Game-Node Schema

Each node is a game carrying ownership counts and derived graph-centrality scores.

FieldTypeDescriptionExample
idstringInternal game identifier73072
titlestringGame titleSurviving Mars
publisherstringPublishing companyParadox Interactive
sample_owner_countintPlayers in the sample who own this game25
connectivity_scorefloatNormalized count of overlap edges (0.0 to 1.0)0.93
proximity_scorefloatNormalized closeness to other games in the graph0.94
authority_scorefloatNormalized influence within the game's cluster1.00
cluster_idstringOrganic cluster this game belongs toCluster 3
steam_app_idstringSteam application identifier464920

Relationships

Overlap-Edge Schema

Each edge connects two games co-owned by players in the sample.

FieldTypeDescription
source_game_idstringFirst game in the co-owned pair
target_game_idstringSecond game in the co-owned pair
shared_sample_ownersintPlayers in the sample who own both games
jaccard_samplefloatJaccard similarity of the two owner sets
same_publisherboolWhether both games share a publisher

Preview

Sample Nodes

Representative game nodes from the sample, ranked by owner count.

idtitlepublishersample_owner_countconnectivity_scorecluster_id
73072Surviving MarsParadox Interactive251.00Cluster 3
78458Cities: SkylinesParadox Interactive240.93Cluster 3
26524Golf With Your FriendsTeam17200.72Cluster 1
73862DredgeTeam17200.71Cluster 1
73088Overcooked! 2Team17200.76Cluster 2
77866BlasphemousTeam17190.68Cluster 1
84466Crusader Kings IIParadox Interactive190.80Cluster 1
4338AutomachefTeam17170.64Cluster 2

Definitions

Derived Signals

Graph-centrality measures computed from the overlap topology.

SignalRangeWhat It MeasuresInterpretation
connectivity_score0.0 to 1.0Overlap-edge count per nodeHow many other games share owners with this one.
proximity_score0.0 to 1.0Graph closeness centralityHow central a game is across the whole topology.
authority_score0.0 to 1.0Within-cluster influenceHow strongly a game anchors its own cluster.
jaccard_sample0.0 to 1.0Owner-set overlap ratioEdge strength independent of raw popularity.

Methodology

How The Graph Is Built

Player libraries are intersected pairwise across games. Every pair of games co-owned by enough sampled players becomes a weighted overlap edge.

Clusters are detected from the edge topology alone — community detection on the overlap graph, with no genre or publisher labels supplied as input.

Connectivity, proximity, and authority scores are normalized to a 0.0–1.0 range within the sample, so nodes stay comparable regardless of absolute popularity.

FAQ

Common Questions

Is this full-market data?

No. It is a curated five-publisher sample chosen to demonstrate the topology. Production datasets cover the full catalog.

How are clusters defined?

Purely from shared-ownership structure. Community detection runs on the overlap graph; genre labels are applied afterwards, never as input.

What does an edge mean?

An edge means players in the sample own both games. Its weight is the count of shared owners, normalized by Jaccard similarity.

Can we join it to our own data?

Yes. Game nodes carry Steam application IDs, so the graph joins cleanly onto first-party catalog and ownership data.

This sample is the surface of the ownership graph.

The full dataset maps the publisher ecosystem at scale.

Access is granted under a written data-use agreement. Samples may include a representative slice across all four layers depending on buyer use case, coverage requirements, and approval status.

We never sell or share this form data. See the Privacy page for details.