How to Track a PDF You Sent by Text Message
By Oleh Tsyupa, Founder of PDFTrackr · Published 2026-09-14 · Updated 2026-09-14
7 min read12.2% of recorded sessions rendered no page at all — the link opened and nothing was read — and a plain open count reports every one of them as a view.
This is the group that matters most on a channel where the phone fetches your link before the person does. Across 3,745 recorded sessions on multi-page documents, 457 rendered no page at all and a further 1245 rendered page one and stopped, so 45.4% of what a counter would call opens involved reading at most one page. The zero-page group is deliberately left in this corpus rather than filtered out of it — automated sessions included — precisely so that it stays visible, because a measurement that quietly drops the opens nobody reads tells you the number is clean when it is only smaller. What separates the two on a phone is time: the median session that got past page one ran 71.4 seconds against 13.9 for one that did not.
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 next quote or contract is going out by text this afternoon, create a free tracked link and paste that in place of the attachment — or open the live demo first to see what the record looks like.
What a text message can actually carry
A plain SMS carries text and nothing else — it has no concept of a file. Sending the document itself normally means MMS, which wraps the file as multimedia content and hands it to the carrier, and carriers cap how large that may be. There is a newer path: RCS, the standard Google's Messages app uses and Apple added in iOS 18, carries files rather than MMS attachments where both ends and both networks support it — Google's own help page describes RCS carrying material MMS cannot, and publishes no size limit for it. What you cannot rely on is which of the two a given message will take. The MMS caps are set by each carrier and each handset on top of whatever the standard's baseline is, which is why the same PDF goes through to one recipient and comes back as a failed send to another, and it is the practical reason most people sending documents by text end up sending a link whether they meant to or not.
Whether the file arrives or not, what it tells you afterwards is the same: nothing. An attached document is a copy on a phone. It does not phone home, it cannot report which pages were opened, and the delivery receipt your messaging app may show you refers to the message reaching the device, not to a person reading the document inside it. The same boundary applies on every messaging channel — we describe it from the app side at how to track a PDF sent via WhatsApp, where the mechanics differ and the conclusion does not.
The preview problem, and why your first open is not a person
Paste a URL into a text and a rich preview card usually appears — a title, sometimes an image. Apple's own developer documentation describes Messages generating those inline previews from metadata on the page the link points at, which means the link has to be visited for the card to exist. That visit is a real request to your link and it is not a person deciding to read anything. Which device makes that request is worth knowing: independent research published in 2020 by Talal Haj Bakry and Tommy Mysk found that iMessage builds the preview on the sender's device at send time, not the recipient's — so on that platform the first request to your link can be your own phone, before the message has even arrived. Either way, a counter records it as an open.
Two more machines join in. If your recipient forwards the text to a work address, or you also sent the link by email, a corporate mail filter rewrites the URL and fetches the destination to check it before anybody sees the message. And where an app builds its previews on the receiving side rather than the sending side, a link dropped into a group chat can be fetched once for each client that renders it — which app does which is the app's own design and worth assuming nothing about.
Every one of those is an open on a naive counter, and none is a reader. PDFTrackr classifies automated opens at session close and excludes them from the counts, and the dashboard shows what the filter removed rather than quietly shrinking the number — but the habit to keep regardless of tool is to read the sessions that rendered several pages and ignore the ones that rendered none. The vocabulary for the distinction, and the measurements behind it, are at opened, clicked or read.
What each way of sending shows you
| What you send | What arrives | What you learn | What it costs the reader |
|---|---|---|---|
| The PDF as an MMS attachment | A copy on the phone, subject to a carrier size limit that varies by network | Nothing beyond a delivery receipt, which is about the message rather than the document | Nothing — it is the easiest thing for them, and that is its whole advantage |
| A tracked link (PDFTrackr) | A viewer in the phone's browser, no app and no account | Every open, which pages rendered, in what order and for how long, whether a download was clicked, and whether they came back — with automated opens classified at session close and excluded from the counts | One tap, the same as any link in a text |
| A tracked link with an email gate | The same viewer, behind a short form | The same reading, attached to whatever address the reader typed | A form on a phone keyboard — real friction, and worth it only when you genuinely need the name |
| A link to a file in cloud storage | A download or a preview, depending on the service and the phone | Usually that the file was opened, without which pages were read | One tap, sometimes a sign-in prompt if sharing was not set to public |
The verdict, bounded to this table: for a document sent by text where the answer changes what you do next, the tracked link is the pick, because it is the only row that reports what happened inside the file and the only one that separates the machine opens — which on this channel are routine enough to expect — from the human ones. Where the plain attachment genuinely wins is friction: it is the easiest possible thing for the recipient, it works with no tap and no browser, and if the person on the other end is not technical that can matter more than the record does.
The steps
One. Upload the PDF and generate a share link. Leave downloading on for anything a customer might need to keep — a quote, a contract, a policy schedule. Blocking the download of a document somebody is expected to act on reads badly and helps nobody.
Two. Skip the email gate unless you truly need the name. On a phone keyboard a gate is real friction, and when you are texting one named person you already know who opened it. The gate earns its place when a link gets forwarded around a household or a business and you need to know which of them read it.
Three. Write the message so the link looks like what it is. “Here is your quote — the PDF is at this link” gets tapped; a bare URL from an unfamiliar number reads as spam and, on a channel where fraudulent links are a daily problem, reasonably so.
Four. Discount the first open completely. On this channel the preview fetch is not an edge case, it is the normal path, so treat the first request as noise by default and read the first session that rendered more than one page.
Five. Read the session rather than the total, and use the return visit. Somebody opening a quote again two days later is deciding; that is the moment a follow-up text is useful rather than pushy, and it is the one signal worth being told about quickly. The general form of all of this is at what PDF tracking is.
When Pro becomes the right choice
Everything 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 texting a few documents a week never needs to pay us.
Pro becomes the right choice when texting documents is the job rather than an occasional errand. Once you are sending the same quote or schedule to a run of named customers, bulk personalised links give each number its own link, so the record says which customer read it without anybody typing an address into a phone. Once a re-open is the buying signal — and on quotes it usually is — the return-visit alert reaches you the hour it happens rather than in the next morning's digest, which on a channel measured in minutes is most of the value. And past fifty active links the flat account removes the ceiling. Open the demo dashboard and decide from the record rather than from this paragraph.
Frequently asked questions
Can I tell if someone opened a PDF I attached to a text message?
No. An attached PDF is a copy that lands on the recipient's phone, and an ordinary copy reports back to nobody — that is a property of the file rather than of your messaging app, and no document tracker changes it. One category that does is DRM, which only works because the reader has to install a licensed viewer before the file will open. The delivery or read receipt your app may show refers to the message arriving or being seen, not to the document inside it being opened. The only way to get an answer is to send a link you generated instead of the file.
Why does my link show an open seconds after I sent the text?
Because a phone visited it to build the preview card. Apple's developer documentation describes Messages generating inline link previews from metadata on the page the link points at, which requires the page to be visited — and research published in 2020 by Talal Haj Bakry and Tommy Mysk found iMessage does that on the SENDER's device at send time, so the first request can be your own phone rather than your recipient's. Add a corporate mail filter if the text gets forwarded to a work address, and one message can produce several machine opens. PDFTrackr classifies automated opens at session close and excludes them from the counts, and shows what the filter removed — but the rule of thumb holds anyway: 12.2% of recorded sessions render no page at all, and those are the ones a plain counter reports as views.
Does the recipient need an app or an account to open the link?
No. A tracked link opens in whatever browser is already on the phone — nothing to install, nothing to sign into, and no software left behind once the tab is closed. What the page can leave in the browser includes what any web page leaves: our cookie notice stores whichever answer the reader gives it, and site analytics set their own cookies on accept, both set out in our Cookie Policy — and neither is how the reader is identified in the reading record. That zero-install property matters a great deal on this channel, because the reason people send documents by text is that it works for recipients who will not install anything. The only thing that adds a step is the email gate, and that is yours to switch on or leave off per link.
Can I send a PDF by text without the file being too large?
A link sidesteps the question entirely, which is the practical reason to use one even if you do not care about tracking. Sending the file itself normally means MMS, and carriers cap multimedia message size — each carrier and handset sets its own cap on top of the standard's baseline, so the same document can go through to one recipient and fail for another. Where both ends and both networks speak RCS, the newer standard Google Messages uses and Apple added in iOS 18, the file travels that way instead and the MMS cap does not apply — but you cannot tell from your end which path a message will take. A link is a few dozen characters regardless of how large the document is.
Is it acceptable to track a document I text to a customer?
Recording how a document you wrote was read is ordinary analytics applied to a file, and the same expectations apply: be proportionate, be able to say what you hold, and do not misrepresent what the link is. Nothing is installed on the recipient's phone — the link opens a web page, it can see that page and nothing else, and closing it ends the session. PDFTrackr stores no IP address and resolves location only to a country. If you would not be comfortable saying in the text that the link reports back, that is the signal to change the practice rather than to hide it.
Sources
- Apple Developer — Technical Note TN2444, Best Practices for Link Previews in Messages: Messages in iOS and macOS automatically generate inline previews that rely on metadata from the page the link points at, so the page must be visited for the card to be built. ⚠️ Channel disclosure: developer.apple.com did not answer a direct fetch from our network, so this was read through search-engine retrieval of Apple's own technical note (accessed 2026-09-14)
- Talal Haj Bakry and Tommy Mysk — Link Previews: How a Simple Feature Can Have Privacy and Security Risks (October 2020): the measurement that iMessage and WhatsApp generate a link preview on the SENDER's device, so the first request to a shared URL can originate before the recipient sees the message. ⚠️ Channel disclosure: mysk.blog did not answer a direct fetch from our network, so this was read through search-engine retrieval of the published research and its contemporaneous coverage (accessed 2026-09-14)
- Google — Messages Help, Learn about Rich Communication Services (RCS) messaging: what RCS carries that SMS and MMS do not, including high-resolution photos and videos, typing indicators and read receipts. ⚠️ It publishes no file-size limit and no statement about where a link preview is fetched from, and this page cites it for neither (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)
- Locklizard — PDF Document Tracking (Safeguard logs document opens/views and print requests on a viewer the reader installs first): the source for the document-rights exception in the short answer and in FAQ 1. Channel: locklizard.com refuses connections from our network, so this material was read through search retrieval rather than by opening the URL. Already cited, with this date, on /how-to-know-who-opened-your-pdf, /who-downloaded-your-pdf and /track-resume-views. (accessed 2026-07-15)
- 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)
Text a link instead of a file
Upload the PDF, paste the link into the message, and see which pages your customer actually read. Free: 50 files, 50 links, 12 months of history, no card.
Create a free tracked linkKeep reading: how to track a PDF sent via WhatsApp, opened, clicked or read, and what PDF tracking is. Or start with how free PDF tracking works.
Oleh Tsyupa
Founder, PDFTrackr
Has analysed over 3,000 tracked document-viewing sessions on PDFTrackr.