How to know if someone read your document

You sent the document. Then you waited. A day passed. You started telling yourself a story: maybe they are busy, maybe they read it and they are thinking, maybe it went to spam. Delivered did not tell you any of that. Delivered means the email left your outbox. It says nothing about whether the file was opened, which pages were read, or how long anyone stayed. This guide covers the real ways to find out, what each one misses, and the one approach that also gets the document signed on the same link.

Why does delivered mean so little?

Email clients report delivery when your message reaches their servers. That is not a read. Attachments make it worse: once someone downloads the PDF, the trail ends. You are left asking in a follow-up message and hoping the answer is honest. For proposals, contracts, policies, and investor decks, honest guesses are not a workflow.

How do people try to know if a document was read?

Email read receipts

Gmail and Outlook can request a read receipt. The recipient can decline it. It fires once, it does not tell you which pages were read, and it says nothing about an attachment. For anything that matters, it is a guess dressed up as data.

Tracking pixels in email

A tracking pixel tells you the email was opened. It does not follow the PDF after it is downloaded, so the moment your file leaves the inbox you are blind again. Privacy tools and image blocking make pixels unreliable.

Attachments

Attaching a PDF feels direct. It also kills visibility. The reader can forward the file, print it, or save a copy you never see again. You get a polite reply. You do not get proof.

A tracked link instead of an attachment

Stop attaching the file. Share a link to it instead. A tracked link shows every open, which pages were read, and how long the reader stayed on each one. You see interest, not just delivery. You can add a password, an expiry date, allowed domains, and you can revoke the link any time. Learn more in our read proof feature guide.

What should you see on a tracked link?

• First open time and last activity
• Time on each page, not just total time
• Return visits to the same page (a signal they are debating that section)
• Viewer identity when the link requires email verification
• Device and region when you need to know if it was read on a phone or in the office

The part most tools miss: sign on the same link

Most tracking tools stop at the read. Then you move the file to a signing tool and the read history stays behind. Now the proof lives in two places and the story lives in none. The cleaner way is one link that shows the read and gets the signature on the same file, then seals the result with a certificate anyone can verify at a public verify URL.

How to set it up in four steps

• Upload the PDF or document you need read or signed.
• Choose link settings: password, expiry, email gate, or allowed domains if the file is sensitive.
• Send the link instead of attaching the file. Watch opens and per-page time in your dashboard.
• When the reading says ready, request a signature on the same link. Export the audit trail or share the verify link if you need third-party proof.

Try it free

Docshark includes page-level read analytics and e-signatures on the free plan: 20 documents, 10 signatures per month, audit export, no card. Send a document, watch the pages land, and sign on the same link. [Start free](/en/docshark) in two minutes or read [pricing](/en/docshark/pricing). Educational only: see our [e-signature legality guide](/en/legal/legality) for country-specific rules.