Do Document Tracking Tools Work on Mobile?

If the person you are sending to lives on their phone, test it on yours before you rely on it: create a free tracked link, open it from your own mail app, and watch the record arrive — or open the live demo to see what the record contains first.

A link works on a phone, a file does not

The dividing line is not the device, it is what arrives on it. When a PDF is attached to an email, the phone's mail app shows it with its built-in viewer, and from there the reader can save it to Files or open it in Books — Apple's own guide describes exactly that route for a PDF received in Mail or Messages. Every one of those steps happens between the reader and their handset. The file is a copy, it contains no connection back to you, and whether it is read on a phone, a tablet or a laptop, what comes back to the sender is the same thing: nothing.

A link is different because the document never lands on the phone as a file. Tapping it opens a web page, and the page renders the PDF one page at a time inside the browser. Every page that renders is an event the page can record — which page, when, and for how long it held the screen — and that is as true of Safari on an iPhone or Chrome on an Android handset as it is of a desktop browser. This is why the honest answer to the mobile question is a question back: what did you send?

What is worth checking in any tool is whether its viewer is usable on a small screen, because a viewer that fights the reader corrupts the record it produces. PDFTrackr's viewer fits the page to the width of the screen, lets the reader pinch to zoom and swipe to turn the page, and below a phone's width moves the page controls to a bar along the bottom, where a tap on either half of the page also turns it. The general mechanism, device aside, is at what PDF tracking is.

In-app browsers and preview cards

On a phone, a link is often not opened by the browser at all. Messaging and social apps commonly open a tapped link inside their own embedded browser, so the reader never leaves the app. Google's Custom Tabs documentation is candid about the difference: an embedded web view does not share state with the phone's browser, which is why a reader who is signed in somewhere in Chrome arrives as a stranger inside the app. For a tracked link that is mostly harmless — the page still renders and still records — with one exception covered in the next section: an embedded browser can be destroyed along with its host app before the page is told anything.

The second phone-specific effect happens before anybody taps. Paste a link into a text or a chat and a preview card appears, and the card is built by fetching your link. That fetch is a real request and it is not a person reading. Which device makes it, and when, depends on the app, and the mechanics are set out at how to track a PDF you sent by text message. The practical consequence is the same on every messaging channel: the first open after a send is often a machine, and a tool that counts it as a reader is reporting your own send back to you.

The hardest part on a phone: when reading stops

Knowing that somebody started reading is easy on any device. Knowing when they stopped is where phones differ, and it matters, because every duration in a reading record depends on it. On a laptop, closing a tab gives the page a moment to send a last message. On a phone, the reader swipes to another app, locks the screen or clears the app switcher, and the browser platform documentation says plainly what follows: the events a page would use to say goodbye are not fired in those cases, and the transition to hidden is often the last change a page can reliably observe, especially on mobile.

So a viewer built for phones listens for that moment rather than for the close. PDFTrackr sends the end of a session when the page becomes hidden or is being put away, using the browser's beacon mechanism, which exists to deliver a small message as a page goes; the older unload events are kept only as fallbacks behind it. And because an in-app browser can be torn down before even that fires, the viewer also writes the current page's dwell periodically while it is still open, over the same request path that delivers page turns.

The figure at the top of this page is about our own instrument rather than about phones: most durations in our corpus were rebuilt from page dwell, largely because most of those sessions predate the recording of closing reports. Rebuilding from dwell is still the fallback that matters on a phone, because it needs nothing from a page that is being torn down — and how the rebuild is bounded is set out at how long someone spent reading.

What each way of sending reports when it is opened on a phone

The verdict, bounded to this table: when the reader is likely to open what you send on a phone and you want to know what happened inside the document, the tracked link is the pick, because it is the row that reports page by page without asking the reader to install anything, and the one that separates a previewer's fetch from a person before you read anything into a first open. Where the plain attachment genuinely wins is the reader's side: it opens with no signal and no tap into a browser. Where an installed app wins is anything the reader has to do rather than read, such as signing.

When Pro becomes the right choice

Everything above is on the plan that costs nothing — per-page reading on any device, the email gate, the exclusion of automated opens, 500MB, 50 files, 50 active share links, twelve months of history, no card. Somebody sending a few documents a week to people on their phones never needs to pay us.

Pro becomes the right choice when you need names and your readers are on phones. The free way to learn who read a shared link is an email gate, and a form on a phone keyboard is real friction — the one thing a mobile reader is least willing to put up with. Once you are sending the same document to a run of named people, bulk personalised links give each of them their own link, so the record says who read it without anybody typing an address into a phone. And past fifty active links the flat account removes the ceiling. Look at the demo dashboard before deciding.

Keep reading: what PDF tracking is, how to track a PDF you sent by text message, and how long someone spent reading. Or start with how free PDF tracking works.