To know if someone actually read your document (vs. just skimmed it), look at time spent per page, scroll depth, completion, revisits, and (for PDFs) searches. One “opened” event isn’t enough; you want a consistent reading pattern across pages.
Quick steps (2 minutes)
-
Share your document with a trackable link.
Result: Viewers open the document in a web viewer (not as an attachment). -
(Recommended) Turn on email verification on the link.
Why it matters: You’ll know who the reader was, not just that “someone” opened it.
Result: Viewers identify themselves before viewing. -
Open the document analytics and review a viewer session.
Result: You can see per-page time, completion, and behavior signals.
Step-by-step: tell “read” vs “skim” (simple rules)
-
Check completion (did they reach the final pages?).
Why it matters: Completing a doc is one of the strongest “they actually read it” signals.
Result: You can classify the session as completed / partial / bounced. -
Check time spent per page (not just total time).
Why it matters: A long total time can be a tab left open; page time reveals movement and attention.
Result: You see which pages were read vs blown past. -
Check scroll depth per page.
Why it matters: Low scroll depth often means skimming; high depth suggests real reading.
Result: You can tell “read the page” vs “glanced at top.” -
Look for revisits to key pages (pricing, scope, terms).
Why it matters: Revisits usually mean the page mattered or was confusing enough to re-check.
Result: You know which section is driving the decision. -
(PDF) Check searches (e.g., “pricing”, “timeline”, “termination”).
Why it matters: Searching is active intent, not passive scrolling.
Result: You know what they’re trying to find.
A quick “score” you can use
- Definitely read: reached the end + meaningful time on key pages + at least one revisit/search.
- Likely skimmed: short per-page time + low scroll depth + jumped around a lot.
- Bounced: viewed 1–2 pages then left quickly.
Troubleshooting (common false signals)
- “They spent 45 minutes” but no page movement: tab was likely idle; rely on per-page time + page changes instead.
- Mobile sessions look “fast”: mobile users scroll differently; look at completion + revisits more than raw time.
- Multiple short sessions: combined, they may equal a full read; check total views + progress across sessions.
Quick checklist (copy/paste)
- Completion checked (end reached or not)
- Time spent per page checked (not only total time)
- Scroll depth checked
- Revisits checked
- PDF searches checked (if applicable)
- Follow-up message mapped to what they focused on