Read Proof. Viewer Analytics
Page-level analytics on every plan. Who opened your document, which pages they read, for how long, and how often they returned.
Sending a document into the dark is over. Every Docshark link records its own readership. Not just "opened", but which pages, for how long, and how often they came back.
What each session records
| Signal | What you learn |
|---|---|
| Per-page dwell time | Seconds each page stayed on screen. Which sections held attention and which got skipped. |
| Page completion | How far through the document each viewer reached. |
| Return visits | Every time a viewer came back, and when. |
| Device type | Desktop, tablet, or mobile. |
| IP region | Country-level location, derived at the edge. no raw IP is stored. |
| Viewer identity | Name and email when the link gates identity. Verified sessions are marked Verified; typed-but-unproved emails are Claimed. |
| Events | Downloads, gate acceptances, denied attempts, capture attempts, questions asked. |
Where you see it
- On the document. Opens, viewers, and a page-level read breakdown per link.
- On each link. An activity drawer with that link's own sessions and denied attempts.
- On Home. This week's reads, returning viewers, and your most-read documents.
- In Analytics. The org-wide view across every document, room, and envelope.
- In each data room. room-scoped analytics per file and per visitor.
Session replay
Open any viewer session and replay the read as a short story, not a ping log. The raw timeline folds into chapters a person would tell:
- Opened the room
- Read page 1 · 2m 36s
- Scrolled through pages 2–5. Pages held under about 3 seconds count as a skim, not a read
- Came back to page 1 · 3m 46s. Returns are marked separately from first reads
- Downloaded the file
The replay runs at a smart pace, long reads compress, skims flash by, while every label keeps the real time. It is the difference between "they opened it" and "they read the pricing page twice, then went back to page one."
What it looks like in practice
- Your proposal gets opened three times by the same person, always stopping on the pricing page. Time to follow up on price.
- A pitch deck gets 40 seconds total. Your opening pages need work.
- A contract sits unread for a week. A nudge is due before the signature request.
- A denied attempt appears from a region you did not share with. Someone forwarded the link; the allowlist held.
Privacy by design
Analytics measure reading behavior, not people. IP addresses and user agents are stored only as SHA-256 hashes, location stays at country level, and every event lands in the same tamper-evident audit trail that backs signatures. See data protection for the retention model.