Skip to main content
Requiring Steam as an identity provider proves each player has a real Steam account before they join. Combined with the Steam integration, it feeds playtime, ownership, and wishlist signals into every player’s profile. This playbook covers connecting Steam, requiring it, handing out keys, and reading the signals back.

Take the guided tour

Connect Steam to your studio, from the publisher key to the App IDs.

What you need first

  • The Admin role, to connect Steam under Integrations.
  • Your Steam App IDs (up to four).
  • A Steamworks publisher Web API key, if you want ownership data. Playtime and wishlist work without one.
  • Steam keys, if you plan to distribute them.

The playbook

1

Connect Steam

Go to Integrations and click the Steam card. Add your App IDs and, optionally, your publisher Web API key.

Tracked apps

The four slots and what removing them all does.

Publisher key

What it unlocks and how a rejection behaves.
2

Require Steam identity

In the playtest editor, open the Onboarding tab and click the fingerprint button. In the Identities modal, switch Steam on.

Identity

The four providers and how to choose what to require.

Onboarding

The tab this modal lives on, and the screen that runs before it.
3

Enable key distribution

If you are handing out Steam keys, open the Config tab and set Key Distribution to Enabled. On the Keys tab, load your keys.

Key distribution

The limits, and how the vault relates to the playtest.

Stock a key vault

Playbook: pick the Steam variant before you load anything.
4

Configure the rest of the playtest

Type, access, build, survey, and recording are all independent of identity and keys.
5

Publish

Click Publish in the editor header and confirm.
6

Read the signals

As players join, open Players and click a player’s row. The detail sheet shows a Steam section with playtime, ownership, and wishlist data.

Steam insights

Ownership, playtime, and wishlist signals per player.

See who your players are

Playbook: read the same signals across your whole directory.
7

Force a refresh

If the signals look stale, open the overflow menu on the Players page, click Steam connection, and hit Refresh.

How you know it worked

  • Your playtest lists Steam among the identities it requires.
  • A player who signs in has a Playtime row on their detail sheet.
  • The Ownership row appears if you attached a publisher key. It reads Owned, Not owned, or Family shared.
  • A player who has not linked Steam sees the Steam identity step and cannot skip it.
  • The Analytics tab on the Players page shows aggregate Steam coverage.

Steam integration

Connecting, adding App IDs, and the publisher key.

Identity

The four providers and how to choose what to require.

Steam insights

Ownership, playtime, and wishlist signals per player.

See what players own and play on Steam

The signals playbook without the identity requirement.

Run a single session playtest

Playbook: the full setup this one only adds Steam to.

Keep Steam data fresh

Playbook: re-sync the signals when they start looking stale.