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

Why a plain link tells you nothing

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 code 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. Publish the page behind company auth:

dsp publish ./proposal.html

Now anyone who opens it has authenticated as themselves first. The artifact's view record shows which company identities opened it and when, and you get a notification the first time someone does. That's a real answer to "did the security lead actually see 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's a verified record of who opened an internal artifact, which is exactly the signal internal sharing needs.

Option 2 - Link shorteners with analytics

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