Reading a profile

Open a person from the Users list to see everything Spectry knows about them.

Overview

The summary: first and last seen, total sessions, pages viewed, device and browser, location, and any traits you attached with identify(). Enough to place the person before you go deeper.

Sessions

Every visit, newest first, with duration, pages viewed and entry point. Where a session was recorded, a link opens it in session replay — the fastest route from "this customer had a problem" to watching it happen.

Events

The chronological stream of everything captured for this person: page views, custom events, form submissions, errors, rage clicks. This is the timeline to read when you need the exact order things happened in.

Reading a profile well

• Start at the end. The most recent session is usually the one that prompted the question.
• Mind the gaps. A long pause between sessions often marks a decision point — what did they see just before it?
• Watch, don't infer. If a replay exists, watching two minutes beats reconstructing the story from event names.
• One person is an anecdote. A profile generates hypotheses; confirm them with a funnel or a segment before acting.

What is not here

Only data you collected. Sessions before the snippet was installed, activity where consent was not granted, and anything beyond your plan's retention window will not appear.