Track who reads your PDFs, page by page

What is PDF tracking?

PDF tracking is the practice of sharing a document as a hosted link instead of an email attachment, so that every page view, the time spent on each page, and whether a reader returns all become measurable by the sender. An attachment leaves your hands and goes dark - it can be opened, forwarded, and ignored without you ever knowing. A tracked link keeps a thread back to the document, so "did they read it?" stops being a guess.

EveryPage does this with first-party measurement inside its own viewer: there are no third-party tracking scripts, no browser extension for the reader, and no DRM. You get a clean link to share and a readership report that updates as people read. For the full picture of what each method can and cannot tell you, see the guide on how to see who read your PDF.

There is more than one way to do it, and they are not interchangeable. These are the methods in real use - EveryPage is one of them:

• A hosted viewer link. Upload the PDF to a service such as EveryPage or DocSend and share the link it gives you; the document opens in the service’s viewer, which measures pages read and time spent. This is the only method that reports reading depth, and it needs nothing installed on either side. Its limit: if you allow downloads and a reader saves the file, the saved copy is an ordinary PDF - measurement stops at the viewer’s edge.
• A tracked short link. Host the PDF anywhere and share it through a shortener like Bitly, or tag the URL with UTM parameters. Free and simple - but a click is not a read. You learn the link was opened, and nothing about whether anyone got past page one.
• Google Analytics on your own site. If the PDF lives on your website, you can fire an analytics event when the download link is clicked. Fine for counting downloads at scale, but it needs a site and a tag setup, says nothing about reading, and ad blockers eat a share of the counts.
• Email marketing click tracking. Tools like Mailchimp report who clicked the document link in a campaign, per recipient - useful for send-outs. But it measures the email, not the document: the open pixel says the email was viewed, not that the PDF was read.
• Scripts or DRM inside the file itself. JavaScript embedded in a PDF, or an enterprise IRM/DRM wrapper, can report opens even after download. In practice, modern PDF readers block embedded scripts by default, and DRM requires the reader to install or sign in to specific software - workable inside a company that manages its machines, a poor fit for sending documents to clients or investors.

No method sees everything. A hosted link measures reading precisely, but only inside its viewer; a downloaded copy goes quiet. DRM follows the file after download, at real cost to the reader’s experience. Choosing a method is choosing which trade-off fits the relationship you have with your readers.

Who uses PDF tracking

• Sales teams sending proposals and one-pagers - to see if a prospect read the proposal before the follow-up call, and which section they lingered on.
• Founders raising money - to know whether an investor actually opened the pitch deck and how far into the financials they got.
• Consultants and agencies shipping client deliverables - to confirm a report was read, not just received.
• Compliance and HR distributing policies - to evidence that a document was opened and read through, without storing anyone's IP address.

How PDF tracking works

When you upload a PDF, EveryPage stores it encrypted and gives you a shareable link (and a QR code and embed code). Recipients open the document in the EveryPage viewer in their browser - nothing to install. As they read, the viewer records each page turn and how long each page was on screen, attributes the visit to its source (direct link, QR scan, email, or embed), and assigns the reader a stable pseudonymous identity so returning visits line up - all without ever storing their IP address.

That data becomes a readership report: a read-through funnel, per-page reading time, returning-reader signals, and source attribution. It is the kind of document analytics an email attachment can never produce, because an attachment has no viewer to measure.

It is worth being precise about what a viewer can and cannot see. It measures what happens inside it: pages rendered, time on screen, return visits, and the source of each visit. It cannot tell you who a reader is unless you ask - names come from the optional email gate, not from surveillance - and it cannot follow a downloaded copy: if downloads are enabled and someone saves the file, the saved PDF is untracked. When that matters, turn downloads off and the reading stays measurable.

This is also where tracking methods diverge on privacy. Conventional document trackers log visitor IP addresses to tell readers apart; email pixels mark a recipient’s inbox; DRM demands identification before the file opens. EveryPage takes a narrower deal: readers are told apart by a salted one-way hash and their IP address is never stored - so you get returning-reader detection and per-page depth without holding personal data you never needed.

What the funnel tells you

The read-through funnel is the metric that turns a view count into a story. Say you share a 20-page deck and the funnel reads: 100% reached page 1, 78% reached page 6, 52% reached page 12, 24% reached page 20. A raw "opened" count would have told you none of that. The funnel says most readers made it past the intro, half got through the middle, and a quarter finished - so the drop-off at page 12 is where you are losing people, and that is the slide to rework.

Pair that with per-page time and you can tell the difference between a page that was read and a page that was skimmed. And because every page turn records its direction, the dashboard also reports a re-read rate and your most re-read pages from the Basic plan up - the pages readers went back to, which is where your stickiest content lives. Comparing EveryPage to DocSend for this? See the DocSend alternative page.