# Analytics

> Where a blueprint's readers came from, how on-platform arrivals are attributed, and who can open the panel.

Analytics is reported at two scopes from the same data: the **Analytics** tab
on the blueprint itself, and **Dashboard → Analytics**, across everything you
can see in the current workspace.

## Who can see it

Analytics is owner data, and access is narrower than for the tabs beside it:
the author, anyone who can edit the blueprint (team and org managers, plus
explicit ACL-edit), or a moderator. A reader who can open the blueprint cannot
open its analytics.

> [!IMPORTANT]
> It is a **premium** feature, and the plan that counts is the **author's**,
> not yours. On an org-owned blueprint the author is still the creator, so a
> team manager on a paid plan can find analytics unavailable because the person
> who wrote it is not.

## What is counted

| | |
| --- | --- |
| Views | All-time and over the selected window |
| Unique visitors | Distinct sessions, not identified people |
| Views over time | The trend across the selected window |
| Referrer domains | Where off-platform traffic arrived from |
| Agent traffic | Crawlers and AI agents, separated from humans |
| Engagement | Including the helpful / not-helpful tally |

Counts only. No reader is identified: the session is hashed, and nothing in the
panel resolves to a person.

## Traffic sources

On-platform arrivals are attributed to the surface that produced them, in the
platform's own vocabulary:

| Source | Reader arrived from |
| --- | --- |
| Direct link | A URL someone gave them |
| Explore | Browsing Explore |
| Explore (featured pin) | A featured position in Explore |
| For-you feed | The personalised feed |
| Fresh feed | The recency feed |
| Following | Following you or your organisation |
| Tag page | A tag they were browsing |
| Author profile | Your profile page |
| Bookmarks | Their own bookmarks |
| Comments | A comment thread |
| Resume reading | Picking a blueprint back up |
| Direct / other | Everything unattributable |

The breakdown shows whether a blueprint is found because people go looking for
it, or only because you sent them the link.

## Embeds

Views through an [embed](/foliums/blueprintr-user-guide/sharing/embedding-blueprints) are
counted and attributed to the embedding page.

> [!NOTE]
> Anonymous readers on the embed surface leave nothing on their device: no
> cookie is written there. Counts are aggregate rather than per-person, and no
> setting changes that.