See who read it
The Analytics tab shows reading trends and recent activity.
guide~2 minVerified v0.237.0
Goal
Understand reading activity without treating a view as proof of understanding.
What you'll have
Reading trends, recent activity and reported browser faults for your artifact.
Needs
An artifact with recorded activity. Owners see the overview and errors; Editors see Recent activity. Viewers and Commenters get a page that opens the artifact instead.
Prompt
Steps
The reading trend
- Open Analytics. Its overview covers 14 days: views, people reading within the last minute, and distinct errors. Views by day draws the trend. A trailing + on views means the latest 500 events give a lower bound.
- Read Who opened it. People are named only when signed in and on the access list. Public-link visits are counted without names. Anonymous visitor labels change each day, so they cannot produce a unique-reader count across days.
The ledger
- Open Recent activity for reading sessions and submissions, including version, path, device, country and browser when recorded. Bots are hidden until Include bots is selected; link previews and crawlers are excluded from the reading figures.
Errors
- Read Errors for up to 20 distinct faults last seen within 14 days, newest first. Each shows its message, source script and line, version, lifetime occurrence count and last occurrence. Long text is shortened.
What is not shown
There is no error notification or error page-path breakdown. An empty activity state can offer opening and sharing the page before showing figures.
Check it worked
An admitted visit appears with its version and path. A named reader appears only when the identification conditions are met.
If not
A dash or read error means the source could not be loaded; it is not zero. Check the period, bot filter and the visitor's access.
Variations
Visitor answers live on Data. A project report combines activity across artifacts.