How to See If Someone Opened a Link You Sent
By Oleh Tsyupa, Founder of PDFTrackr · Published 2026-09-14 · Updated 2026-09-14
8 min read45.4% of recorded sessions on multi-page documents either rendered no page at all (12.2%) or never went past the first one (33.2%) — and a counter that reports opens would have called every one of them a read.
This is the number that makes "did they open it" the wrong question to stop at. Across 3,745 recorded sessions, 457 rendered no page at all — the link opened and nothing was read — and a further 1245 rendered page one and stopped there. Only 54.6% reached any page beyond the first. The two groups also behave completely differently once you can see them apart: the median session that stopped on page one lasted 13.9 seconds, against 71.4 seconds for one that got further. An open, on its own, does not distinguish somebody who read your document from somebody whose mail system fetched it. That distinction is the whole reason to prefer a link that records pages over one that records requests.
Based on 3,745 recorded sessions across 247 documents and 277 share links, 22 Sep 2025 – 25 Aug 2026, extracted 26 Aug 2026 — multi-page documents only, because a one-page document has no second page to get to. That restriction drops 153 sessions from the 3,898 recorded: 83 on one-page documents, and 70 more whose document has no page count on record — the second group is dropped because its page count is unknown, not because it is one. Every recorded session inside the restriction is counted, including the automated ones, so that the group which renders no page at all stays visible. Figures are medians, not averages.
If the document is the thing you want an answer about, the quickest test is to create a free tracked link for it and send that instead of what you were about to send — or look at the live demo first to see what a reading record looks like on sample data.
What “opened” means here — four different events
Most of the confusion on this question is one word doing four jobs. Before you choose a method, decide which of these you actually want to know, because they have different answers and different reliability:
- The message was opened. An email tracking pixel's answer. It means a remote image was requested by something, which is not the same as a person looking at the message.
- The link was clicked. A redirect's answer. It means a request reached the destination — a real navigation, usually, but not always a human one.
- The destination was loaded. The page rendered in somebody's browser. Closer, and still silent about whether anything was taken in.
- The content was read. Which parts, in what order, for how long. Only a destination you control can report this, and only if it is built to.
The vocabulary is worth getting right because the gap between the second and the fourth is where most senders go wrong — we separate the three of them with the measurements at opened, clicked or read, which is where the figures in the box above live in full.
What each kind of link can actually show you
Five things people mean by “a link I sent”, compared on the only question that matters here: what comes back to you afterwards.
| What you sent | Do you own the destination | What you learn | What you never learn |
|---|---|---|---|
| A tracked document link (PDFTrackr) | Yes | Every open, which pages rendered, in what order and for how long, whether a download was clicked, and whether the same visitor came back inside the day — with automated opens from mail scanners and link previewers classified at session close and excluded from the counts | Who the reader is, unless you switched on the email gate and they typed an address |
| A link to a page on your own website | Yes | That the page was loaded, and whatever your site analytics measure about the visit | Which specific person it was, on a link everybody shares |
| A shortened link you created | The redirect only | That the redirect was followed, and roughly when | Anything past the click — the destination is somebody else's and reports to them |
| An email with a tracking pixel | The image, not the message | That a remote image was requested — degraded badly by mail clients that pre-load remote content on the reader's behalf | Whether a person saw the message, and anything at all about a document attached to it |
| A URL you did not create — a public page, somebody else's file | No | Nothing. The destination reports to its owner | Everything. Adding reporting means sending a link you own instead — a shortener you created reports the click, but nothing past it |
The verdict is ours and it is bounded to this table: for finding out whether a document you sent was opened, the tracked document link is the pick, because it is the only row that reports both the open and what happened after it, and the only one that separates the machine opens from the human ones before you read anything into the number. Where the pixel row genuinely wins is that it needs no click at all — a plain message with no link can still report something, and no hosted document can do that. Where the shortened link wins is that it works on a destination you will never own.
Why the email answer keeps getting less reliable
If you have used open tracking for years and feel the numbers have stopped making sense, you are right, and it is not your imagination or your sending tool. Three separate things now stand between an email and an honest open count, and each is documented by the platform that does it.
Mail clients pre-load remote content. Apple's Mail Privacy Protection, on by default for Apple Mail users who accept the prompt, loads remote content privately in the background whether or not the reader opens the message — so the sender learns nothing reliable about whether it was opened, and nothing about the reader's address. Gmail scans the images in a message before you receive it, which its own help page says stops a sender using an image load to get information about your computer or location.
Security systems follow links before people do. Corporate mail filters rewrite the URLs in inbound mail and scan the destination on the organisation's behalf — as the message arrives, and again at the moment of a click. That scan is a real request from a real machine, and to anything counting requests it looks exactly like a recipient clicking. It is also the reason a first open arriving seconds after you pressed send is usually not a person.
And an open was never a read anyway. That is the figure in the box above and it is the part no amount of email-side engineering fixes. The fix is not a better counter, it is a different measurement: record what the reader did inside the document rather than the fact that a request arrived. That is the difference we set out in full at email tracking versus document tracking.
The version that still works, in four steps
One. Host the thing rather than sending it. Upload the file and generate a link for it. The link is yours, so it can report to you; an attachment is a copy handed over and reports to nobody.
Two. Decide whether you need a name attached. If you are writing to one person you already know who opened it. If the link will be forwarded inside an organisation, turn on the email gate so each reader identifies themselves — an address somebody types is a claim rather than proof, and the form tells the reader plainly that it is shared with you.
Three. Give the first day no weight. On a corporate address the first open is frequently a scanner. PDFTrackr classifies those at session close and keeps them out of the counts, and shows what was removed rather than quietly shrinking the number — but the habit of ignoring the first few minutes is worth keeping regardless of tool.
Four. Read the session rather than the total. One session that covered nine pages over six minutes tells you more than forty opens do, and it is the thing you can quote back in a follow-up without sounding like you are reciting a dashboard. The general form of this — attachment records nothing, hosted link records the reading — is at how to know who opened your PDF.
When Pro becomes the right choice
All of the above is on the plan that costs nothing — per-page reading, the email gate, the exclusion of automated opens, 500MB, 50 files, 50 active share links, twelve months of history, no card. Free is the product rather than a trial, and somebody who sends a few links a month never needs to pay us.
Pro becomes the right choice when one link stops being enough. Once the same document goes to more than a handful of named people at once, bulk personalised links give each recipient their own, so the record says who opened it rather than leaving you to guess from a shared URL. Once knowing an hour earlier changes what you do, the return-visit alert fires when the same reader comes back, instead of appearing in the next morning's digest. And past fifty active links the flat account removes the ceiling. Open the demo dashboard to see whether any of that is worth $9 to you.
Frequently asked questions
Can I tell if someone opened a link I did not create myself?
No. A link reports to whoever owns the destination, and that is a property of the link rather than of any tracker, ours included. If you pasted a public URL, a shared drive address or somebody else's file into a message, the information about that open belongs to them and never reaches you. The workaround is not a tracker but a change of link: host the thing you are sending, or a copy of it, at an address you generated, and send that instead.
Does the recipient know the link is tracked?
Not unless you tell them or you switch on the email gate, which shows a form saying the address is shared with the sender. That asymmetry is real and it is worth closing yourself: a sentence in the covering message saying the link reports back costs nothing and tends to help, because a reader who knows a document is measured treats it as one somebody cares about. Nothing is installed on their device either way — a tracked link opens a web page, and closing the tab ends it.
Why did the link register an open seconds after I sent it?
Almost always a machine. Corporate mail filters rewrite the URLs in inbound messages and scan the destination before the recipient ever sees the mail, and chat and messaging apps request a link in order to build a preview card. Both look like a click to anything counting requests. PDFTrackr classifies those automated opens at session close and excludes them from the counts, and the dashboard shows what the filter removed — but as a rule of thumb, an open in the first minutes on a corporate address is not a person.
What is the difference between an open and a read?
Everything that matters. An open says a request arrived; a read says something was taken in. Measured across 3,745 recorded sessions on multi-page documents, 12.2% rendered no page at all and 33.2% rendered the first page and stopped, so 45.4% of what a counter would report as opens involved reading at most one page. The median session that stopped on page one ran 13.9 seconds against 71.4 seconds for one that went further — two completely different events that an open count reports identically.
Can I see who opened the link rather than just that it was opened?
Only if the reader tells you. A shared link carries no identity: it is the same URL for everybody who has it, so the record shows sessions rather than names. Two things attach a name. The email gate asks each reader for an address before the document opens, which is a claim they typed rather than a verified identity. Or, on Pro, bulk personalised links generate a separate link per recipient, so the link itself is the identity and nobody has to type anything.
Sources
- Apple — Use Mail Privacy Protection on Mac: remote content is privately downloaded in the background when you RECEIVE a message rather than when you view it, and the reader's IP address is hidden from the sender. ⚠️ Channel disclosure: support.apple.com did not answer a direct fetch from our network, so this was read through search-engine retrieval of Apple's own guide (accessed 2026-09-14)
- Google — Gmail Help, turn images on or off: the page states that Google scans images for signs of suspicious content before you receive them, that senders cannot use image loading to get information about your computer or location, that senders cannot use the image to set or read cookies in your browser, and that Gmail checks the images for known harmful software. ⚠️ It describes no image proxy and is not cited for one (accessed 2026-09-14)
- Microsoft — Safe Links in Microsoft Defender for Office 365: URL scanning and rewriting of inbound mail during mail flow, plus time-of-click verification — a machine checks the destination before the reader reaches it. ⚠️ Channel disclosure: learn.microsoft.com did not answer a direct fetch from our network, so this was read through search-engine retrieval of Microsoft's own documentation (accessed 2026-09-14)
- PDFTrackr — the free plan's limits, the retention windows and the Pro price, published on the site's own pricing surface (accessed 2026-09-14)
Send a link that answers the question
Host the file, send the link you generated, and see every open with the pages that were actually read. Free: 50 files, 50 links, 12 months of history, no card.
Create a free tracked linkKeep reading: how to know who opened your PDF, opened, clicked or read, and email tracking versus document tracking. Or start with how free PDF tracking works.
Oleh Tsyupa
Founder, PDFTrackr
Has analysed over 3,000 tracked document-viewing sessions on PDFTrackr.