Core concepts

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.

​

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 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: You switch models at any time without re-tagging anything — TrackRev recomputes from the same underlying events. See 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.

​

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.

---

​

How the pieces fit together