Playbooks
See what players own and play on Steam
Steam ownership, playtime, and wishlist signals.
Playtest with Steam players
Require Steam identity, hand out keys, and read back playtime.
Keep Steam data fresh
Tracked apps, key rotation, and what to do when Steam rejects a key.
Hand out game keys
Give each player a Steam key or a code of your own as they join.
Who can connect it
You need the Admin role or above to connect Steam.Integrations are available on every plan. Free studios can connect Steam exactly like paying ones.
Connect it
Two things to supply, and the second is optional. Steam never redirects you anywhere: you paste what Userplay needs.1
Add your App IDs
The Steam App ID for your game, so Userplay knows which apps to pull data for.
2
Add a publisher key, or skip
A Publisher Web API key from Steamworks. You can add one later.
Both halves have to be connected
Steam insights need your studio connected and the individual player’s Steam account linked. A player who signed in with email only carries no Steam data, however well your integration is set up.
To get the player half reliably, require Steam as an identity on the playtest, waitlist, or survey they arrive through.
Managing it afterwards
The Steam tab has three cards, one per thing you can change:
You can change any of them at any time, and refresh on demand rather than waiting for the nightly sync.
Disconnecting lives in the connection panel, which the Steam row of the integrations catalog also opens. It tears the whole thing down: insights disappear from your player directory and the stored key is deleted. Connecting again rebuilds everything on the next sync.
Related articles
Tracked apps
Up to four App IDs, and what removing them all does.
Publisher key
What it unlocks, and how to handle a rejection.
Player insights
Where the signals actually show up.
Roles and permissions
Members cannot connect an integration. Admins and owners can.