Know is the first tab on the left rail, and it is where signing in puts you: the CMS home preference defaults to /know. Every number on it comes from your own published site, collected by scripts your site build ships on your own domain. There is no third-party analytics script, no external vendor seeing your traffic, and no tag manager to install. Anyone whose role reaches analytics:read can open it.
The old /analytics URL still works and redirects here.
Reading the header
The header is three lines of text and one control:
- the eyebrow Performance
- the title Know
- the subtitle All content · compared with the prior period
“All content” is literal — Know is never scoped to a page, a label or a content type. To look at one page, use the Page Analytics panel in the editor instead.
The date-range picker sits at the right of the header, and it is the only date control on the screen. Every widget below follows it, with one exception noted in the widget stack. The default is Previous 30 days.
Your choice is remembered in session storage, under a key specific to Know — so it survives moving around the CMS in the same browser tab and is forgotten when you close that tab. It is not shared with the editor’s panel, which keeps its own range.
How far back the picker will let you reach is a plan quota rather than a feature gate: presets that would start before your cutoff render locked, and the footer tells you your limit. That is covered in full under how far back your plan reaches.
The comparison period
“Compared with the prior period” means the window of equal length immediately before the one you selected — from - span up to from. It is not a calendar comparison.
So a Previous 7 days range selected on a Thursday compares against the seven days before that, ending Thursday — not against last week’s Monday-to-Sunday. If you want a calendar week against a calendar week, pick Last week and then compare it yourself against the week before; there is no calendar-aligned comparison mode.
The comparison window is clamped to your retention cutoff, so a delta never mixes in data from before your plan’s history reaches.
Chart granularity
You never choose a bucket size. Every chart on Know derives it from the length of the range you picked:
| Range span | Bucket size | Bucket unit |
|---|---|---|
| 1 day or less | 1 hour | hour |
| Up to 14 days | 1 day | day |
| Up to 90 days | 7 days | week |
| More than 90 days | 30 days | month |
Buckets with no data are filled in as zero rather than skipped, so a line never has a gap in it — a flat stretch at zero means no traffic, not missing data. The maximum any single query can span is 365 days, on every plan; that cap and the reason for it are covered under the 365-day rule.
The five KPI cards
The KPI row is five cards. Each shows its total for the selected range and a colored delta chip against the prior period. Four of them also carry a sparkline; Leads does not, because there is no time series behind it.
| Card label | Query metric | What it counts | Sparkline? | Prior-period delta? |
|---|---|---|---|---|
| Page Views | pageViewsMetric | Every page-view row in the window — one reader viewing five pages counts five times | Yes | Yes |
| Unique Sessions | uniqueSessionsMetric | Distinct session ids that recorded at least one page view | Yes | Yes |
| Unique Visitors | uniqueVisitorsMetric | Distinct persistent visitor ids — a reader who returns next week counts once | Yes | Yes |
| Average Page Views Per Session | averagePageViewsPerSessionMetric | Mean pages per session, over sessions with at least one page view | Yes | Yes |
| Leads | derived — the sum of per-page form fills | Form fills attributed to your pages in the window | No | Yes |
Two details that surprise people:
- Every card formats its value as a rounded whole number, including Average Page Views Per Session. A true average of 2.4 pages per session displays as 2. Query
averagePageViewsPerSessionMetricdirectly if you need the decimal. - A delta chip reads
—when the prior period had nothing to compare against. The change is only computed when the prior value is greater than zero, so a brand-new site shows no deltas at all for its first period.
A session is not a visit and a visitor is not a person. The exact definitions — and why Unique Sessions and Total Sessions both count distinct session ids yet answer different questions — are in the metrics reference. Session, visitor, event and journey stage each have a one-line definition in the glossary.
The widget stack
Below the KPI row, Know is a single scroll. In order:
| # | Widget | In one sentence |
|---|---|---|
| 1 | Top insights | Two heuristics — an OPPORTUNITY page that converts far above your average, and a RISK page that pulls traffic and never converts — with a Refresh control. |
| 2 | KPI row | The five cards above. |
| 3 | Page views over time | The page-views line for the selected range, subtitled “Real traffic across the selected range”. |
| 4 | Where readers spend time | A donut of engaged (active) minutes by content type. |
| 5 | Top performing pages | Your pages by lead conversions — Page, Sessions, Leads, CR. |
| 6 | Journey funnel | Sessions → Engaged → Explored 3+ pages → Converted, for your busiest entry content type. |
| 7 | Top growth and Top decline | Two cards, side by side, ranking pages by how far their conversion rate moved against the prior period. |
| 8 | Search gaps | Permanently empty today — see below. |
| 9 | Sessions by channel | Your top five inbound UTM sources. |
| 10 | Top referrers | Referring hosts by sessions, top eight. |
| 11 | Most viewed videos | Videos by unique viewers, with watch time. |
| 12 | Sessions by geography | A US state map and a world map, side by side. |
| 13 | Broken links | The current broken external links found by the crawler. |
Everything else on Know is free on every plan, including Free. Leed’s product rule is that capture never stops — every tier records the same events — and only the reporting side is ever gated. What differs between plans on this screen is those two widgets and how far back the picker reaches.
Two of these widgets are clickable, which is not obvious from looking at them: a row in Top performing pages opens that page in the editor, and a row in Most viewed videos opens that asset. The rest are read-only.
Broken links is the one widget that ignores the date range. It shows the state of your site at the last crawl, not a window of history, and its subtitle says so: “from the latest link crawl”. It is produced by the daily link check.
Every widget’s exact question, backing endpoint, columns and empty-state string is set out row by row in the widgets reference.
Widgets that are honestly empty
Know is built on a rule worth knowing about before you conclude something is broken: a widget with no real source behind it renders an honest empty state rather than a plausible-looking number. Nothing on this screen is filled in with sample or estimated data.
What Know does not do
Three absences catch people out, all of them deliberate:
- There is no click-to-zoom on the trend chart. Clicking a point on Page views over time does nothing. That behavior existed on the retired
/analyticsscreen and was not carried across. - There is no per-widget date override. One picker drives the whole page. If you want two ranges side by side, open two tabs — the remembered range is per tab.
- There is no export button. Nothing on Know downloads as CSV. To get the underlying rows out, query the metric directly or ask over MCP.
Where the rest of analytics lives
Know is the site-wide view. For one page rather than the whole site, open the Page Analytics panel in the editor, which adds filters Know does not have — minimum active time, session start, email batch and remove-bounces. For the definitions behind every number here, the metrics reference covers the counted metrics and the list metrics reference the ranked tables. And you can skip the dashboard entirely — the Leed Assistant will answer “how did the pricing page do last month” and render the chart in the chat, and an external AI client can do the same over MCP.