Skip to main content
Playtest types determine how many gameplay sessions each player completes during a playtest. Userplay supports three playtest types, each designed for different testing goals.

Playbooks

Single session

One sitting, one survey. First impressions or a feature check.

Multi session

Players come back a few times. Watch a first impression change.

Longitudinal

Sessions spread across days. Retention and habit formation.

Survey only

Hand out a build, ask questions, record nothing.

Compare playtest types

Single Session is a one-time test. Play once, answer a survey, done. There is no cooldown to set. Multi Session brings players back a few times with breaks in between. It works well for a build that needs several short passes, like a tutorial on the first visit and a later level on the next. Longitudinal spreads sessions across days. It works well for retention questions: does a progression system still feel rewarding on the fourth visit?

Session cooldowns

Multi Session and Longitudinal playtests both support between two and six gameplay sessions. The difference between them is how much time players wait between sessions. Configure a session cooldown to control when players can start their next session. Short cooldowns encourage players to complete sessions close together, while longer cooldowns spread gameplay over several days.

Session cooldowns

Learn how session cooldowns work and when players become eligible for their next session.

Multi session

Players come back a few times. Watch a first impression change.

Changing the session count

The number of gameplay sessions is fixed for Single Session playtests and configurable for Multi Session and Longitudinal playtests. To change it:
  • Open the Playtest tab.
  • Find the Number of Sessions setting.
  • Choose between 2 and 6 sessions.
You can only change the session count while a playtest is still in draft.
Lowering the session count doesn’t delete any existing content. If you increase it again later, previously configured session briefings, objectives, and surveys are restored.

What the session count affects

Changing the session count affects several parts of your playtest:

Publishing

Learn how publishing reserves recorded gameplay sessions.

Session content

Configure briefings, objectives, and surveys for each session.
The number of sessions affects how many recorded gameplay sessions are reserved when you publish. Make sure you’ve chosen the correct session count before publishing, as it cannot be changed afterward.

Session timing

The minimum duration and cooldown that sit next to the count on the same tab.

Run a multi session playtest

Playbook: two to six sittings per player, with a cooldown between them.

Run a longitudinal study

Playbook: retention research that runs across days or weeks.

Check what a playtest will cost

If you want to see what a higher count does to the reservation before committing.