Creators
Not vanity numbers. How often each book is opened, how far people actually read, whether they finish, and when they turn up.
Split by where the reader came from
1,382 measured sessions, by how much of the book they reached
Sessions that reached the last page
402 of 1,382 sessions. A reader who turns back and forth keeps their furthest page.
Of readers who were signed in
191 of 486 signed-in readers had read one of these books on an earlier day.
Readers who are not signed in are not counted here. Recognising them would mean keeping an id on their device or fingerprinting their connection, and MotusPage does neither — no cookie is set for analytics, and no IP reaches the application. Everywhere else on this screen, every visit counts.
By the reader’s own local hour, not the server’s
How readers open your books
Top countries
The screen is the real one — the same charts your dashboard draws, with the range control live. The figures are a sample: ours would be a claim about our traffic, and a creator’s are their own.
The histogram above is one session per bar, by how much of the book it reached. It is the difference between a book people open and a book people read — and it shows WHERE you lose them, which is the part you can do something about.
The share of sessions that reached the last page. Turning back and forth does not cost a reader their furthest page.
Seven days by twenty-four hours, in the READER'S own local time rather than the server's — so it answers when to publish, not what UTC was doing.
The share of your signed-in readers who had read one of your books on an earlier day. Anonymous readers are not counted — recognising them would mean an id on their device or a fingerprint of their connection, and neither is worth what it costs a reader.
Every read is attributed to the Gallery, a direct link, another site, an embed of yours, or one of your own pages. No referrer is ever stored.
How your readers open books, and roughly where they are. Bucketed at the edge: no IP address ever reaches the application.
Reading depth rides on the beacon that already fires at the end of a session, and the hour on the one that fires when a book opens — so none of this costs your reader an extra request. No analytics vendor is involved, no cookie is set for it, and nothing here can be resolved back to a person: depth is a tenth of a book, and the clock keeps the hour without the date.
Underneath the totals is a table of your books — reads in the range, reads all time, and when each was last updated — sortable by any of them. It is the quickest way to see which title is carrying the others.
All-time totals are always all-time. The detailed range is what varies: the widest option on your dashboard is labelled with the retention your plan actually has, rather than a rounder number that would promise more than the storage keeps.
See what each plan retainsPublish a book and the numbers start the moment someone opens it — nothing to install, no tag to add, no third party watching your readers.