Skip to main content
Multi-session and longitudinal playtests let the same people answer the same questions more than once. Results groups those answers by session number, which is where the comparison lives.

What you need first

  • A multi-session or longitudinal playtest. A single-session playtest has nothing to compare.
  • Players who have completed more than one session. Until they have, every session tab but the first reads empty.

The playbook

1

Check how far people got

Open Results, and on Overview read Sessions / player and Played in Participation & engagement.If most players stopped after session one, you have a retention finding rather than a comparison.

Analytics

How responses and sessions are grouped by session number.

Run a multi session playtest

Playbook: the setup that produces more than one session to compare.
2

Compare the answers session by session

Open the Responses tab and scroll to Responses by question.Move through the Session 1, Session 2, and later tabs. Each one carries that session’s completed-session count, so you can see how many people the answers represent.

Post-session survey

Where these questions were written, and the per-session switch.

Read what players told you

Playbook: work a single session’s answers question by question.
3

Watch for questions that moved

A rating that climbs suggests something clicked on the second visit. A rating that falls usually means novelty carried the first session.Note the questions that moved. They are the ones worth pulling recordings for.
4

Compare the sessions themselves

Open the Sessions tab and use the same session tab strip on Session details.Duration and completion time per session number tell you whether later visits were shorter.
5

Watch one early and one late session

In Gameplay recordings on the same tab, open one session 1 recording and one from the last session, ideally the same player.Watching the same person twice is the clearest version of this comparison.

Reviewing a session

The panel beside the recording, and the playback modes.

Session timing

The cooldown that sets how far apart those two recordings sit.
6

Read the highlights across the arc

Filter highlights by category and look at what got marked early against what got marked late.Confusion in session one that disappears by session three is onboarding working. Confusion that persists is a design problem.

Highlights

Every category, and why generation requires video.

Highlight categories

What each category catches, so you know which arc to follow.
7

Export both sets

Use Export in the Results header and take Responses and Individual responses.Session numbers travel with the answers, so the comparison holds up outside Userplay.

How you know it worked

  • Responses by question shows a tab per session, and the completed-session count changes as you move between them.
  • Session details filters to one session number at a time.
  • You can name at least one question whose answers changed between the first and last session.

Playtest types

What multi-session and longitudinal playtests ask of players.

Analytics

How responses and sessions are grouped by session number.

Session timing

The cooldown that sets how far apart those sessions sit.

Run a longitudinal study

Playbook: set one up so the comparison is there to make.