Flipbook Analytics That Show What Matters

Every plan includes page-level view tracking. Creator and above add time-on-page, heatmaps, geographic data, device breakdown, UTM tracking, share counts, TTS Sessions (how many unique reading sessions activated text-to-speech), and data export, with 2 years of analytics history. Business and Enterprise keep unlimited analytics history, and add new vs returning readers for readers signed in to your library.

Yes. Time-on-page tracking is available on Creator plans and above. You can see exactly how long readers spend on each page of your publication.

Heatmaps are available on Creator plans and above. They show a visual map of reader attention across your entire publication.

A TTS Session is counted each time a reader starts the text-to-speech feature from scratch in a reading session — not resuming from pause. It tracks unique sessions that used TTS, so you can measure accessibility feature adoption across your readership.

ZenFlip does not have a direct Google Analytics integration, but UTM parameters work with any analytics platform. Add UTM tags to your flipbook links and track campaigns in GA, HubSpot, or any tool you use.

Yes, data export is available on Creator plans and above. Export page-level engagement data for use in your own reporting tools.

ZenFlip analytics use no cookies and no browser fingerprinting, and write nothing to the reader's device. For an anonymous reader, a randomly generated viewer ID is held in memory for a single visit and discarded when the tab closes, alongside coarse location, browser and device type. Raw IP addresses are never stored — they are used in memory only to derive country and city. Because nothing is stored on the reader's device, the ePrivacy consent rule for cookies and similar storage does not apply. The tradeoff is that an anonymous reader returning next week counts as a new visit, which is why the dashboard reports visits rather than people. On Business and Enterprise plans, events from a reader who is signed in to your library are additionally linked to that reader's account, which is what makes new-versus-returning readership measurable; this still stores nothing extra on their device, since it uses the login they already have. That linked data identifies an individual, so you are the controller for it and should say so in your own privacy notice — it can be turned off per publication, and strict privacy mode disables it outright.