Reports & Analytics

The dashboard overview is the fastest place to answer whether the workspace is alive and whether the top-line numbers look normal. It surfaces headline cards such as total pages, total views, and unique viewers, then pairs those with a live 30-minute graph and direct paths into the detailed reports. Use it before opening deeper tabs.

• Top-level cards summarize the current state of the tracked workspace.
• The live graph helps confirm whether traffic is happening now or whether an issue may be blocking instrumentation.
• Featured reports make it easier to jump from the summary view into a specific investigation.

The live page views report focuses on the last 30 minutes of activity. It is best for verifying that a launch, campaign, new article, or active troubleshooting session is generating real traffic. It also helps identify which pages are actively receiving readers right now.

• Use live data to validate fresh instrumentation or a newly published Notion page.
• Use the active pages list to see which documents are currently attracting readers.
• Do not use the live report to explain long-term trends; switch to the historical reports for that.

The page views report measures total traffic volume. It is useful when the team wants to know whether readership increased, whether a launch pulled attention to a specific doc set, or whether one page outperformed another in raw demand. Nalytics lets teams filter this data by hour, day, week, or month and compare it against a previous period.

• Use page views for reach and raw demand, not for user uniqueness.
• Use period comparison to spot whether a content update or distribution push moved the number materially.
• Expect refreshes and repeat navigation to count because the report is about total consumption events.

Sessions are a better metric than page views when the question is about visit continuity. A reader can create multiple page views in one session, but once 30 minutes of inactivity pass, a new session begins. That makes the sessions report useful for understanding visit patterns without over-reading raw traffic volume.

• Use sessions when you care about distinct reading periods rather than every refresh or navigation.
• Expect a long, active reading sequence to remain one session until inactivity breaks it.
• Pair sessions with page views to understand whether volume growth came from more visits or more pages per visit.

The users report estimates unique people using anonymous identifiers such as IP context, device traits, and cookies. It is helpful when teams want to understand audience breadth rather than traffic volume. Because these identifiers are behavior-based instead of account-based, the same person may count as new if they switch devices or clear their cache.

• Use users when you need unique readership rather than total visits.
• Expect some inflation if readers clear storage, use different browsers, or move across devices.
• Interpret the metric as audience reach, not identity certainty.

The new users report focuses on readers who appear for the first time in the selected workspace or page window. It is useful for launches, campaigns, onboarding flows, and content meant to expand audience reach rather than simply re-engage the same group.

• Use new users to see whether the content is attracting fresh readership rather than only repeat traffic.
• Compare new users with total users to understand the balance of acquisition versus retention.
• Expect the number to change when anonymous identifiers reset on the reader side.

The page performance report compares tracked pages against each other using measures like page views, sessions, and users. It is the right report when the job is to identify winners, losers, and pages that deserve an update, redistribution push, or retirement.

• Use the ranking view to spot which pages pull traffic consistently and which pages are fading.
• Swap the metric lens between views, sessions, and users depending on the decision you need to make.
• Pair performance ranking with content ownership so the next action is obvious after the report is reviewed.

The location report is useful when geography matters to the content strategy, such as regional documentation, market expansion, or audience segmentation. Nalytics presents a color-coded map and table that can usually drill down to country, region, and city when the underlying signal is available.

• Use the map for a quick regional read and the table for sorting and filtering.
• Country is the most stable location layer; finer detail may vary by signal quality.
• Combine location with week time when publishing or support timing depends on geography.

Week time is the right report when the team needs to know when engagement actually happens. The heatmap highlights the days and hours that produce the strongest traffic so content owners can time launches, support staffing, updates, or review cycles more intelligently.

• Use the heatmap to spot recurring engagement windows rather than one-off spikes.
• Look for consistent hot zones before changing publishing cadence or staffing coverage.
• Pair week time with location if the audience spans multiple regions or work patterns.

Average time on page is an estimate based on sequential page-view timestamps rather than perfect direct observation. It works best when readers move through multiple tracked pages in sequence. Single-page bounces limit the calculation because there is no following event to close the timing window cleanly.

• Use this report to compare relative reading depth across pages, not as a precise stopwatch.
• Expect bounce-heavy pages to understate time because there is no second event to anchor the calculation.
• Pair average time with page views and reactions before deciding that a page is truly engaging or weak.