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

# Link analytics

> Clicks, unique visitors, geo, device, browser and OS breakdowns — with bots filtered out automatically.

Every click TrackRev records carries a rich set of attributes, surfaced across the **Dashboard**
and **Channels** pages. All of it is first-party — captured server-side at the redirect, not from
a third-party analytics script.

## What's captured on every click

At the redirect, TrackRev records:

* **Channel** and **link**
* **Geo** — country and city (from edge headers)
* **Device** — desktop / mobile / tablet
* **Browser** — Chrome, Safari, Firefox, Edge, Opera, Samsung, Other
* **OS** — iOS, Android, Windows, macOS, Linux, Other
* **Referrer**, **IP**, and a **bot flag**

## The Dashboard

Open **Dashboard** for a workspace-wide view. Use the **7d / 30d / 90d** range switcher (default
30 days); every metric shows a delta versus the previous equal-length window.

<CardGroup cols={2}>
  <Card title="Metric cards" icon="gauge">
    **Clicks**, **Visitors**, **Conversions**, and **Revenue** — each with a trend sparkline and
    period-over-period change. (Revenue is a paid-plan feature.)
  </Card>

  <Card title="Traffic over time" icon="chart-line">
    Clicks and unique visitors plotted daily across the range.
  </Card>

  <Card title="Top channels" icon="radio">
    A table of Channel, Clicks, Visitors, Conversions, Revenue and conversion rate.
  </Card>

  <Card title="Devices & audience" icon="users">
    Device split, plus top **Countries**, **Browsers** and **Operating systems**.
  </Card>
</CardGroup>

There's also a **live activity** feed of events as they arrive.

## Bot filtering

TrackRev filters out non-human traffic so your analytics reflect real people. It uses an
industry bot-signature database, and additionally treats empty user-agents and link-preview
**prefetch** requests (for example, Apple Mail's privacy prefetch) as bots.

<Info>
  Bots are **flagged but still redirected** — a real person may be behind a preview fetch — but
  they're excluded from your analytics counts and never trigger conversion or webhook events. In
  the [API](/developers/endpoints/clicks) you can opt to include them with `?bots=include`.
</Info>

## Deeper breakdowns

* **Channels page** (under *Insights*) — channel performance and lifetime value by channel. See
  [Channels](/link-tracking/channels) and [Channels & LTV](/revenue-attribution/channels-and-ltv).
* **Visitors page** — the full journey for any individual visitor. See
  [Visitors & the journey](/revenue-attribution/visitors).
* **Export** — download channel performance as CSV. See [Exports](/revenue-attribution/exports).