How to Add Analytics to a Notion Page (2026 Guide)

Updated May 2026 · 8 minute read · Written by the team behind PageInsight

You publish a Notion page, share it on Twitter, watch a click spike in your link shortener — and then have no idea whether anyone read past the first paragraph. Notion has no built-in analytics for shared pages, the obvious answer (Google Analytics) literally cannot run inside a Notion-published page, and most of the workarounds you'll find on the first page of search are either dated, paid for a different problem, or quietly broken.

This guide gives you the full picture: why standard analytics fails on Notion, the four options that actually work in 2026, the honest pros and cons of each (yes, including ours), and a step-by-step setup if you decide to use the option we make. We'll tell you when something else is the right call.

Why Google Analytics doesn't work on Notion

The single technical fact that drives this whole question: Notion strips arbitrary <script> tags from published pages.

When you Publish a Notion page to the web, Notion's renderer reads the page's blocks and emits HTML for visitors. Anywhere a typical analytics tool would inject a script tag — at the bottom of the body, in a Code block, anywhere — the renderer either removes it or escapes it as plain text. There is no first-class "custom HTML" block on a published Notion page that lets you ship executable JavaScript. That's how Google Analytics, Plausible, Fathom, Simple Analytics, and every other script-tag analytics product works. None of them can fire from inside a published Notion page.

What Notion does support is the /embed block. An embed renders an iframe pointing to a third-party URL. The third-party URL serves arbitrary HTML and JavaScript inside the iframe, sandboxed from the parent Notion page but free to run analytics code that pings home. That iframe is the only sanctioned place to run code inside a published Notion page, and it's the mechanism every Notion-native analytics tool — including PageInsight — uses.

The one caveat for iframes: Notion lazy-loads them. An embed only fetches its source URL when it scrolls into the visitor's viewport. If your tracker iframe is at the bottom of a 4000-word guide and most readers bounce after the intro, those bouncers don't count. The fix is to place the tracker block near the top of the page (we automate that on activation).

The exception to the script-tag rule: if you serve your Notion content through a custom subdomain proxy like Super.so or Potion, the proxy renders the Notion content as static HTML at yoursite.comand you can inject any site-wide script you want from the host's settings panel. There, GA / Plausible / Fathom all work normally — but you've just paid $12-39/month for a proxy you wouldn't need otherwise.

The four real options in 2026

Every working solution falls into one of these four buckets. We'll cover them in order of decreasing setup overhead, with honest pros and cons.

Decision tree — which one is right for you

3-minute step-by-step setup (PageInsight)

If you've decided to use PageInsight, here's the literal sequence. The whole thing usually takes under three minutes from a fresh signup.

1. 1. Sign up. Visit pageinsight.satosushi.co/signup, create an account with email + password (no card). You'll land on the dashboard.
2. 2. Connect Notion. Click Connect Notionin the dashboard header. You'll be redirected to Notion's official OAuth flow. Pick the pages you want PageInsight to see — only those pages are imported. You can revoke access any time from Notion's connections panel.
3. 3. Sync pages and pick one. Once you're back on the dashboard your shared pages appear in the Notion Pages section. Find the page you want to track and click Enable. PageInsight auto-inserts a tracker iframe near the top of the page via Notion's API — there's nothing for you to copy-paste.
4. 4. Open the page in a browser. Visit your published Notion page in any browser. The first page-view event fires the moment the iframe loads. You'll see the dashboard's "Live" counter tick up within seconds.
5. 5. Watch real reads. Page views, sessions, locations, and heartbeat-based time-on-page roll into the dashboard in real time. The Top Pages section shows which of your tracked pages is pulling weight, sorted by views with average time alongside.

That's the whole setup. If something goes wrong (most common: the embed is below the fold and visitors are bouncing before scrolling to it), the help page covers the eight most common gotchas.

What metrics actually matter for Notion creators

A trap when you finally get analytics on a Notion page: drowning in metrics that don't help you make decisions. The metrics that actually move the needle for Notion content:

• Views per page. Which Notion guide is pulling weight. A guide that gets 10x the views of others is telling you what to write more of.
• Average time-on-page (heartbeat-based). Did people actually read the guide or did they bounce after seeing the title? A 4-minute average on a long-form guide means your audience is engaged. A 12-second average on the same guide means the title is doing all the work and the content is letting them down.
• Referrer. Where they came from. A spike from Twitter on the day you tweeted is expected; a spike from Google search a week later is the real signal — the content is ranking, the audience is finding it organically, you should write more like it.
• Coarse geo. Country and city. If 80 percent of your readers are in the US and you're writing for a European market, you have a positioning problem.
• Live readers (real-time). Less for analysis, more for psychology — when you tweet a guide and watch the live counter go up in real time, you know your distribution worked.

You don't need bounce rate, scroll depth, click maps, or session recording to make better Notion content. Those are tools for marketing teams running A/B tests on a homepage. Notion creators need to know which guide got read, for how long, by whom — that's it.

Frequently asked questions