# How to Create a Tracking Link Without Stopping to Name a Campaign > Create a tracked link from any conversation with one keystroke, no campaign name or spreadsheet. Learn the HeyZinc browser extension workflow. - **Author**: Caius Hayes - **Published**: 2026-08-19 - **Category**: Product - **URL**: https://heyzinc.com/blog/create-tracking-link-without-campaign-names --- ```tldr Open the conversation you're already in, press Alt+Shift+L, and the HeyZinc browser extension drops a tracked link at your cursor with the source context captured automatically -- no campaign name, no builder, no spreadsheet. You get notified when someone clicks, and you can engage with that context while the visitor is still on your site. UTMs are still right for broad campaigns; this is the per-conversation layer beneath them. ``` You want to know which reply, DM, or email brought a visitor to your site. So you reach for a tracking link -- and the moment you do, most tools ask you to stop and name a campaign. If you have ever searched "how to create a tracking link" mid-conversation, you already know the friction. `utm_source`, `utm_medium`, `utm_campaign`. Google's own [campaign URL guidance](https://support.google.com/analytics/answer/10917952) recommends you always set source, medium, and campaign, and that the values are case-sensitive -- `Spring` and `spring` are two different rows. That is a reasonable convention when you are running one broad campaign. It is the wrong unit of work when you are having ten conversations a day across replies, DMs, and emails. If you actually need a campaign URL, a [UTM link builder](https://heyzinc.com/tools/utm-link-builder) is still the right tool. But most of the time the question is narrower: which *specific* reply earned this click? And for that question, a campaign name is overhead you pay every time, for context you then have to maintain by hand. `utm_content=reply_04` only means something if somebody remembers what "reply 04" was six weeks later. The link becomes a tiny database record you are managing manually. There is a faster way. ## Create the link from the conversation you're already in The workflow is four steps, and the first three happen inside the page where you are already typing. **1. Open the conversation.** Go to the post, reply, comment, DM, or email where you want to share a link. You do not switch to a builder. You do not open a spreadsheet. You stay where the context already is. **2. Press the shortcut.** Press **Alt+Shift+L**. The HeyZinc browser extension reads the page you are on and builds the attribution payload automatically. It captures the source page URL, the page title, a platform label, and -- for Reddit -- the subreddit when those values are available. You do not type any of it. **3. Share the tracked link.** A short tracked link appears at your cursor, ready to paste into the reply or message you were already writing. The URL carries only a small first-party token -- something like `?tid=a7K3x` -- while the richer context (which page, which platform, which thread) is stored server-side with the link record. There is no campaign-name field because there is no campaign. There is a conversation. **4. Watch and respond.** See the visit and its original source the moment the visitor lands. That is the whole creation step. The shortcut is the builder. The page you are on is the context. The cursor is where the link goes. The reason this matters at conversation scale is that the friction you remove is the friction that actually kills per-message tracking. The moment creating a link costs you a context switch -- open a builder, name a campaign, copy, switch back, paste -- you stop doing it for every message. You batch. You reuse one link across ten replies. And the moment you reuse one link, the per-conversation signal collapses back into a campaign signal: you are back to "Reddit worked," not "this reply worked." The shortcut exists so that one link per conversation is cheap enough to actually sustain. One note worth being precise about: the shortcut documented on HeyZinc's current [tracking links](/tracking-links) page is Alt+Shift+L. An earlier post referenced a different key combination; the product page is the current source of truth, and that is what I am describing here. I have not independently hands-on tested every keystroke -- I am reporting the documented current behavior, verified against the live product page, not a personal benchmark. ## What the link actually carries (and what it doesn't) A tracked link carries attribution context, not identity. That distinction matters, because the category attracts overclaim. The link records where the visit came from: the source page, the platform, the thread. It does not name the visitor. Unless someone identifies themselves -- replies to your message, fills a form, logs in -- the link tells you *which conversation* brought them, not *who they are*. Identity is a separate problem, and pretending otherwise is the fastest way to look creepy. It also does not prove intent. A click tells you a message earned attention. It does not tell you that attention became a meeting, a deal, or revenue. On-site behavior is a separate signal from source context, and a click is the middle of the story, not the end. If you want the concept layer -- why campaign attribution stops one level above the conversation -- the [conversation attribution](https://heyzinc.com/blog/conversation-attribution) post is the deeper read. The short version: a UTM answers "which campaign?" A tracked link answers "which conversation?" ## What happens after the click This is the part most tracking-link tutorials skip. They end at "copy the generated URL." But the click is only useful if it changes what you do next. When a visitor opens a tracked link, HeyZinc can send a push to your mobile or desktop companion app and flag them as active now, so you can respond while their intent is still fresh. Bot and scraper traffic is filtered out automatically, so the alert is about a real person, not a crawler. The dashboard then shows per-link activity: visits, unique visitors, sessions, engagement, and a live state when a visitor is currently present. You are reading a conversation-level view, not a campaign rollup. Two qualifications, because the wording here is easy to overstate. First, "can send a push" is not "will always arrive." Mobile and companion delivery depends on your workspace's notification configuration and the device -- treat it as a configured workflow, not a universal guarantee. Second, the point is not to interrupt every visitor. The point is to make the moment visible when the context is still useful, so you can choose to act instead of finding the visit in next week's report. Picture the difference in timing. Without a live signal, you discover the visit in tomorrow's analytics report, by which point the visitor is long gone and the moment to say something useful has closed. With the arrival signal, you are choosing *while they are still on the page*: send a helpful message that references the page they opened, start a chat, pick up the phone, or do nothing and avoid turning useful visibility into pressure. The tracked link did not create the intent. It made the intent visible in time to act on it. If you want to take that all the way to revenue -- connecting this specific message to a closed deal -- the [tracking which message generated a customer](https://heyzinc.com/blog/track-message-generated-customer) post is the next step. A click is the middle of the story; that post is the rest of it. ## Use the source context to engage, not to pretend A tracked link gives your engagement something better than "visitor arrived." It gives it a source. When you connect a tracked link to an auto-engage rule, the opening message can reference where the visitor came from. If they clicked a link from a Reddit thread about onboarding, the opener can acknowledge that -- something like, "Saw you came from the onboarding thread -- are you looking at self-serve or team setup?" The context makes the message specific instead of generic. The rule is simple and worth keeping: reference only what the visitor actually shared. The tracked link tells you which conversation brought them. It does not tell you their name, their company, or their budget. Acknowledging the source is helpful. Inventing familiarity is how you lose trust. Keep a human takeover path available. Auto-engage is useful for the first pass; the moment the conversation needs judgment -- a real objection, a nuanced use case, a frustrated visitor -- a person should be able to step in without the visitor bouncing between tools. That handoff is what [proactive outreach](https://heyzinc.com/blog/proactive-outreach) is built around: see the live visitor, message them, call them in-browser when text is not enough, and escalate to a meeting when it is. ## When you actually need a campaign name (and when you don't) UTM parameters solve a real problem. They give analytics tools a standard vocabulary for campaign attribution, and they interoperate with the systems you already use. If you are running a paid campaign, a newsletter blast, or any initiative where the unit is "the campaign," use UTMs. That is what they are for. Tracked links address a different layer: the operational context around individual conversations. Use a UTM when the question is "did Reddit work?" Use a tracked link when the question is "did *this specific reply* work?" There is also a privacy angle, and it is worth scoping honestly. Several browsers strip known tracking parameters from URLs -- [MDN's web privacy documentation](https://developer.mozilla.org/en-US/docs/Web/Privacy) notes that Firefox, Safari, and Brave do this, and [Safari 17.0's Private Browsing](https://webkit.org/blog/14445/) blocks known tracking query parameters in links. The rules target well-known advertising and analytics parameter names, the `utm_*` family included. A custom first-party token like `?tid=` is a narrower target for those rules. It is not a name the cleaners recognize, so it is less likely to be caught by the rules aimed at known advertising parameters. But that is a reduction in exposure, not immunity. A determined privacy tool can still remove, rewrite, or block any tracking parameter, custom or not. The honest claim is the narrow one: the context lives server-side, and the token in the URL is a less obvious target -- not an invisible one. If you want the full comparison -- the token, the dashboard, the privacy posture -- the [tracked links vs. UTM parameters](https://heyzinc.com/blog/tracked-links-versus-utm-parameters) post is the mechanics deep-dive. ## The whole workflow in one pass Install the companion browser extension. Open the post, reply, DM, or email where you are about to share a link. Press Alt+Shift+L. A short tracked link lands at your cursor with the source page, platform, and thread captured automatically. Paste it into the conversation. When someone clicks, you get the arrival signal -- on your desktop or phone, with the visitor flagged as active now and the original conversation attached. Decide whether to engage, and if you do, let the context shape the opener instead of pretending you know more than the visitor shared. No campaign name. No builder. No spreadsheet to maintain. One shortcut, per conversation, with the context preserved on the link record. If you want to try it on your own outreach, [HeyZinc tracked links](/tracking-links) walk through the extension workflow, the dashboard, and the live-response handoff. Install the extension, share your first tracked link in a reply, and see the conversation behind the next click. --- - [More Product articles](https://heyzinc.com/blog/category/product) - [All articles](https://heyzinc.com/blog)