Notion Wiki Analytics

Updated May 2026 · 6 minute read

Most companies using Notion as their internal wiki have no idea which pages their team actually reads. You write the onboarding doc, the security policy, the engineering RFC — and then it disappears into the sidebar, possibly unread forever. Notion provides no view counts, no time-on-page, no signal at all.

This guide explains how to add analytics to your internal Notion wiki using an iframe embed, what metrics to track, and how to interpret the data to improve your documentation.

Why Notion has no built-in wiki analytics

Notion is a document editor, not a content platform. It stores and displays pages — it doesn't instrument them. There is no "page insights" panel, no view history, no reading-time estimate. The closest Notion offers is the edit history (who changed the doc and when), which tells you about writes, not reads.

Adding third-party analytics via a script tag isn't possible either — Notion strips <script> tags from rendered pages. The only executable surface in a Notion page is the /embedblock, which renders a sandboxed iframe. That's the hook analytics tools like PageInsight use.

This applies to both public pages (published to the web) and private pages (shared within your workspace). The embed fires for any user who can open the page — workspace members for private docs, or the entire internet for published pages.

How to track internal Notion wiki reads

The mechanism is simple: add a PageInsight tracker to each Notion page you want to monitor. The tracker is a small iframe embed that fires a view event when someone opens the page and sends heartbeat pings while they stay on it. You read the aggregated data in the PageInsight dashboard.

Because the tracker is an iframe and not a script tag, it works inside Notion's sandbox without any special permissions. The embed shows a small live-reader widget (you can style its placement). Data flows to the dashboard in real time.

Use cases by doc type

Which metrics matter for a wiki

Wiki analytics has different goals than content marketing analytics. You're not chasing traffic — you're confirming that the right people read the right docs.

• Views over time. A policy page that spikes once (when you send the announcement Slack message) and then flatlines has no repeat readership. That's often fine — but if you expect ongoing reference, low repeat views means the doc isn't being used.
• Average time-on-page. A 5,000-word runbook with 12-second average time means nobody reads past the title. A 500-word SLA policy with 4-minute average means people are studying it carefully. Time-on-page is the signal for whether you've written something people actually need.
• Zero-view docs. Run a monthly audit: any doc with 0 views in 30 days is either invisible (not linked from anywhere), obsolete (the team has moved on), or redundant (the same info exists in a better place). Delete or archive aggressively.
• Geo distribution. For distributed teams, city-level geo tells you which office is reading which doc. If your Singapore team never reads the US-office onboarding flow, they may have their own flow — or no onboarding at all.
• Live reader count. Mostly a curiosity for internal docs, but useful during rollouts: send an all-hands Slack message and watch the live counter on the linked doc spike in real time.

Setup in 3 minutes

1. 1. Sign up for PageInsight. Free for up to 5 trackers, no card required. Create your account →
2. 2. Connect your Notion workspace via OAuth. PageInsight requests read access and the ability to add blocks to pages. You control which pages you grant access to — PageInsight can only see the pages you explicitly share.
3. 3. Pick the wiki pages to track. From the dashboard, click Enable on each page. PageInsight auto-inserts the tracker iframe at the top of the page via Notion's API — nothing to copy-paste.
4. 4. Watch the data roll in. The next time a team member opens the page, the view fires. The dashboard updates in real time.

For teams tracking more than 5 pages, the Pro plan ($10/mo) covers 100 trackers. The Team plan ($30/mo) adds multi-seat dashboard access so your entire ops or people team can see the data.

Frequently asked questions