# Visitors and the visitor drawer

> The visitor list, how identity works in cookieless vs. cookie mode, and the drawer: journey timeline, tracked events, conversion timing, and replay links.

Section: Analyze. Canonical page: https://mrkr.app/docs/analyze/visitors. Last updated: 2026-10-03.

The Visitors page lists every distinct person seen in the range; opening one shows their whole journey, one session at a time.

![The Visitors page listing individual visitors with their source, device, session count and last seen time.](https://mrkr.app/docs/visitors.webp)

Every visitor in the range. Opening one shows their full journey.

## The visitor list

Each row shows first-seen and last-seen times, total sessions, total pageviews, and whether the visitor has ever completed a conversion, aggregated from every session tied to their visitor id. The list loads up to 100 visitors at a time, most recently active first.

## Visitor identity: cookieless vs. cookie mode

How a "visitor" is identified depends on the site's tracking mode:

- `Cookieless (default)`: The visitor id is a SHA-256 hash of the visitor's IP, user agent, site id, and a daily-rotating salt. Because the salt rotates every UTC day, the same real person gets a different visitor id tomorrow: there's no cookie and nothing persisted client-side. The display name reflects this: cookieless visitors show as a short "Visitor #xxxxxxx" handle rather than a name, since a stable-looking name would misleadingly imply long-term identity.
- `Cookie mode`: The visitor id is a persistent client-supplied id, so the same browser is recognised as the same visitor across sessions and weeks. These get a friendly, deterministic handle (an adjective and an animal, like "Calm Falcon") derived from their id, so the same person shows the same name every time you look.

> **Note:** Cookieless is mrkr's default tracking mode. Switching a site to cookie mode is a setting under Configure: see [Cookieless vs. cookie mode](https://mrkr.app/docs/configure/cookieless-and-cookie-mode) for what changes.

## The visitor drawer: journey timeline

Opening a visitor shows their sessions, each with a timeline mixing pageviews, outbound clicks and downloads, and any custom events they fired, in order, with timestamps, so you can read a session as a narrative rather than a table of rows. mrkr does not autocapture in-page clicks, so a timeline shows the pages someone moved through and the things you chose to instrument, not every button they pressed.

## Tracked events and conversion timing

Each session shows its pages, outbound clicks, downloads and custom events in order. The visitor summary includes first and last seen, session counts and conversion details. Persistent cookie identity can connect visits across days; cookieless identity cannot.

## Replay links

Any session that was recorded has a **Replay** link straight into the session-replay player, so you can go from "what did this visitor do" to "watch exactly what they did" in one click. See [Session replay](https://mrkr.app/docs/tracking/session-replay) for what gets recorded and how masking works.