Read analytics

Every published document collects read analytics. They answer the question an attachment never could: did anyone actually open this, and did they get to the end?

What you can see

On every plan, including Free:

• Views and unique visitors
• Average read time — counted only while the tab is actually visible, so a document left open in a background tab doesn’t inflate it
• Average pages per session
• A daily series, so you can see the shape of a launch
• Top pages — which pages held attention
• Devices, countries and referrers — where readers came from

On Studio and above:

• Read depth and completion rate — how far through people actually got

On Agency Pro:

• CSV export of the underlying figures

You can look at the last 7, 30 or 90 days.

What stays private

The analytics are deliberately anonymous, and we’d rather explain that than have you assume otherwise:

• No cookies are set on readers. Nothing is stored on their device, so no cookie banner is needed on a page that embeds a Living Page
• No IP address is stored. It’s combined with the date, the browser’s user agent and the document id, hashed, and truncated — enough to count one person twice in a day, not enough to identify them
• No cross-document tracking. The identifier is per document, per day, so the same person reading two of your documents cannot be linked between them, and cannot be followed from one day to the next
• No session replay, no scroll heatmaps, no third-party analytics or advertising tags in the reader

Where your embeds are running

Separate from reader privacy, because it is about your site rather than your readers.

When a flipbook is opened, we record the site it was opened from. You already see this as the referrer breakdown in your own analytics. Two additions are worth knowing about:

• We record whether a view came from an embed or a share link. A referrer alone cannot tell the two apart — a site that merely links to your document and a site that frames it look identical — so the reader now says which it is.
• Where your site tells us, we record the page. A browser only ever hands an embedded reader the domain, never the path, so the page is known only when something on your site volunteers it. Our WordPress plugin does; a hand-pasted iframe does not.

This is placement data, not reader data. It is a public URL with its query string stripped, it is never joined to an individual reader, and it does not change anything in the list above.

What this means in practice

You can tell that 40 people opened your proposal and 12 reached the last page. You cannot tell which 40 people — unless you turn on the email gate, which asks readers to identify themselves and is the only feature that captures an address.

That’s a deliberate trade. A reader following a link you sent hasn’t agreed to be tracked across the web, and a document that quietly did so would be a liability for you as much as for them.

Next

UTM campaign reports — see which campaigns drive your opens (Agency and up).

Plans and pricing — what read depth and CSV export need.