Playbooks
Run a survey
Create it, publish it, and read the responses.
See what players own and play on Steam
Read Steam ownership, playtime, and wishlist signals alongside the answers.
What the analytics show
Charts vary with the question type. Choice questions render as bar lists, range ratings as distributions, and text inputs list the verbatim answers.
There is no eligibility breakdown here. Surveys accept everyone who submits, so there is nothing to split. Waitlist analytics does show one.
Removing someone from the roster
You can remove a respondent individually or several at once. Removing them:- Takes them off this survey’s roster.
- Leaves them in your studio’s player directory.
- Does not block them. They can respond again through the same link.
You cannot add people by hand
A survey roster fills from one place only: people opening your survey link and submitting. Neither the studio nor the API will write to it directly. If you want a roster you curate yourself, build a player group and add people there.Getting the data out
Survey responses leave Userplay through the public API or the CLI, both of which read surveys and their responses.Related articles
Player groups
The roster a survey fills, and what else you can do with it.
Survey questions
Determines what the charts can show.
Archiving a survey
Pull what you need out first.
Tell respondents what happens next
Playbook: tell respondents what their answers changed.