Page-level document analytics: know what they actually read
An open only tells you the door opened. Page-level analytics shows who read, how long they stayed on each page, and which pages they came back to. Here is what to track and how to read it.
By the Docshark team··5 min read
Attention heatmap
Where readers actually spend their time, page by page.
Avg page dwell
42s
Engaged sessions
9
Cover
48s
Scope
31s
Pricing
1m 12s
Terms
18s
Less timeMore timeHover a page
Four pages, one document
The reads colour them in
Pricing runs hot
Hover it for the numbers
Page-level document analytics records a session for every viewer of your link. It captures time spent on each page, pages returned to, total duration, device, browser, and region. An open can only answer one question: did they click. A session answers the real one: what did they study.
Asim Ahmed
2 sessions
Mon 09:12
2m 49s
Pages read · All 4 pages
Cover48s
Scope31s
Pricing1m 12s
Terms18s
Two days later
He came back for the price.
The first read, all four pages
Two days of quiet
He opens it again
Straight to pricing
Live demoA live read session: page timeline, dwell, and return visits.
01What does a viewer session capture?
Signal
What it tells you
Per-page time
Which sections held attention, and which got skimmed
Return visits
The pages they reopen are the pages they are debating
Completion
Did they reach the end, or stop at page 4 of 12
Viewer identity
A verified email when the link requires it
Device and region
A desktop in the office, or a phone in transit
Denied attempts
Forwarded links that hit your allowlist and bounced
Per-page time
What it tells you
Which sections held attention, and which got skimmed
Return visits
What it tells you
The pages they reopen are the pages they are debating
Completion
What it tells you
Did they reach the end, or stop at page 4 of 12
Viewer identity
What it tells you
A verified email when the link requires it
Device and region
What it tells you
A desktop in the office, or a phone in transit
Denied attempts
What it tells you
Forwarded links that hit your allowlist and bounced
02How do you read the signals?
Long time on pricing plus a return visit means a negotiation is forming. Call before they do. A 30-second skim of a 20-page proposal is a polite no forming. Change the document, not the follow-up email. Three viewers on a link you sent to one person means your champion is forwarding it. That is either great news or a reason to turn on email verification.
03When does read proof matter most?
Before asking for a signature: send the request when the reading says ready, not when the calendar does.
Policy rollouts: “everyone read it” becomes a per-person, per-page record.
Disputes: “we never saw that clause” meets a session log that says otherwise.
04How long is analytics kept?
Retention scales with your plan, with longer history on higher tiers. The capability itself is the same on every plan, including Free: page-level sessions, viewer identity, and audit export.
05Questions people ask
Do viewers know they are being tracked?
Viewers open the document through a managed link with the gates the sender set, like email verification. The analytics records access and reading activity on that link. It is the same class of record any document portal keeps.
Can I see analytics on a signed document?
Yes. Reads and signature events live on the same envelope. The engagement history stays attached to the signed record instead of dying at the handoff.
Is page-level analytics a paid feature?
No. Page-level engagement and audit export are included on every plan. Plans differ on volume and retention, not on whether you get proof.
