Opening enterprise analytics and choosing projects to compare
In Atloria, start from the authenticated workspace and open the Admin area. On the main Admin screen, look for the Analytics card labeled Usage statistics and insights. Select that card to open Analytics & Insights.
When the analytics screen opens, first confirm that you are working from the enterprise reporting view rather than a single project workspace. This matters because project comparison only makes sense when the page is showing combined reporting across multiple projects. The page header should stay focused on Analytics & Insights, and your comparison should be built from the project selection controls and reporting filters available on that screen.
To compare projects fairly, add the projects you want to review into the same analytics view. Use the project selector, project filter, or any project-picking control shown in the analytics toolbar. As you add projects, check that each one is included in the current reporting scope before you begin reading charts or tables. If one project is missing from the selected set, the comparison will be incomplete and enterprise totals will not reflect the same group of projects.
Set the date range before you evaluate any numbers. If one project is being viewed over a different time period than another, the comparison will be misleading. Keep the same reporting window across all selected projects so activity, documentation changes, and usage patterns are measured on equal terms.
A quick visual check helps here:
- Confirm the Analytics & Insights header is visible
- Verify the selected projects are all included
- Make sure the date range is the same for the full comparison
- Review any active filters before interpreting results
If you need a refresher on enterprise-level reporting before comparing projects, see Managing Enterprise Analytics for Documentation Programs.
Comparing project metrics in analytics views
Once your projects are selected, move between the available analytics formats to see differences more clearly. In Atloria, comparison is easier when you switch between a chart view and a table view, if both are available in the current analytics screen. Charts help you spot large gaps quickly, while tables make it easier to read exact values and compare rows side by side.
In a chart, look for separate project series, bars, or grouped results that represent each selected project. This view is useful when you want to answer questions like which project is generating more documentation activity or which one is lagging behind over the chosen date range. In a table, scan project rows and compare the values in each metric column directly. This is usually the better option when you need a precise ranking.
To make the comparison more useful, sort the current view by the metric that matters most for your review. For example, if you are evaluating documentation performance, sort the table so the strongest and weakest projects rise to the top and bottom of the list. Sorting helps you avoid guessing based on visual impressions alone.
Keep your filters consistent while comparing. If one project is being measured with a different content scope, documentation area, or reporting slice, the result is no longer a true side-by-side comparison. Before drawing conclusions, verify that all selected projects are being shown under the same conditions.
Focus on these checks while reviewing the screen:
- Use chart view to spot broad differences quickly
- Use table view to read exact project values
- Apply sorting to identify top and bottom performers
- Keep the same filters active for every selected project
- Recheck the date range if results seem unexpectedly far apart
Finding stronger and weaker documentation areas across projects
Project comparison becomes much more useful when you move beyond overall totals and look at specific documentation areas. In Atloria, use the analytics breakdowns for category, area, or section whenever those reporting dimensions are available. These views help you see whether a project is strong in one part of its documentation but weak in another.
Start by narrowing the view to a documentation area you want to evaluate. Then compare how each selected project performs within that same area. One project may show stronger activity or better coverage in a section where another project is consistently low. That difference helps you separate a project-specific issue from a broader enterprise pattern.
This kind of comparison is especially helpful when overall project numbers look similar. Two projects may appear close at the summary level, but one may be carrying gaps in a particular documentation area that are hidden in the total. By opening the area-level breakdown, you can identify where the weaker project needs attention.
When you review low-performing areas, avoid assuming the problem is always the same. A weak result may come from:
- Low activity, where the project simply has less recent documentation work
- Low coverage, where key sections are missing or underdeveloped
- A combination of low activity and low coverage
Use filtered results to test each possibility. If a project looks weak only in one area, the issue may be local to that content. If the same area is weak across several projects, that points to a broader documentation pattern worth addressing at the enterprise level.
For a broader approach to turning analytics into improvement priorities, refer to Using Analytics to Prioritize Documentation Improvements.
Understanding how project activity rolls up into enterprise reporting
Enterprise analytics in Atloria combines activity from the projects included in your current reporting scope. When you look at enterprise totals, you are not seeing a separate set of numbers created on their own. You are seeing a rollup of the project activity that matches the selected projects, filters, and time window on the screen.
This is why project comparison is so important. If an enterprise total rises or falls, the change may come from one project with unusually high activity, or it may reflect smaller changes across several projects. To understand what is driving the enterprise view, compare the selected projects directly and see how each one contributes to the combined result.
A practical way to do this is to adjust the project filter while staying on the same analytics screen. Review the enterprise total with all selected projects included, then narrow the view to one project or a smaller subset. If the total changes sharply when one project is removed, that project is likely driving much of the enterprise result. If the total changes only slightly, the trend is probably spread across multiple projects.
Keep these factors in mind when reading enterprise reporting:
- Project participation: only selected projects contribute to the current total
- Reporting scope: filtered documentation areas can reduce what is counted
- Time window: enterprise trends reflect the chosen date range only
- Selected dimensions: grouped views can change how the same activity appears
When enterprise numbers seem surprising, do not treat them as abstract totals. Trace them back to the projects included in the current view and confirm whether the trend is concentrated or broadly shared.
Refining comparisons with filters and reporting dimensions
A useful comparison in Atloria usually depends on narrowing the analytics view to the exact question you want to answer. Broad project totals are helpful for an initial scan, but filters and reporting dimensions make the comparison much more reliable.
Begin with the most important controls on the analytics screen:
- Date range
- Project filter
- Documentation area filter
- Any available grouping or dimension selector
Use the date range to focus on the same reporting period for every project. Then narrow by project so only the projects relevant to your review are included. If you are investigating a specific content concern, apply a documentation area filter to isolate that part of the documentation rather than comparing entire projects.
If Atloria offers grouping options, switch the view to compare projects by the reporting slice that best matches your goal. For example, a grouped view may help you compare by team, by documentation area, or by another available dimension shown in the analytics controls. This is useful when a simple project-to-project total does not explain why one project is performing differently.
If your team reviews the same comparison regularly, reuse the same filtered setup whenever possible. A repeated view makes trend tracking easier because you are not rebuilding the comparison from scratch each time. Before sharing conclusions with managers, double-check that the same filters are still active and that no hidden constraint is narrowing the data unexpectedly.
When results look inconsistent, clear the current filters and rebuild the comparison carefully. Resetting the view is often the fastest way to confirm whether the issue comes from the data itself or from a leftover filter that changed the reporting scope.
Resolving mismatched project comparisons in analytics
If project comparisons do not look right in Atloria, start by checking what is included in the current analytics view rather than assuming the reporting is wrong. Most mismatches come from scope, filter, or visibility differences on the screen.
When a project does not appear in the comparison, first confirm that you have access to enterprise reporting and that the project is part of the current reporting scope. Then review the project filter or selection control to make sure the project is actually included. A missing project usually means it was not selected or is outside the current enterprise view.
If metrics look inconsistent between projects, compare the active settings at the top of the analytics screen. Make sure the same date range, documentation area, and any grouping or dimension settings are applied across the comparison. Even one extra filter can make two projects look dramatically different.
If enterprise totals do not match what you expected from project activity, check whether some projects or documentation areas are excluded. A total that seems too low often reflects a narrowed reporting scope rather than missing activity. Review all active filters before trying to interpret the rollup.
When a documentation area appears weaker than expected, look at both activity and coverage in that area. A low result may mean the project has less recorded work in the selected period, or it may mean that documentation in that area is incomplete compared with other projects.
Use this quick troubleshooting list:
- Missing project: review access and project selection
- Uneven metrics: align date range and filters
- Unexpected enterprise total: check excluded projects or areas
- Weak documentation area: compare activity and coverage together
If you also need to review administrative reporting availability, see Monitoring Administrative Analytics and Activity.
Overview
Use Atloria’s Admin workspace and Analytics & Insights screen to compare multiple projects in one enterprise reporting view. The goal is not just to see which project has higher numbers, but to understand how those numbers relate to documentation activity, coverage, and the reporting scope currently selected on the page.
A strong comparison usually includes four parts:
- The same projects selected in one analytics view
- The same date range applied across all projects
- The same filters and reporting dimensions
- A review of both project-level and enterprise-level results
As you work through the comparison, move between broad enterprise totals and project-specific breakdowns. Enterprise totals help you spot overall trends, while project rows, chart series, and documentation-area breakdowns help you identify where those trends are coming from. This is especially useful when one project seems to be lifting enterprise performance or when a weak area appears across several projects at the same time.
In practice, you will often use this screen to answer questions such as:
- Which project is strongest in the current reporting period?
- Which project is falling behind in a specific documentation area?
- Is an enterprise trend driven by one project or several?
- Are weak results caused by low activity, low coverage, or both?
This guide focuses on comparison inside the enterprise analytics view. It builds on the enterprise reporting approach covered in Managing Enterprise Analytics for Documentation Programs, but stays focused on side-by-side project analysis rather than general enterprise monitoring.
Prerequisites
Before you compare projects in Atloria, make sure you can open the authenticated workspace and access the Admin area. From there, you should be able to select the Analytics card and open Analytics & Insights. If you cannot reach that screen, you will not be able to build an enterprise-level comparison.
You should also have the right level of visibility for the projects you want to review. A project can only be compared if it is available in the current enterprise reporting scope and appears in the project selection controls on the analytics screen.
Have these items ready before you begin:
- Access to the Admin workspace
- Access to Analytics & Insights
- At least two projects available in the current enterprise reporting scope
- A clear date range for the comparison
- A clear question to answer, such as comparing overall activity or reviewing one documentation area
It also helps if you already know the difference between enterprise reporting and project-level reporting. If you need that foundation, review Analyzing Documentation Performance Across Projects and Managing Enterprise Analytics for Documentation Programs before continuing.
For the next step after project comparison, continue with Using Analytics Reporting Across Enterprise and Project Views.
Was this page helpful?