> ## Documentation Index
> Fetch the complete documentation index at: https://docs.openrevenue.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Visitors

> Explore individual visitor profiles and session timelines in OpenRevenue, all anonymous and free of personal data.

## Overview

The Visitors area, at `/<your-domain>/visitors`, lets you look at people on your site one at a time instead of in aggregate. Each visitor gets an anonymous pseudonym and avatar so you can follow their visit without ever seeing who they are. By default a visitor is recognized for one day; with a [stored visitor ID](https://docs.openrevenue.com/advanced/cookies-and-consent.md#with-consent) the profile covers every visit.

## Visitors list

The list shows one row per visitor with these columns:

| Name | Type | Description |
| - | - | - |
| Visitor | name | An anonymous pseudonym and avatar, stable for as long as the visitor ID lasts. |
| Country | geo | Resolved from IP at collection time. |
| Source | referrer | The referring domain, or Direct. |
| Views | number | Total pageviews from this visitor. |
| Revenue | amount | Shown when a revenue provider is connected. |
| Last seen | time | How long ago the visitor was last active. |

Sort by **Recent**, **Views**, or **Revenue**. Search by visitor name, and filter by **Country** or **Source** with an `is` or `is not` operator.

## Visitor profile

Open a visitor to see their full history at `/<your-domain>/visitors/<visitor-id>`:

* Summary cards for **first seen**, **sessions**, and **views**.
* An activity heatmap covering the last six months.
* A session timeline grouped by day, with the pages visited in each session, session and page durations, traffic source, and browser, OS, and device.

## How visitors are identified

By default the tracker stores nothing in the browser. OpenRevenue makes a daily visitor ID on its servers by hashing a secret salt that changes every UTC day, your project ID, a coarsened IP network prefix, and the user agent. When your site [stores a visitor ID with consent](https://docs.openrevenue.com/advanced/cookies-and-consent.md#with-consent), OpenRevenue uses that ID instead and recognizes the visitor across days.

| Name | Type | Description |
| - | - | - |
| IPv4 | /24 prefix | The last octet is dropped before hashing. |
| IPv6 | /64 prefix | Only the first four groups are kept before hashing. |
| Daily salt | secret | A random value that changes every UTC day and is then deleted, so no ID lasts beyond the day and old IDs cannot be recreated. |
| Project | project ID | The same person gets a different ID on every website. |

Coarsening the IP means a mobile network rotating a subscriber's address does not recount the same person as a new visitor.

## Privacy

> [!NOTE]
>
> Visitors are never identified by name, email, or raw IP in the default tracker. The pseudonym and avatar are derived from the anonymous visitor ID, and geo and device fields are coarse categories. Optional `identify()` attaches a hashed product user id only when your site calls it. The script honors Do Not Track and Global Privacy Control; when either is enabled, events are not sent. See [Cookies and consent](https://docs.openrevenue.com/advanced/cookies-and-consent.md) for what the tracker stores in each mode.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.