See who read it

You'll know how your page was read and which signed-in people returned.

The reading trend

The Analytics tab shows the last 30 days of views, readers and named readers, with a daily trend. A reader returning on another day can count again: anonymous readers are counted per day. A signed-in person is one reader across devices. Named readers are people identified by a signed-in address.

The ledger

Recent activity lists reading sessions and submissions: who, when, which version, path, device, country and browser. Bots are hidden by default; Include bots includes them in the ledger.

Answers visitors type into a form are separate from reading activity. Collect responses explains where those answers go.

Errors

When the page throws in a reader's browser, the Errors list on the Analytics tab shows each distinct fault once: the message, the script and line it came from, the version, how many times it happened and when it was last seen, newest first. It lists up to 20 faults seen in the last 14 days, and only people who manage the artifact see it. The text comes from the reader's browser, so long messages are cut short.

What is not shown

Nobody is notified when a fault happens; you see it when you open the tab. The list has no page path, because the error log does not record one. Reading activity cannot tell you whether somebody understood the page.

Check it worked

A visit appears in Recent activity, with its version and path. A signed-in reader can be named; an anonymous visit is counted without a name.

Next: Put them in a project.