Problem

When using the Content Manager in a space to identify stale content (pages not viewed in the past year), pages that have not been viewed in the last 12 months are displayed with Last Active = N/A and Views = 0.

However, the Confluence Analytics REST API can still return a non-zero number of views for these same pages, indicating that historical view data exists beyond the one-year retention used by the Content Manager display.

This discrepancy makes the Content Manager misleading for space admins deciding whether to archive or delete pages.

Environment

• Confluence Cloud
• Space Content Manager
• Confluence Analytics REST API:
  • `GET /wiki/rest/api/analytics/content/ {contentId}/views`
  • Analytics views REST API documentation
• Related request: CONFCLOUD-73401 - Increase Analytics Data Retention

Steps to Reproduce

1. In Confluence Cloud, check with a space the:
   1. Content Manager
   2. Pages that were viewed in the past (historical views), but have not been viewed in the last year
2. Go to Space settings → Content Manager.
3. Use the filters to focus on pages that have not been viewed in the past year.
4. Note the Last Active and Views values for an old page (it shows Last Active = N/A and Views = 0).
5. For the same page, call the Analytics API:
   1. Query via the Analytics views REST API
6. Observe that the API returns a non-zero view count for that page, despite the page not being viewed in the last year.

Expected Results

• Content Manager should not report Views = 0 for pages that have historical views recorded in Analytics API.
• The metrics shown in Content Manager should be consistent with the Analytics API (for example:
  • either show total/lifetime views, or
  • clearly label and display "views in the last 365 days" without overwriting/loss of historical information).
• Space admins should be able to reliably use Content Manager to evaluate which pages are truly never-viewed or low-value content.

Actual Results

• Content Manager displays:
  • Last Active = N/A for pages not viewed in the last year.
  • Views = 0 for those pages.
• The Analytics REST API for the same pages returns a positive number of views (historical views), even when there have been no views in the last 12 months.
• As a result, pages with historical engagement can appear as if they have never been viewed, which can lead to incorrect clean-up/archiving decisions.

Workaround

• use the Analytics REST API to retrieve and evaluate page view counts:
  • `GET /wiki/rest/api/analytics/content/{contentId}/views`
  • Analytics views REST API documentation
• Optionally, export or script against the API to identify pages that genuinely have zero or very low views.