The attachment tells you nothing after it leaves. A link tells you it was opened, when, and for how long — which is most of what you wanted and less than people assume. What the number actually means, and where it stops being evidence.
There is a particular silence after sending a deck. You attached it, you wrote the note, you pressed send, and now nothing. Not "they said no" — genuinely nothing. Days pass and the honest answer to did they even look? is that you have no way of knowing and will not get one.
That silence is not a gap in your follow-up process. It is a property of attachments. The moment the file leaves, the recipient has a copy that has no connection to you. There is nothing to report back, because there is no longer a "back."
A link is different for exactly one structural reason: the page is still yours. They come to it. That round trip is the only reason a number can exist at all.
Concretely, for each open:
And the one that matters most by its absence: who. A single link sent to five people cannot distinguish them. Five opens might be one person on two devices reloading, or three colleagues and a forward. If you need the identity, you have to design for it — ask for an email before the page opens, or send a different link per recipient and keep track of which went where.
That second option is unglamorous and works. It is also the honest version of "per-recipient tracking" for anyone not running an enterprise tool.
The number is not a measure of interest, and treating it as one leads people somewhere bad.
Consider two opens, both 40 seconds. One is a partner reading your summary slide carefully and deciding to forward it. The other is someone hunting for the price, finding it on slide eleven, and closing the tab. Same number. Opposite meanings.
What the number is genuinely good for is timing. Following up the day after something was read is a different conversation from following up into silence — you know they have the context, so you can ask a real question rather than "just checking you got this."
The failure mode is following up too precisely. A message arriving four minutes after an open reads as surveillance, because it is. Nobody minds that you can see a document was read; people mind being watched in real time. Wait a day. Use the fact, do not display it.
There is also a case where the number tells you something real and negative, and it is the one worth acting on: opened, and then nothing, repeatedly. That is not an attention problem. The document is not doing its job, and no amount of follow-up cadence fixes a deck that loses people on slide three.
Being straight about this matters more than the pitch:
A common and sensible pattern is both: send the link, offer the file on request. The link does the work of being opened and looked at; the file does the work of being kept.
Keep it simple, because complexity here mostly buys anxiety:
You are not buying certainty. You are trading an attachment that reports nothing for a page that reports a little, and the little is mostly when — which turns out to be the thing that changes what you do next.
Anyone selling you more certainty than that — who read it, how interested they were, whether it was forwarded — is selling an interpretation of the same thin signal. The signal is thin. It is still much better than the silence.
You open your host's protection settings and get an upgrade screen instead. The question isn't how to add a password — it's whose free plan has that switch, what the switch actually locks, and when paying for it beats moving.
Every free tier has a wall somewhere. On a private-link host the wall is not storage — it is time, and how many links you are allowed to keep. Here is exactly where each limit sits, what happens on day 8, and the three situations where free genuinely never runs out.
A scheduled self-destruct retires a shared link on a date you set at upload — no reminder, no manual deletion. Here's why scheduling beats deleting by hand, how to pick the date, and what the viewer sees when the link retires.
miinideck turns a single HTML file into an unguessable link with optional password and expiry. Default-private, never indexed.