Skip to main content
Identified visitors on one of the current team’s sites — a “site user” is created the moment your app calls identify() for a visitor (see Tracking & events). A site is addressed by {siteKey} (UUID or domain). All endpoints require Authorization: Bearer {token}. These endpoints return real visitor data — identifier, name, avatar, and behavioral history — for the authenticated team’s own visitors only. A site user always belongs to exactly one site; a foreign site user id returns 404, never another team’s data. Both endpoints accept the shared date range and filter query parameters. The date range scopes differently on each: on the list it selects who to return (people last seen in the window); on the profile it scopes the range-bound metrics and timeline, not which person is returned.

List site users

Paginated, identified site users last seen inside the resolved date range, ordered by last_seen_at descending. This is a paginated endpoint — it returns the standard data / meta / links envelope (see Conventions). Query parameters Plus the shared filter keys, which narrow the behavioral metrics (pageviews, sessions, revenue, etc.) computed for each returned person. Response — each item in data: Status: 200 OK.

Get a site user’s profile

A single visitor’s profile: identity, range-scoped metrics, up to 8 device/browser session summaries, a ~26-week activity heatmap, and a 100-event timeline (newest first). Scoped to the team’s own site — a {siteUser} id belonging to another site (or another team) returns 404. Path parameters Query parameters Plus the shared filter keys. Response Status: 200 OK. 404 Not Found when siteUser does not belong to siteKey’s site.