Page Analytics in the Editor

The Know dashboard answers questions about your site. The Page Analytics panel answers them about one page, without leaving the page. It is the fourth tab of the editor’s right rail — the bar chart icon, labeled Analytics — and it runs on the same metric catalog Know does, with every query scoped to the page you have open.

Opening the panel

The right rail carries five tabs: Assistant, Comments, Workflows, Analytics and Page settings. Click the bar chart icon and the panel opens beside your content; click it again to collapse the rail.

Two behaviors are worth knowing because they happen without you asking:

• Opening a live page selects the Analytics tab and opens the rail. If you spend most of your time in the editor looking at published work, the panel is where you land.
• Opening a page that has never been published, when Analytics was the last tab you had open, closes the rail instead of showing you an empty panel. Analytics on a page nobody has seen is not a useful screen, so you get your editing width back.

The panel reads analytics:read, the same privilege the Know dashboard uses. A team member who cannot see Know cannot see this tab either.

Two states before you see numbers

The numbers in this panel describe what visitors did on the published version of the page. That single fact explains both of the states you can hit before any chart appears.

stateDiagram-v2
    [*] --> NeverPublished
    NeverPublished: Never published — nothing to show, no button
    Editing: Editing the draft — panel offers View Analytics
    ReadOnly: Read-only analytics view — full panel, editing suspended
    NeverPublished --> Editing: first publish
    Editing --> ReadOnly: View Analytics
    ReadOnly --> Editing: Back to Editing

Never published

A page that has never been published shows:

Analytics are only available for published pages. Publish this page to view analytics data.

There is no button and nothing to configure. The page has never been served to a visitor, so no event carrying its id exists anywhere.

Published, currently editing

A page that has been published but is currently in a draft state shows a different message and a button:

Analytics reflect the published version of this page. Switch to a read-only view to see analytics while editing.

Clicking View Analytics puts the editor into a read-only analytics view: a blue Read-only analytics view strip appears across the top with a Back to Editing button, the body stops accepting input, and the full panel populates beside it.

Nothing is lost by switching. Back to Editing returns you to the editor with your draft intact.

The five filters

Every filter applies to every widget in the panel at once. There is no per-widget override — change Minimum Active Time and the stat cards, the chart, the timer table and all five ranked lists all narrow together.

Time Range

The shared analytics date picker, with the same presets and the same plan limits everywhere else in the product. It defaults to Previous 30 days.

The panel remembers its range separately from Know — they use different storage keys — so you can hold a quarter on the dashboard and a week on a page without one clobbering the other. Both are session storage, so both forget when the tab closes. The presets, the 365-day span cap and what happens at your plan’s retention edge are covered in date ranges and retention.

Minimum Active Time

Restricts every widget to sessions that recorded at least this much active time on the page. Idle time does not count toward it — a tab left open for an hour records almost none.

The list always contains Select (no filter) and up to three fixed options — 10s, 30s, 45s — plus two thresholds computed from this page’s own length:

• >50% reading time (Xm Ys)
• >75% reading time (Xm Ys)

Reading time comes from the page’s word count divided by the words-per-minute setting, taking the page type’s value first, then the workspace’s, then a default of 250. The same estimate appears in the panel header as ~N min read.

A fixed option is hidden when it would duplicate a computed threshold — so on a very short page, where 50% of the reading time works out to exactly 30 seconds, the fixed 30s option disappears and only the labeled one remains. The list length therefore varies from page to page. That is deliberate, not a rendering bug.

The reading-time thresholds use the words-per-minute value set on the page type, which you can change in configuring a page type.

Session Start

All or Email. Email restricts the panel to sessions that began from an email click — that is, sessions whose recorded starting event is an email arrival rather than a plain page view.

This works because a session records where it began at the moment it is created; it is not reconstructed later from referrers. The mechanism is described in how Leed tracks visitors.

Email Batch

Appears only while Session Start is Email, and lists your marketing sends. Picking one narrows the panel to readers who arrived from that single campaign, which is the fastest way to answer “did the people I emailed on Tuesday actually read the thing I linked”.

Switching Session Start back to All clears the batch selection for you, so you cannot leave an invisible filter applied.

The list is populated by your sends from sending a marketing email.

Remove Bounces

Excludes sessions with exactly one page view.

What the panel shows, in order

Everything below is scoped to the open page and to whatever the five filters currently say.

Total Time on Page is the one block that can disappear entirely. It renders only when there is active-time data for the page in the window; with no timer events at all, the card is omitted rather than showing a zero. It reports active seconds, formatted as hours, minutes and seconds — not wall-clock time with the tab open.

Top Destination Pages and Top Inbound Pages are the pair that make this panel worth opening: where readers of this page went next, and which of your own pages sent them here. Neither has a site-wide equivalent, because neither question is meaningful without a page to ask it about.

Attribution scoped to one page behaves differently from the site-wide view in a way that surprises people — on-site clicks that are dropped site-wide reappear here. That asymmetry, and why it is the right behavior, is explained in journeys, funnels and attribution.

Each block here is a metric from the list metrics reference, scoped to this page; the reference gives every column and default sort. For the site-wide view of the same catalog, the Know dashboard is the surface.

Naming mismatches worth knowing

Two headings in this panel do not match the catalog underneath them. Both are cosmetic, both generate support questions, and both are worth knowing before you go looking for a discrepancy that is not there.

• Top Referrers is backed by the metric whose catalog name is Referrers — the one that groups by host. There is a different metric called “Top Referrers” that keeps the full URL, and it is not what this block draws. The pair is untangled in the list metrics reference.
• Browsers & Devices is backed by a metric that declares exactly two columns: Operating System and Count. The heading promises browser and device detail the metric does not return.

Pages you did not author in the CMS

Pages that live in your site repository rather than in the editor get the same panel, with one addition. Instead of an editing surface beside it, you get a live preview of the page — and the panel gains a Show analytics overlay switch.

With the overlay on, per-element click counts are drawn as badges directly over the preview, honoring the same five filters the panel is using. So you can set Session Start to Email, pick a batch, and see which links that campaign’s readers actually clicked.

The overlay is covered in full — including what a gray zero badge means, and what happens below Growth — in click tracking and the overlay. Repository-authored pages themselves are described in Your Site Repository.

The panel is one of five tabs on the editor’s right rail, all of which are described in the page editor.