Pages & Tracking

The page search is designed for two different jobs. Search by page title when you are navigating a known content set, and search by page URL when you need to confirm the exact page binding that Nalytics should recognize. Title search is faster for daily operations; URL search is safer for troubleshooting.

1. Use the page title search when you know the doc name but not the exact path.
2. Use the page URL search when duplicate titles or renamed pages make title search ambiguous.
3. Open the matching page row and confirm whether it is active, bookmarked, or missing a widget action.

Nalytics separates page state so teams can distinguish what is currently emitting data from what remains analytically important. The Active list is the working set of pages that are currently being tracked. The Bookmarked list is a convenience layer for pages you want quick access to, including pages whose historical data still matters even if live tracking is disabled.

• Use Active for the pages that should contribute current events to reports.
• Use Bookmarked for pages you revisit often, including seasonal or paused content.
• Do not assume a bookmarked page is still live; confirm the active state before using it as a reporting source.

If a page does not appear inside Nalytics, the problem is usually upstream. The Notion integration may not have access to that page, the page may inherit restricted permissions, or the page may simply be too new to appear in the current sync view. Start by checking access and patience before assuming the product failed.

1. Confirm that the page is shared with the Nalytics integration or accessible through the connected Notion account.
2. Check whether the page lives under a restricted parent or private sub-tree that blocks discovery.
3. Wait briefly if the page was just created or recently moved, then search again by title and URL.
4. If the page still does not appear, reconnect Notion or escalate with the exact page URL.

Nalytics supports automatic single-page activation and broader bulk activation workflows. Those paths are preferable because the product can later remove or update the widget cleanly. The manual embed path should be treated as a fallback because it breaks the clean removal path and usually creates more maintenance work later.

1. Choose the page or page cohort inside Nalytics and activate tracking from the managed workflow.
2. Use bulk activation when you are instrumenting a large page set with consistent ownership.
3. Avoid the manual embed option unless the workspace has a special publishing need that blocks managed activation.
4. Verify the widget appears and that the page begins emitting events before expanding the rollout.

Notion databases do not expose the same embed behavior as a normal page, which means Nalytics cannot attach the widget directly to the database object. The practical workaround is to create a normal Notion page, insert a view of the database into that page, and then track the wrapper page that hosts the view.

1. Create a regular Notion page that will act as the container for the database experience.
2. Insert a linked or inline view of the database into that page.
3. Enable Nalytics tracking on the wrapper page rather than the database itself.
4. Treat the wrapper page as the measurable surface for views, sessions, and engagement trends.

A mismatch between Nalytics and Notion does not necessarily mean either system is wrong. The tools have different tracking models, placement requirements, timezone behavior, and opt-out assumptions. Nalytics only measures pages where its widget is active. Notion may use a different definition of a visit, and user privacy choices can alter the native analytics baseline.

• Widget placement matters because Nalytics only measures pages where the tracking surface is actually present and active.
• Timezone settings can shift where a view lands in the reporting window, especially around day boundaries.
• Notion's own analytics may exclude or include behavior differently depending on how users access the page and whether native tracking is disabled.

The best widget placement is usually near the bottom of the page or directly after the content block that represents the decision point. That keeps the analytics surface visible enough to collect reactions and late-page views without distracting readers from the content itself. Consistency matters more than novelty across a large help center or knowledge base.

• Place the widget after the main content or call-to-action zone, where readers naturally decide whether the page helped.
• Avoid burying the widget inside toggles, databases, or layout blocks that are often collapsed or skipped.
• Keep the position consistent across similar page types so the reading flow feels deliberate.