# See who read it

> The Analytics tab shows reading trends and recent activity.

Kind: guide · ~2 min · Verified v0.163.0 · Next: [Put them in a project](https://pr-1704-stg.superartifacts.app/docs/projects.md)

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

![Analytics tab with reading figures and a daily trend](https://pr-1704-stg.superartifacts.app/screenshots/docs/analytics-overview-light.3caa9b5a.webp)

*Two weeks of reading, above the activity ledger.*

**Read the activity.** The agent explains the Analytics screenshot you share and what its counts mean.

```prompt
Help me understand the Analytics tab for my Super Artifacts page. Ask me to share a screenshot of the tab, then explain its views, readers, named readers and recent activity. Explain what the counts can and cannot tell me; do not invent missing activity.
```

## The reading trend

The **Analytics** tab shows three figures for the last 14 days: views, who is reading now (open on the page within the last minute) and errors. Under them, **Views by day** draws the daily trend and **Who opened it** names the signed-in people on the access list and counts the opens it cannot name. A public link is counted, never named. Anonymous visitors are told apart by a digest that changes every day, so there is no unique reader count across days. Link previews and crawlers are left out of every figure; the ledger keeps them, hidden unless you choose **Include bots**.

Owners see all of this. Editors see **Recent activity** only, and people who can only read or comment get a page that opens the artifact instead.

## The ledger

![Recent activity ledger with reading sessions and submissions](https://pr-1704-stg.superartifacts.app/screenshots/docs/analytics-ledger-light.c9d9105e.webp)

*Recent activity records who read which version and where.*

**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](https://pr-1704-stg.superartifacts.app/docs/collect-data.md) 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 owners 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 on the access list can be named; an anonymous visit is counted without a name.

Next: [Put them in a project](https://pr-1704-stg.superartifacts.app/docs/projects.md).