# Read the journey

Every event you fire lands on a person's timeline. The People page is the roster; the journey is one person's whole story — anonymous first visit through paid, on a single timeline.

Source: https://cross-deck.com/university/read-the-journey/
Verified Crossdeck University lesson — prose plus real, runnable code.

## Everyone who's touched your product, in one list

Open People and you get the roster: every person Crossdeck knows, identified or not. Filter the list with the status chips — All, Anonymous, User, Trial, Paid, Churned — or search by ID, and you can narrow the feed to a city or country. It's how you go from "I have a lot of traffic" to "show me my paying customers" in one click.

## Click a person; read the timeline

Click anyone and you land on their journey: a chronological stream of every event for that one person, newest at the top, with a header that pulls together their identity, device, and how they were acquired. The auto-captured events (page.viewed, session.started, clicks, Web Vitals) sit alongside the domain events you fire (trial_started, feature_used) and the milestones that matter most — entitlement grants and revokes, the plan they're on. The timeline even shows the time elapsed between steps, so you can see where they paused.

## One record, the whole lifetime

The journey is the same canonical person record you met in Cross-platform identity. When an anonymous visitor signs in, their pre-auth device handle aliases into their user — so the pricing-page visit from before they had an account sits on the same timeline, just below the moment they signed up. You're not reading two fragments stitched together at read time; you're reading one person's continuous lifetime.

That's why the journey is the fastest way to answer "what actually happened to this customer?" — a support question, a churn post-mortem, a "did my new onboarding work?" check. Everything you set up in the last two lessons — your domain events, your super properties, your groups — is what makes each entry on this timeline worth reading.

## Find a customer, read their whole story

Filter People to Paid, open a customer, and read top to bottom: how they arrived, what they did before they converted, when the entitlement was granted, and what they've done since. That's the journey — and it's complete because identity kept them as one person the whole way through.

anon → trial → paid
 user_847's timeline: a referral visit, the pricing page, trial_started, the entitlement granted, and the first feature used — one continuous story.