# What Is a Tracking Link? Click Data, Context, and Attribution Explained > A tracking link records what's useful about a click. Learn what a tracking link is, what it records, and where the context lives. - **Author**: Caius Hayes - **Published**: 2026-08-12 - **Category**: Marketing - **URL**: https://heyzinc.com/blog/what-is-a-tracking-link --- ```tldr A tracking link is a shareable URL that records something useful about a click -- where it came from, which conversation produced it, or both. It works through a redirect the link service logs, a token or parameter the destination reads, or a server-side record keyed by a token. The useful distinctions are what the link records (a click, a campaign, a conversation, an active-now state) and where the context lives (in the URL or server-side). No tracking link establishes identity, survives every privacy tool, or proves causal conversion lift on its own. ``` You share a link in a Reddit reply, a cold email, or a DM after a call. A visit shows up in your analytics, labeled "social," "email," or "referral." What you usually want to know is narrower: which specific message brought this person here, and are they on the site right now? That is the gap a tracking link is built to close -- when it is built well. The vocabulary is the first problem. "Tracking link," "short link," "UTM link," and "tracked link" are used interchangeably, but they record different things and fail in different ways. You need a definition that holds up. ## What counts as a tracking link There is no single canonical definition that covers every product the industry calls a tracking link. The cleanest umbrella is this: **a tracking link is a shareable URL that records something useful about a click -- where it came from, which conversation produced it, or both -- by routing the visit through a redirect, attaching a token or parameter the destination reads, or both, and optionally keeping richer context server-side on a link record.** That definition is deliberately wide, because the category covers three mechanisms that often get conflated: 1. **A short link with a redirect log.** A service gives you a short URL. When someone clicks, the request hits the service's redirect endpoint, the service logs the hit (timestamp, rough location, referrer, user-agent), then forwards the visitor to your destination. The tracking is the redirect log. 2. **A UTM-tagged destination URL.** You append `utm_source`, `utm_medium`, `utm_campaign` (and optionally `utm_term`, `utm_content`, `utm_id`) to the destination URL itself. There is no separate redirect service; the destination analytics system reads the parameters when the page loads. The tracking is the parameter values landing in analytics. 3. **A per-conversation tracked link.** A short URL carries a first-party token and keeps richer context -- source page URL, page title, platform, and for Reddit the subreddit -- on a server-side link record keyed by that token. The tracking is the token resolving to a per-conversation record, plus the click activity that record accumulates. A single link can combine all three. The interesting distinctions are not "tracking link vs. short link" but **what is recorded** and **where the context lives**. ## How a tracking link records a click Someone clicks a short URL. The request hits a redirect endpoint the link service controls. The service records the hit -- timestamp, IP-derived location, referrer, user-agent -- and issues an HTTP redirect to your real destination. The visitor lands on your page. Your page analytics records a visit. Notice the split. The link service sees the click. Your destination sees the visit. Those are not the same event, and they can disagree: a click stopped by a network error, a visit that arrives without the parameter because something stripped it, a click from a preview bot that never becomes a human visit. With a UTM link, there is no redirect log; the tracking happens at the destination when the analytics system reads the parameters. With a per-conversation tracked link, the token resolves to a server-side record that holds the conversation context, and the click activity accumulates on that record over time. This is why a tracking link can tell you things a plain destination URL cannot -- and why it can mislead you if you forget which layer the data came from. ## What a tracking link can record Disambiguate the word "track" by what is actually recorded: - **A click.** The raw fact that someone -- or something -- requested the URL. Raw click counts get inflated by preview bots, email scanners, and scrapers; product-specific filtering applies, and a raw click count is not a human visitor count. - **A campaign label.** Which campaign, medium, source, or creative the click belongs to. That is the UTM layer. - **A per-conversation context.** Which specific reply, post, DM, email, or post-call follow-up produced the click. That is the tracked-link layer. - **An active-now state.** Whether a visitor is currently on the site, not just that they clicked at some point. This is configuration- and device-dependent, not a universal signal. These are different signals, not synonyms. A click is not a visitor. A visitor is not a session. A session is not a conversion. A campaign label is not a conversation. The deeper treatment of clicks versus visitors versus sessions versus conversions belongs in a dedicated link-tracking guide; the point here is that "tracking" is not one thing. ## Where the context lives -- URL vs. server-side This is the distinction that actually changes what you can do with the link. With a UTM link, the context lives in the URL. Google documents `utm_source`, `utm_medium`, `utm_campaign`, `utm_term`, `utm_content`, and `utm_id` as the [campaign parameters](https://support.google.com/analytics/answer/10917952) you append to a destination URL, and recommends always setting source, medium, and campaign. The parameters are visible to the visitor. They can be stripped by a browser or extension before the destination sees them. They are case-sensitive -- `utm_source=google` and `utm_source=Google` are different rows. And the URL itself does not carry the human context you care about: `utm_content=reply_04` only means something if somebody remembers what "reply 04" was six weeks later. At conversation scale, you end up maintaining a spreadsheet that maps each value to the human context. The link becomes a tiny database record you are managing by hand. With a per-conversation tracked link, the context lives server-side on a link record keyed by a token. The URL only carries the token; the richer context stays on the record. The URL stays short and clean. The context is not visible to the visitor or to a privacy tool that only inspects query strings. And the mapping between the token and the conversation is captured when the link is made, not typed and remembered by hand. The URL still carries the token, though. So the token itself can still be stripped. Moving the context server-side reduces your reliance on the URL surviving intact, but it does not make the link unkillable. ## Attribution: campaign vs. conversation Google Analytics defines attribution as "assigning credit for important user actions to different ads, clicks, and factors along the user's path to completing the action." An [attribution model](https://support.google.com/analytics/answer/10596866) is the rule, set of rules, or data-driven algorithm that decides how credit is split across touchpoints. GA4 currently ships three models: data-driven attribution, paid and organic last click, and Google paid channels last click. The older rule-based models -- first-click, linear, time-decay, position-based -- were deprecated in November 2023. The unit GA4 operates on is a touchpoint: an ad click, an organic click, a channel engagement. The grain is campaign, channel, and creative. That vocabulary is excellent for deciding which ad budget earned a conversion. It is the wrong grain for deciding which human conversation earned a click. UTM parameters populate the manual source/medium/campaign dimensions at that campaign grain. A per-conversation tracked link sits at a layer beneath campaign attribution: the individual reply, DM, email, or post-call follow-up. It does not replace multi-touch or data-driven attribution for aggregate budget decisions. It gives each touchpoint per-conversation context, and makes the earliest conversation visible -- the one last-click attribution typically erases. We wrote the full attribution thesis in our [conversation attribution](https://heyzinc.com/blog/conversation-attribution) piece; the short version is that the unit of work in founder-led distribution is a conversation, not a campaign. One distinction worth keeping sharp: identity, behavioral intent, and attribution context are three different problems. A tracked link attributes a visit to a source context. It does not name the visitor. Behavioral intent -- what the visitor does on the site -- is a separate signal, read from page activity, not from the link. Conflating them produces the creepiest outcomes and the weakest data. If you want the identity side, that is [a separate problem](https://heyzinc.com/blog/identify-website-visitors); a tracked link will not solve it. ## Privacy: what browsers actually do Privacy tooling does not treat every query parameter as neutral. WebKit's [Safari 17.0 release notes](https://webkit.org/blog/14445/) list "Blocking for known tracking query parameters in links" as a Private Browsing improvement. MDN's [web privacy documentation](https://developer.mozilla.org/en-US/docs/Web/Privacy) notes that several browsers strip known tracking parameters. The behavior varies by browser, extension, device, and configuration -- it is not a universal stripping of every query parameter in standard browsing. That creates two separate concerns: 1. A parameter can be removed before the destination sees it. 2. Even when it survives, a generic campaign label may not preserve the original conversation context. A custom first-party token is a narrower target for rules aimed at known advertising and analytics parameters, and keeping richer context server-side reduces reliance on the URL surviving intact. This is a reduction in exposure, not immunity. A determined privacy tool can still remove, rewrite, block, or refuse any tracking. The accurate claim is narrow: a custom first-party token is less likely to be caught by rules that target the best-known parameter names, while the richer context lives server-side. Anything stronger is overclaim. ## Forwarded links When someone copies a tracked URL and forwards it -- pastes it into another thread, sends it to a friend, posts it somewhere else -- the token travels with the URL. Every click on the forwarded URL still resolves to the original link record and its captured source context. That can be useful. A good reply amplifies, and you see the amplification on the original link's dashboard. It can also mislead. A different audience is now grouped under a conversation they did not have. A click count that looks like "one reply is driving all this traffic" may actually be "one reply plus three forwards plus a reshare." The mechanic is honest; the interpretation needs the caveat. There is no reliable way to tell a forwarded click from an original one on the same device chain without additional signals -- a different referrer, for example -- and the referrer itself can be stripped or spoofed. Plan for forwarded links. They are a feature of any URL that carries a token, not a bug specific to one product. ## What a tracked link cannot establish The category attracts overclaim, so it is worth being explicit about the limits. - **It is not identity resolution.** A tracked link attributes a visit to a conversation context. It does not name the visitor unless the visitor identifies themselves. - **It is not immune to privacy tooling.** A custom first-party token reduces exposure to known-parameter rules. It does not guarantee survival against a determined privacy tool. - **It is not a replacement for campaign or multi-touch attribution.** Use UTMs and GA4's models for aggregate budget allocation. Use a tracked link for the operational layer beneath: which message, which reply, which call. - **It does not prove causal conversion lift on its own.** Seeing a visit does not prove a conversion, and a click does not prove causal lift. Conversion claims need attributable internal data or a controlled result. - **Live and mobile signals are configuration-dependent.** Active-now and notifications depend on your workspace setup and device, not a universal guarantee. - **Raw click counts can be inflated.** Preview bots, email scanners, and scrapers issue requests to URLs. Product-specific filtering applies; do not treat a raw click count as a human visitor count. None of these limits make tracking links useless. They make the honest version of the claim useful. A tracked link is a handoff between distribution and conversation: a durable reference to the context you created, a dashboard that shows what happened after the click, and a chance to respond while the moment still matters. ## Where HeyZinc fits HeyZinc tracked links use a short first-party token in the URL and keep per-conversation context -- source page URL, page title, platform, and for Reddit the subreddit -- server-side with the link record. The browser extension builds that context from the page you are already on, so a link made while replying to a specific thread carries that thread's context without you typing it. The dashboard surfaces visits, unique visitors, sessions, engaged visitors, and an active-now state, with companion and mobile notifications when someone clicks. The notifications are a configured workflow, not a universal guarantee -- they depend on your workspace setup and device. If you want the full mechanics -- the token, the redirect, the dashboard, the privacy posture in detail -- the [tracked links versus UTM parameters](https://heyzinc.com/blog/tracked-links-versus-utm-parameters) piece is the deep dive. If you just need a conventional campaign URL, the [UTM link builder](https://heyzinc.com/tools/utm-link-builder) is the free tool for that. And if you want to try per-conversation tracked links on your own outreach -- one link per reply, DM, or cold email, with the source context captured and a live visit you can act on -- [HeyZinc](https://heyzinc.com) is the place to start. A dedicated `/tracking-links` product page is on the way; for now, the homepage and the deep-dive above are the best entry points. --- - [More Marketing articles](https://heyzinc.com/blog/category/marketing) - [All articles](https://heyzinc.com/blog)