Skip to content

Viewing analytics for your publication

StudioExplanation3 min read15 views

Tagged

You built it, you published it — now, how do you find out what readers actually did? 3D Issue publications don’t keep analytics inside the platform: reader activity is forwarded to your own Google Analytics (or Google Tag Manager) property, so your data lands in the reports you already run everything else through. This page is about reading those reports; the wiring is product-specific — see Google Analytics 4 setup for Studio, and Google Analytics 4 setup (Replicate) and Google Analytics for Flow publications (e-165) for the other editors.

First: is tracking wired in?

Analytics arrive only if the publication carries your measurement ID. The checks, per product:

  • Studio: Project Settings (the cog icon) → SEO/SEM → Tracking, for a Google Analytics ID and, if used, a Google Tag Manager ID.
  • Replicate: the brand the tile’s ⋯ → Settings assigns; its Advanced section on Brands holds the ID (see Google Analytics 4 setup (Replicate)).
  • Flow: no screen exposes the field; see Google Analytics for Flow publications (e-165).

If the ID was added after the publication went out, publish again.

Where to look in Google Analytics

  • Realtime report — the sanity check. Open your live publication, click through a few pages, and watch your own visit appear within moments. If it doesn’t: confirm the ID was saved, confirm you published after saving, and check that browser privacy extensions aren’t blocking the analytics scripts.
  • Page-level reports — which pages are read and in what order; each published page is a distinct address, so the per-page numbers map to your publication’s pages.
  • Event reports — reader activity with the interactive elements: page turns, link clicks, downloads, and the elements you labeled. Every Analytics Tag (called Analytics label on some elements) you set in the editor names its element’s events, so give them recognizable names (“footer-download”, “chapter1-audio”) and they’ll be easy to isolate here (see Google Analytics 4 setup for the Studio element-label guidance).
  • Traffic sources — where readers came from: the social posts you shared (see Sharing your publication to social media), the QR code, the email blast.

The dashboard’s Stats item

A Replicate project’s tile ⋯ menu carries a Stats item alongside Share, Embed, and Settings (see Project settings, rename & delete (Replicate)). The GA route above works regardless.

Reading the numbers usefully

  • Compare opens against page-depth: many opens that stop at page 1 point at the cover or the link copy, not the content.
  • Watch mobile vs. desktop — if your audience is mostly phones, the Flow/reader experience is where quality shows (see Testing your publication on mobile devices).
  • Date-stamp your reading: a publication’s traffic spikes around the campaigns you run for it, so compare like periods.