Skip to main content

What Creates a Session (Operational Guide)

Understand exactly what counts as a Session in Lookback, including minimum thresholds, maximum duration limits, reconnect behavior, and how Sessions relate to quotas.

Henrik Mattsson avatar
Written by Henrik Mattsson
Updated today

A Session is the fundamental unit of data collection in Lookback.


Understanding what creates a Session - and what does not - is essential for planning studies, managing quotas, and interpreting results correctly.

This article explains Sessions from an operational perspective.


What is a Session?

A Session is one complete research interaction with a single participant, from start to finish.

A Session is created whenever a participant:

  • joins a study (moderated or unmoderated), and

  • completes one recorded interaction flow

This applies to:

  • Moderated sessions (LiveShare or Interview)

  • Unmoderated sessions (Tasks or SelfTest)

  • Remote or in-person sessions

Once completed, a Session exists as a recorded artifact that includes all captured activity.


When does a Session count? (minimum thresholds)

A Session is only counted once a minimum duration threshold is passed.

  • Unmoderated sessions (Tasks, SelfTest):
    → Count after 3 minutes of recorded activity

  • Moderated sessions (LiveShare, Interview):
    → Count after 5 minutes of recorded activity

If a participant drops before the threshold is reached, no Session is counted.


Maximum duration: when one Session becomes multiple

Sessions are counted in 2-hour blocks.

  • Up to 2 hours1 Session

  • More than 2 hours2 Sessions

  • More than 4 hours3 Sessions

  • And so on

This applies regardless of whether the study is moderated or unmoderated.


Reconnect behavior (important)

Reconnects that count as the same Session

A reconnect counts as the same Session if:

  • the participant reconnects on the same device, and

  • the reconnect happens within the same 2-hour window

Temporary drops, refreshes, or accidental disconnects do not create new Sessions under these conditions.


Reconnects that create a new Session

A new Session is counted if:

  • the participant reconnects using a different device, or

  • the reconnect occurs after the 2-hour window, or

  • the participant intentionally starts a new recorded interaction

Even if the participant is the same person, device changes always create a new Session.


What is included in a Session

A Session includes everything recorded during that interaction, including:

  • screen recording (when applicable)

  • participant audio and (if enabled) camera video

  • touches, taps, and gestures (when supported)

  • time-stamped notes

  • observer chat

  • transcriptions (if enabled)

  • Findings created from that Session

  • Reels that reference Findings from that Session

All of this belongs to one Session, unless duration or device rules trigger additional Sessions.


Diary studies and repeated participation

In diary or longitudinal studies:

  • Each recorded entry counts as one Session

  • Multiple entries by the same participant = multiple Sessions

Example:

  • 5 participants

  • 5 diary entries each
    25 Sessions total

Sessions are counted per recorded interaction, not per participant.


What does NOT create a Session

The following do not count as Sessions:

  • Preview Sessions

  • Observer views

  • Stakeholders watching live or replay

  • Researchers reviewing recordings

  • Notes, tags, or Findings created after the Session

Only participant-initiated, recorded interactions are counted.


Deleting Sessions

If a Session is deleted:

  • its recording is permanently removed

  • all Findings created from it are deleted

  • it may not be recoverable

Deleting a Session does not restore session quota.


Why this matters

Understanding session counting helps you:

  • estimate quotas accurately

  • design diary and longitudinal studies safely

  • handle reconnects without stress

  • explain billing clearly to stakeholders

  • avoid accidental over-consumption of Sessions

Did this answer your question?