2026-08-23

Email click tracking without a CRM

You send twenty personalized outreach emails, each with a link. Three days later you want one answer: which of the twenty clicked?Not "the link got 3 clicks" — which three people. Here's how to get that answer without buying an enterprise sales platform.

The problem with aggregate click tracking

Paste any link into Bitly, TinyURL, or almost any shortener, and it'll tell you the link was clicked N times, roughly where from, on what kind of device. That's the right answer for a link on a landing page or a social post, where "who" doesn't mean anything — anyone could have clicked it.

It's the wrong shape of answer for outreach. If you send the same short link to twenty people, a click count of 3 tells you 3 people clicked something — not which three. To know that, the click has to be attributable to an individual before it happens, not inferred after the fact.

Why this usually means buying a CRM feature

Tools like Outreach and Salesloft solve this by tying every link to a contact record in their platform — the attribution is a side effect of everything already living inside a CRM. That works, but it means the tracking capability is locked behind adopting the whole platform: importing contacts, running sequences through it, paying per seat. If your workflow is a normal mail client and a spreadsheet, that's a lot of infrastructure to adopt just to answer one question.

The actual mechanism: one short code per recipient

The technique itself doesn't need a CRM — it needs a short code minted per recipient rather than per link. Instead of one shrtlynx.com/abc123 shared by everyone, each recipient gets their own: shrtlynx.com/abc123 for Alice, shrtlynx.com/x9k2m1 for Bob, and so on, all pointing at the same destination URL. The moment one resolves, you know exactly whose code it was.

Two things make this practical instead of tedious:

  • No login required from the recipient. The attribution comes from which code they clicked, not from who they authenticate as. They never see a sign-in screen — the link just goes to your destination, same as any other short link would.
  • Codes are provisioned in bulk, not one at a time. In ShortLynx, you paste a list of recipients (an email, or any label you'll recognize) and get every short URL back at once — the same motion as a mail merge, not twenty separate manual steps.

Walkthrough

  1. Create a link, choosing User-attributed as the type.
  2. Under Provision codes, paste one recipient per line — an email address or any label you'll recognize later.
  3. Copy each recipient's unique URL into their email — this is the mail-merge step.
  4. Send. The link detail page's analytics now show which recipients clicked, and — just as usefully — which didn't, so you know who to follow up with.

The consent question, and why it isn't optional here

Tracking who clicked a link you sent someone is a real privacy decision, not a neutral feature — the recipient didn't opt into being tracked just by receiving an email. This is why ShortLynx enforces a disclosure interstitial by default on user-attributed links: if you haven't published a privacy policy that covers link tracking, recipients see a disclosure screen before the redirect completes and can decline to be tracked — the destination still loads either way. Once you've published a policy that covers it, that screen is skipped. The point isn't to make tracking hard; it's to make it impossible to do by accident, silently.

A more reliable signal than open tracking

Worth saying directly: if your current approach to this is an email open-tracking pixel, per-recipient click links are simply the more reliable of the two. A pixel requires the recipient's mail client to fetch a remote image — and Apple Mail Privacy Protection pre-fetches every image for every message regardless of whether it was actually opened, which has made "open rate" a number that measures something closer to "which provider they use" than genuine engagement. A click requires a deliberate action from the recipient. It's a cleaner question with a cleaner answer.

Frequently asked questions

Does the recipient have to click a special link, or does this work with any link?

It has to be the per-recipient short link — that's what carries the identity. If you paste the plain destination URL instead, there's nothing to attribute the click to. In practice this means generating one short link per recipient before you send, not after.

Do I need to tell recipients their click is being tracked?

If you haven't published a privacy policy covering it, ShortLynx shows an interstitial disclosure screen before the redirect completes, and the recipient can decline to be tracked — the destination still loads either way. If you do have your own privacy policy, you're responsible for it covering link tracking; ShortLynx enforces disclosure by default specifically so this isn't something you can accidentally skip.

Does this work for cold outreach, or only existing contacts?

Technically it works for anyone you have an email address for. Whether it's appropriate is a separate question from whether it works — the same deliverability and consent norms that apply to any outbound email apply here too.

How is this different from an email open-tracking pixel?

An open-tracking pixel is a 1x1 image that has to load for you to know the email was opened — and Apple Mail Privacy Protection, most corporate proxies, and many mail clients now pre-fetch or block images by default, which makes open rates unreliable in ways that are hard to detect. A click is a much cleaner signal: the recipient took a deliberate action, and nothing about it depends on whether their mail client decided to render an image.