How to Know If Someone Opened Your Link (and Who)

You send a URL in Slack or email and then... nothing. Did they open it? Did it land at the wrong time and get buried? Did they read it and have no notes? A bare link has no way to report back unless the thing serving it

How to Know If Someone Opened Your Link (and Who)
TL;DR
A plain URL gives you no feedback at all. A click counter (Bitly and similar tools) tells you something was clicked. It does not tell you who clicked it. To actually know who opened a page, the link has to be tied to identity. With Display, gated artifacts tie views to signed-in identities. The artifact header shows who is viewing now, by name, and which version each person is viewing. Display shows view counts too. Display sends no notification when someone first opens a link. Tracking pixels and shorteners still have niche uses, but for "did the right person see this," identity beats counting.

You send a URL in Slack or email and then... nothing. Did they open it? Did it land at the wrong time and get buried? Did they read it and have no notes? A bare link has no way to report back unless the thing serving it keeps a record. By default, most don't.

That silence is the problem. "Ignored" and "never saw it" call for completely different follow-ups, and a plain link can't tell them apart.

"Opened" is a weaker signal than it sounds

Before reaching for any tracker, be honest about what a "view" is worth. A click is not a read. An anonymous count of 14 views tells you a page was loaded 14 times, by people you can't name, possibly including your own preview. For internal work the number you actually want is a name: did the VP of Engineering open the proposal, not did something open it.

So the useful question isn't "how many opens" but "which people." That reframes the tooling.

What you actually want to know: who, by name

The only way to attach a name to a view is to make the viewer identify themselves. Two honest ways to do that:

  • Company SSO. The viewer signs in with their company Google or Microsoft account to see the page. Every view is now tied to a verified identity.
  • A one-time password sent to a specific email address. For a specific outside person, they confirm a code sent to their address. The view is tied to that address.

Anything that doesn't ask the viewer who they are can only ever give you a count.

Option 1 - Identity-bound viewing

This is the strong version, and it's what gated publishing does by default. Ask your agent to publish the page to Display with company access.

Now anyone who opens it has authenticated as themselves first. While you have the artifact open, the header shows the signed-in people who are viewing it, with their names and the version each person views. People outside your organization appear with a Guest label. Anonymous visitors never appear. Display also shows view counts. Viewer stats show counts on Solo, and counts with viewer identity on Pro and Enterprise. Display sends no first-open notification, so check the artifact when you need to know. That's a real answer to "is the security lead looking at this," not a number you have to interpret. And because access is identity-bound, the same mechanism that tells you who viewed it also lets you revoke any one viewer.

This isn't a marketing-analytics product, and that's the point. It shows who is viewing an internal artifact, which is the signal internal sharing needs.

Bitly, Rebrandly, and similar count clicks and show rough geography. They're easy and they work on any destination. What they can't do is tell you who clicked or what happened after the click. Good for "is this campaign link getting traffic," useless for "did Maria open the doc."

Option 3 - Email tracking pixels

A 1x1 image that pings when an email is opened. Increasingly blocked (Apple Mail Privacy Protection pre-loads images, many clients strip them), so the signal is noisy and shrinking. It also tells you an email was opened, not that your linked page was read. Treat it as a fading proxy, not a source of truth.

Option 4 - Just ask

Underrated. In a trusted relationship, "did you get a chance to look at this?" is faster and more accurate than any tracker, and it doesn't make anyone feel surveilled. Reserve tooling for cases where asking doesn't scale or the record matters (compliance, audit, many recipients).

Where each fits

Plain linkShortenerTracking pixelIdentity-bound viewing
Tells you it was opened❌✅⚠️ (email, often blocked)✅
Tells you who, by name❌❌❌✅
Notify on first open❌⚠️⚠️❌ (viewer presence and view counts instead)
Survives forwarding sanely❌❌❌✅ (access stays per-person)
Right fornothingcampaign clicksshrinking email proxyinternal deliverables

FAQ

Can I get notified when someone opens my link?+

Not on Display. Display sends no first-open notification. It shows who is viewing the artifact now, by name, and gives view counts. A plain link records nothing. Shorteners give you a counter without named alerts.

How do I know who opened it, not just that it was opened?+

Tie the link to identity. Viewers can sign in before they see the page. They can use company SSO, or a one-time password sent to a specific email address. Then every viewer shows with a verified name. Counters and pixels can't do this because they never ask who the viewer is.

Is it legal to know who opened a link?+

In a B2B setting where you've sent someone a deliverable, recording that they opened it is normal and expected. Identity-bound viewing is cleaner than covert pixels because the viewer knowingly signs in. As always, collecting personal data should be disclosed in your privacy policy.

Can I track a link I already sent?+

Not retroactively. The original URL has to point at something that records views. If it was a plain link, re-publish the content at a tracked, gated URL and share that one going forward.

I don't want to feel like I'm spying on colleagues.+

Reasonable. Identity-bound viewing exists mainly so access is controlled and auditable, not to watch people. For a quick "did you see it," just ask. Use the record when it actually matters, like compliance or a decision that hinges on who reviewed what.

Publish your first artifact in 15 seconds.

Free tier. No credit card. One-time password auth for viewers on free, Google + Microsoft SSO on Pro (€49/month flat).

Get started free →See pricing