Sessions

A session is one journey: an app run on a phone, a visit in a browser tab. A subject is the person (or anonymous device) behind it. Events, logs, errors, replays, survey responses and Telescope journeys all attach to both, so the console can show a single, ordered timeline for anyone.

Read the identity & sessions concept for how sessions start, time out and are superseded.

Automatic sessionsCopy Anchor Link

Client SDKs start a session at init and refresh it on foreground (autoTrackSessions, default true). You rarely call anything yourself — only identify when you know who the person is, and reset on sign-out.

APICopy Anchor Link

final nexus = Nexus.instance;

await nexus.sessions.identify('user_123',
    email: 'ada@example.com', name: 'Ada', phone: '+9647…', traits: {'plan': 'pro'});

final String? sessionId = await nexus.sessions.track(); // start / refresh now
nexus.sessions.reset();                                 // forget the person, rotate

nexus.sessionKey;  // current session key
nexus.distinctId;  // null while anonymous

In the consoleCopy Anchor Link

Sessions lists journeys with filters (platform, OS, app version, country, person). Open one to see its timeline — every event, log line, error, replay and request journey in order — and the person's other sessions.

ReferenceCopy Anchor Link

Flutter · JavaScript · PHP · Python · .NET · REST