# Visitors and journeys

> Find one visitor and follow every visit, source, goal and payment they made, in order, on a single timeline.

Section: Features  
Canonical page: https://statsy.co/docs/features/journeys  
Last updated: 2026-09-15

Aggregates tell you what usually happens. A journey tells you what happened to one person — how they found you, how many times they came back, and what finally made them pay. It is the fastest way to understand a customer, and the fastest way to sanity-check your own tracking.

## Finding a visitor

**Journeys** has a single search box. It matches on email, name, user id, visitor id, country, city and page path, so you can look somebody up by the email they signed up with, or find everybody who saw a particular page.

Results list visitors with their country, first channel, sessions, pageviews, lifetime value, intent score and when they were last seen.

> **Note.** Email and name only exist for visitors you identified. Until your app calls `statsy.identify()`, everybody is an anonymous id, which is searchable but not memorable.

## The timeline

Open a visitor and you get their full history in time order, grouped by day:

- **Pageviews**, grouped into sessions.
- **Touches** — each arrival that carried a source, showing the referrer, the UTM tags and the page they landed on.
- **Goals** they completed.
- **Identify** events, where an anonymous visitor became a name.
- **Payments**, labelled new, renewal or refund.

Above the timeline, a summary row gives the first channel that brought them, their lifetime value, their location and their device. Where a session was recorded, the timeline offers **Watch replay** so you can see the session rather than read it.

## What to look for

- **The gap before the purchase.** If most customers first arrived months ago, your [lookback window](https://statsy.co/docs/revenue/attribution-models) is probably too short.
- **The page they kept returning to.** Often the pricing page, sometimes a comparison page you thought nobody read.
- **The second channel.** Somebody who found you on social and bought after a search did not really come from search, whatever last-touch says.

## Privacy

Journeys need a persistent visitor id, so they are complete only for visitors in Full mode. Cookieless visitors are counted, but cannot be linked across days by design. Identities exist only because your own site chose to send them, and shared dashboards never expose visitor lists, journeys or replays, whatever else you share.

Visitor search and journeys are available through the REST API and over MCP, so an assistant can answer "how did this customer find us?" from a support ticket.

Previous: [Funnels](https://statsy.co/docs/features/funnels)  
Next: [Session replays](https://statsy.co/docs/features/replays)