Analyzing Documentation Performance Across Projects

Opening analytics views for all projects or a single project

In Atloria, start from the main signed-in workspace and open the Admin area if you want a cross-project view. On the Admin screen, look for the Analytics card labeled Usage statistics and insights. Selecting that card opens Analytics & Insights, which is the enterprise-level analytics area for reviewing activity across your documentation work.

At the top of the analytics screen, use the page title and surrounding controls to confirm what you are looking at before you read any numbers. When you are working at the enterprise level, the dashboard is meant to summarize activity across projects rather than showing only one project. If you need to focus on a single documentation workspace, switch to that project first and then open its analytics view from the project area. That project-level view is where you review performance for one project instead of the full Atloria workspace.

As you move between enterprise and project analytics, pay close attention to the filters shown near the top of the page. Before interpreting any chart, check:

• the selected date range
• the current project or All Projects selection
• any team or contributor filter that may narrow the results

These controls change what every chart and table is showing. A chart that looks low may simply be filtered to one project or one contributor.

Use the project switcher to move between All Projects and an individual project dashboard when you want to compare broad trends against project-specific results. This is especially useful when a project appears unusually active or unusually quiet and you want to confirm whether that pattern is local or part of a larger trend.

Reading documentation performance metrics on the main dashboard

The main analytics dashboard is easiest to read when you separate reader activity from documentation team activity. In Atloria, top-level metric cards usually summarize the most important numbers for the selected date range. Depending on the view available in your workspace, these cards may include measures such as page views, unique readers, search usage, and documentation activity totals tied to content work.

Treat reader-focused metrics and authoring-focused metrics as two different stories:

• Page views show how often documentation pages were opened
• Unique readers help you estimate how many different people used the content
• Search usage shows how often people searched instead of browsing directly
• content activity totals reflect work done by your team, such as edits or publishing activity

This distinction matters. A project can have strong reading traffic but little recent authoring activity, which may mean the content is stable and heavily used. Another project may show many edits and publishes but limited reader traffic, which can point to a newer documentation set or one that still needs promotion.

Look beside each metric card for any comparison against the previous period. Trend indicators help you see whether a number is rising, falling, or staying steady. Always compare these indicators using the same date range. A monthly increase is meaningful only if the card is also set to a monthly comparison.

For charts below the summary cards, use the legend to turn series on or off if that option is available, and hover over points or bars to inspect exact values for a day, week, or month. If the dashboard includes a metric selector, switch between available measures to see whether the same time period tells a different story for readers versus contributors.

Comparing activity trends across projects and teams

When you want to understand which documentation areas are growing, slowing down, or being actively maintained, start with the Projects filter. In Atloria, this filter lets you narrow the analytics view to one project or compare several projects within the same reporting window. Use the same date range for all compared projects so the results stay meaningful.

After selecting the projects you want to review, add a Team or Contributor filter if your workspace includes those options. This helps you isolate activity from a specific documentation group or from a project that is mainly maintained by one administrator. Filtering this way is useful when you are reviewing ownership, workload, or adoption across teams.

Read trend charts by matching the line or bar color to the legend, then scan for three patterns:

1. steady activity over time
2. sudden spikes in creation, updates, or publishing
3. long flat periods with little or no movement

Steady activity often points to ongoing maintenance. Spikes usually line up with releases, migrations, or cleanup work. Flat periods can reveal neglected projects or projects that are complete but no longer updated.

If Atloria shows a comparison table below the charts, sort it by the column that matches your question. For example:

• sort by views to find the most-used projects
• sort by edits to find where the team is actively revising content
• sort by recent activity to spot projects that may need attention

A useful pattern is to compare high views with low edits. That often highlights mature content that many readers rely on. Low views with high edits can indicate active work on content that has not yet reached its audience.

Investigating usage patterns and content engagement

To understand whether documentation is actually helping readers, move beyond project totals and look for page-level or article-level breakdowns where available. In Atloria, these views help you identify the documentation that gets the most attention and the content that receives little or no traffic. Start by reviewing the highest-viewed pages, then compare them with low-traffic pages in the same project.

High-traffic pages often reveal what readers need most. These may be setup guides, troubleshooting pages, release-related instructions, or frequently referenced technical documentation. Low-traffic pages are not automatically a problem, but they deserve a closer look. They may be hard to find, too specialized, outdated, or no longer relevant.

Search-related analytics add another layer. If Atloria shows search usage in the analytics area, use it to understand what readers are trying to find. Repeated search activity can point to strong demand for a topic. If readers search often but engagement stays low, that may suggest content gaps, unclear navigation, or page titles that do not match the words readers use.

Time-based patterns are also important. Review traffic by day, week, or month and look for spikes after:

• documentation releases
• product launches
• internal announcements
• onboarding pushes

Then compare those spikes across projects. If most traffic is concentrated in only one or two projects, your documentation usage may be uneven. If engagement is spread across many projects, that usually indicates broader adoption of Atloria documentation across the organization.

Use these patterns together rather than in isolation. A page with high views, high search demand, and repeated traffic spikes is usually a strong candidate for continued improvement. For more project-specific analysis, see Analyzing Project Performance and Activity.

Using filters and date ranges to answer specific reporting questions

Filters are what turn the analytics dashboard from a general summary into a reporting tool. In Atloria, begin with the date range control. Use it to match the reporting window to the question you need to answer. For example, choose a custom range for a release period, a quarterly review, or a recent documentation campaign. Keeping the date range aligned with a real event makes the charts much easier to interpret.

Once the time period is set, combine it with the other available filters. A few common reporting questions map well to simple filter combinations:

When a chart or table looks unexpectedly narrow, check for leftover filters before drawing conclusions. A contributor filter from an earlier review can make enterprise results look incomplete. Reset filters to return to the default analytics view whenever the dashboard stops matching your expectations.

If your Atloria workspace includes sharing or export options for analytics results, use them after you have confirmed the filters. This is the best time to save or export because the view reflects the exact scope you want stakeholders to see. If you are preparing broader reporting for administrators, it also helps to compare your findings with the admin workspace guidance in Monitoring Administrative Analytics and Activity.

Fixing common problems when analytics data looks incomplete or misleading

When analytics results do not look right, start with the visible controls on the page instead of assuming the data is wrong. In Atloria, most confusing reports come from scope and timing rather than a broken dashboard.

If no data appears in charts, first confirm the date range. A very narrow range can remove all visible activity. Next, check whether the dashboard is set to a single project instead of All Projects. If you are in a project-level analytics view, remember that only that project’s documentation activity will appear. Also confirm that the project has published documentation available for readers, since unpublished work may not show the same usage patterns.

If metrics seem lower than expected, review every active filter. A Team or Contributor filter can reduce totals dramatically. This is especially common after comparing one group and then forgetting to clear the filter before returning to enterprise reporting.

When project totals do not match enterprise totals, verify whether some projects are outside the current scope. Archived projects, excluded projects, or projects not included in the current filter set can make the enterprise view and project rollups look inconsistent. Always compare like with like: same date range, same project scope, same contributor scope.

If recent activity appears to be missing, check whether the changes were actually published. Draft edits and published documentation do not represent the same kind of activity. Also allow for a short delay before newly published work appears in analytics.

A quick troubleshooting order works well:

• confirm the date range
• confirm All Projects or the intended project
• clear Team and Contributor filters
• verify the content was published
• refresh the analytics view and check again

If you also need to review admin-side activity and audit-related visibility, see Reviewing Security and Audit Controls.

Overview

Atloria gives you two useful ways to analyze documentation performance: an enterprise-level analytics view for cross-project reporting and a project-level analytics view for focused review inside one documentation workspace. This document is about using those views to understand how readers interact with your documentation and how your team is maintaining it over time.

The most effective way to work in analytics is to read the dashboard in layers. Start with the top summary cards to get a quick picture of reader traffic and documentation activity. Then move into trend charts to see whether usage is rising, falling, or staying steady across the selected period. After that, narrow the view with project, team, or contributor filters so you can answer a specific question instead of relying on broad totals.

As you review results in Atloria, keep these distinctions in mind:

• enterprise analytics shows patterns across multiple projects
• project analytics focuses on one project’s documentation activity
• reader metrics reflect content consumption
• authoring metrics reflect content work such as updates and publishing
• filters can completely change the meaning of a chart or table

This guide focuses on reading the analytics screens that are available in Atloria today, including the Analytics area in the Admin workspace and project-specific analytics pages. It also explains how to avoid common mistakes, such as comparing filtered project data with enterprise totals or reading a narrow date range as a long-term trend.

If you are new to the admin side of Atloria, it helps to be familiar with the navigation described in Using the Admin Workspace. If you already know where analytics lives, the sections above will help you turn the dashboard into a practical reporting tool rather than just a collection of charts.

Prerequisites

Before you start comparing documentation performance in Atloria, make sure you can access the right workspace and that you know which level of reporting you need. You do not need advanced setup knowledge, but you do need enough access to open either the Admin analytics area or the analytics view inside a project.

It helps to have the following in place:

• an Atloria account that can sign in successfully
• access to the Admin workspace if you need cross-project reporting
• access to at least one project if you want project-level analytics
• documentation that has been published, so reader activity can be measured
• a clear reporting question, such as comparing projects, checking reader growth, or reviewing recent publishing activity

You should also be comfortable moving between the main workspace, the Admin area, and individual projects. If you need help with account access first, use Accessing and Registering Your Atloria Account or Signing In to Atloria and Solving Access Problems.

Before opening analytics, decide what you want to compare:

• All Projects if you are reviewing organization-wide documentation performance
• a single project if you are checking one documentation workspace
• a specific date range if you are measuring a release, campaign, or reporting period
• a team or contributor filter if you are reviewing ownership or workload

If the Analytics & Insights screen in your Atloria workspace is marked as coming soon or has limited content, you may only be able to review part of the reporting workflow right now. In that case, use the available project analytics screens where possible and continue with Using Analytics to Prioritize Documentation Improvements when you are ready to turn reporting into action.