Skip to main content
A published waitlist gives you two things back: the roster of everyone who joined, and the analytics behind it. Analytics profiles those people, charts their answers, and shows how many the eligibility rule accepted. Both appear once you publish.

Playbooks

Screen waitlist signups

Write the questions and the rule that decides who gets in.

See what players own and play on Steam

Read Steam ownership, playtime, and wishlist signals alongside the answers.

What the analytics show

Check the eligibility breakdown first. A rule declining most of your traffic is either doing its job or is stricter than you meant, and this is the only place that tells you which.
With questions turned off there is nothing to chart, so you get the player analytics on their own.

Removing someone from the roster

You can remove a player individually or several at once. Removing them:
  • Takes them off this waitlist’s roster.
  • Leaves them in your studio’s player directory.
  • Does not block them. They can sign up again through the same join link at any time.

You cannot add people by hand

A waitlist roster fills from one place only: people opening your join link. Neither the studio nor the API will write to it directly. For a roster you curate yourself, build a custom player group instead.

Turning the roster into a playtest

Add the waitlist’s group to a playtest from that playtest’s roster. Members copy across as ordinary players, and the waitlist keeps its own roster unchanged.

Waitlist questions

Determines what the charts can show and who the rule lets through.

Player groups

The roster a waitlist fills, and what else you can do with it.

Archiving a waitlist

Copy the people you want to keep out first.

Screen waitlist signups

Playbook: build the rule that sorts eligible from not.