Skip to main content
Longitudinal spreads a player’s sessions over days instead of minutes. It starts at 5 sessions and accepts any count from 2 to 6, the same range Multi Session offers. The setup is the same too. What separates the two is the cooldown: hours or days rather than minutes.

What you need first

  • A build that stays reachable for the whole window. Players launch it days apart, so a build link or key that expires mid-study cuts the study short.
  • A session count and cooldown you can wait out. Five sessions with a 24-hour cooldown means at least four days per player.
  • Enough recorded gameplay sessions for cap (or roster) times count. Check the Credits card under Settings > Billing.

The playbook

1

Create the draft as Longitudinal

Open Playtests in the sidebar.
  • Click Create playtest.
  • Choose the Longitudinal card, then click Continue.
  • Set the name, the Minimum Session Duration, and a Session Cooldown.
  • Click Save Draft.
2

Set the session count

On the Playtest tab, click Number of sessions and drag the slider between 2 and 6. It defaults to 5.
The card is draft only, and every per-session editor is sized by this number.
3

Set a cooldown in hours or days

Click the Session cooldown card on the same tab, then pick a unit and a value.
12, 24, 48, and 60.
This single setting is what spreads the study out over time.

Playtest types

What separates Longitudinal from Multi Session, and what each one fixes.

Run a multi session playtest

Playbook: the same setup with the gap measured in minutes.
4

Decide who gets in

Open the Playtest Access card on Overview and set Access and Player Count.
A week-long study is easier to follow up when you have a roster you seeded, but open works too.

Access

Open and closed modes, and what each one changes about the roster.

Build a group you can reuse

Playbook: seed the roster you will want to follow up with.
5

Give players something to play

On the Config tab, in the Playtest Settings card:
  • Set Build Distribution or Key Distribution to Enabled.
  • Click Save.
6

Write a briefing that changes over time

On Config, set Session Briefing to Enabled, then use the session picker on the Briefing tab.Day one teaches, day four asks what stuck.
Briefing content never freezes, so you can still fix a later session’s wording after you go live.

Session briefing

What a briefing can hold, and why it stays editable after publish.

Brief players and set objectives

Playbook: point day four somewhere day one never went.
7

Ask the same question every session

On Config, set Session Survey to Enabled, then write one survey per session number on the Survey tab.Repeating a question across sessions is what lets you watch the answer move.
Questions freeze at publish. Write them all first.

Post session survey

The per session editor, and exactly what the freeze covers.

Write survey questions

Playbook: word a repeated question so the answer stays comparable.
8

Preview, then publish

Click Preview in the editor header, then Publish.
Publishing reserves the whole study up front: cap (or roster) times session count.

How you know it worked

  • Your session cooldown reads in hours or days rather than minutes, for example 24 hours.
  • The results Sessions tab shows a player’s sessions landing on different calendar days, spaced by the cooldown you set.
  • Submissions holds players at In Progress until their last session lands. A player who stops coming back stays there. That drop-off is a retention finding on its own.
  • Answers to a repeated survey question shift between session numbers on the Responses tab of results.

Session timing

Has the full cooldown table and explains why the setting is one value for the whole playtest.

Run a multi session playtest

The same shape with gaps measured in minutes.

Work out what to fix next

Playbook: read a set of sessions that arrived days apart.

Run a closed playtest

Playbook: seed the roster a long study is easier to follow up with.