Basic plan

Page-by-page statistics

Track which pages were seen and how long readers spent on each.

EveryPage records a turn event every time a reader leaves a page, and rolls those events up per page number: how often each page was seen, how long readers stayed on it, and how often they came back to it.

Metrics per page

The page-stats endpoint (GET /api/v1/files/{uuid}/readership/pages) returns three numbers for every page that has data, plus the document's total page count:

  • Views — how many times a reader's time on that page was recorded, across all sessions
  • Average time — mean dwell time on the page (avgDurationMs, in milliseconds; the dashboard chart rounds it to seconds in the bar tooltip)
  • Back turns — how many of those records show the reader arriving at the page by navigating backward, the re-read signal

The dashboard plots views as the "Page-by-page" bar chart, and ranks the pages with the most back turns in a separate "Most re-read" list. The file-level share of backward turns out of all directional turns appears in the summary cards.

Reading dwell time

Views and average time answer different questions. A page with many views and two seconds of average dwell was passed through; a page with fewer views and thirty seconds was read. Turns that recorded no measurable time are excluded from the average, so the figure describes the turns that actually dwelled on the page.

How page data is captured

As readers navigate your document, the viewer posts turn events to /api/files/{uuid}/page-turns. That path is deliberately neutral: EasyPrivacy and similar ad-blocker filter lists block URL segments such as "analytics", "stats", "tracking" and "page-view", and a blocked request fails silently, so every capture route avoids those words.

Each event describes the page the reader has just left: the page number, the milliseconds spent on it, and how the reader had arrived at it — forward or back (empty for the session's opening page, which counts as neither). A final event is flushed when the reader closes the tab or navigates away. Values arrive from an unauthenticated endpoint, so implausible page numbers and durations are rejected or clamped before they are stored.

Page range links and reported data

If you've shared a page-range link — a Pro feature that limits readers to a window of pages — those readers are served a trimmed document, and their page numbers are relative to what they received. A reader restricted to pages 5–10 reports pages 1 through 6, which is where their turns land in the per-page stats.

The page count itself stays honest: a reader who only saw a window is never allowed to write the document's total page count, so a 6-page preview never shrinks a 50-page document.

Funnel vs. page-by-page breakdown

The read-through funnel answers "how many readers reached page N?" It shows drop-off: the percentage of sessions that made it through your entire document. Page-by-page statistics instead show "how long did readers spend on each page?" They complement the funnel but measure different things.

A funnel might show that 80% of readers reached page 3 but only 20% finished. Page stats tell you whether those who did reach page 3 read it carefully (high dwell) or skipped past it (low dwell). Together, they reveal both where readers exit and how they engage with the content they do see.

Availability

Page-by-page statistics are available on the Basic plan and above; free accounts see only the summary cards. Capture is not tiered — page turns are recorded on every plan, so upgrading exposes the history a document already accumulated. See plans and limits for feature availability.