> ## 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.

# Core concepts

> The handful of ideas the rest of the documentation is built on — workspaces, links, channels, visitors, events, orders and attribution.

TrackRev's three products share one vocabulary. Learn these ten terms once and every
dashboard reads clearly.

## Workspace

A **workspace** is one brand or product you're tracking — its links, channels, visitors,
revenue and affiliate programme all live inside it. Everything you do in TrackRev happens in
the context of a workspace, and data never leaks between workspaces.

Most people run one workspace. Agencies and multi-product teams run several and switch
between them from the workspace switcher in the sidebar. Your plan sets how many workspaces
you can own: Free and Starter are one workspace; Growth and Scale are unlimited.

<Note>
  Your **workspace ID** is the UUID you put in the pixel's `data-id`. Find it on the
  Integrations tab.
</Note>

## Link

A **link** is a branded short URL you create in TrackRev — for example
`go.yourbrand.com/spring`. Every link has a destination, a channel, and optional UTM
parameters baked in. When someone clicks it, TrackRev records the click server-side, tags
the visitor, and redirects to the destination.

* **Slug** — the short path after the domain (`spring` in the example above). You choose it,
  accept an AI-suggested one, or let TrackRev generate one.
* **Destination** — where the click ultimately lands.

## Channel

A **channel** is the acquisition source a link belongs to — *newsletter*, *twitter*,
*affiliate*, *paid-search*, and so on. Channels are how TrackRev rolls thousands of
individual clicks and sales up into an answer to the only question that matters: **which
source pays your MRR?** Every link belongs to a channel, so revenue always rolls up by
channel automatically.

## Campaign

A **campaign** is a folder that groups links for a specific push — a product launch, a
Black Friday sale, a webinar. Campaigns give you date ranges, tags and bulk actions across a
set of links without changing how each link attributes.

## Visitor

A **visitor** is one person TrackRev is following, identified by a first-party `vid`
(visitor id). The `vid` is created at the first click (or first pageview) and stored as a
first-party cookie on your domain, so it survives across your marketing site, app and
checkout. When you call `identify(email)`, that email is attached to the visitor — which is
how an anonymous clicker becomes a known, paying customer in the timeline.

## Event

An **event** is something a visitor did that the pixel reported: a **pageview**, an
**identify** (email attached), or a custom **track** event you fire yourself. Events build
the [visitor journey](/revenue-attribution/visitors) and count toward your monthly
tracked-events allowance.

## Order (sale)

An **order** is a real charge pulled from your payment processor — Stripe, Paddle, Polar or
Lemon Squeezy. TrackRev joins each order back to a visitor using the checkout reference you
pass (`client_reference_id` / `metadata.vid`) or, failing that, the customer's email. An
order is TrackRev's single **definition of a sale** — the same one used by channel reports,
the visitor journey and affiliate commissions, which is why every number reconciles.

## Attribution model

An **attribution model** decides which touch gets credit for an order when a visitor
clicked more than one link on the way to buying. TrackRev supports:

<CardGroup cols={3}>
  <Card title="Last-touch">
    All credit to the most recent link before the sale. The default.
  </Card>

  <Card title="First-touch">
    All credit to the very first link that brought the visitor in.
  </Card>

  <Card title="Linear">
    Credit split evenly across every touch in the journey.
  </Card>
</CardGroup>

You switch models at any time **without re-tagging anything** — TrackRev recomputes from the
same underlying events. See [Attribution models](/revenue-attribution/attribution-models).

## Attribution window

The **attribution window** is how far back TrackRev looks from a sale when assigning credit.
A click older than the window doesn't get credit. It's configurable per workspace; SaaS
teams commonly run 30–60 days to match their consideration cycle. See
[Attribution windows](/revenue-attribution/attribution-windows).

## Commission & partner

When a sale comes through your affiliate programme, TrackRev records a **commission** — the
partner's cut of that order — on the affiliate ledger. A **partner** (affiliate) is someone
enrolled in your programme with their own referral links and a portal to track earnings.
Because commissions are computed from the same orders as everything else, a refund on a sale
automatically reverses the commission. See [Affiliate overview](/affiliate/overview).

***

## How the pieces fit together

<Steps>
  <Step title="A link belongs to a channel">
    You create a **link** for a **channel**, optionally inside a **campaign**.
  </Step>

  <Step title="A click creates a visitor">
    A click on that link records the click and creates (or matches) a **visitor** with a
    `vid`.
  </Step>

  <Step title="Events build the journey">
    The pixel reports **events** — pageviews, an identify, custom events — under that `vid`.
  </Step>

  <Step title="An order joins back to the visitor">
    A charge becomes an **order**, joined to the visitor by the checkout reference or email.
  </Step>

  <Step title="The model assigns credit">
    Your **attribution model** and **window** decide which channel — and which **partner**,
    if any — gets the credit.
  </Step>
</Steps>

<Card title="Ready to see it live?" icon="rocket" href="/getting-started/quickstart">
  The Quickstart takes you from sign-up to your first attributed click in five minutes.
</Card>