Exported space analytics data shows "Last Viewed = 0" and "Views = 0" for pages with confirmed recent activity in Page Analytics UI and API

XMLWordPrintable

    • Type: Bug
    • Resolution: Unresolved
    • Priority: Low
    • Component/s: Analytics
    • None
    • 1
    • Major

      Issue Summary

      When exporting space analytics data from Confluence Cloud, some pages show "Last Viewed" and "Views" as 0 in the exported CSV file, despite having confirmed recent activity visible in both the Page Analytics UI and the Analytics View Count API (/rest/api/analytics/content/{contentId}/views).

      The three data sources — Confluence Automation ("For each inactive page" branch), Page Analytics UI, and the space analytics export — are powered by different backend endpoints and produce inconsistent results. This undermines content governance workflows that rely on exported analytics to identify and archive inactive pages.

      Steps to Reproduce

      1. Identify a Confluence Cloud page that has confirmed views within the last 12 months (verifiable via Page Analytics UI)
      2. Call the Analytics View Count API for that page:
        GET /rest/api/analytics/content/{contentId}/views
        — Confirm it returns a non-zero view count
      3. Navigate to Space Settings → Analytics → Content and export the space analytics CSV
      4. Locate the page in the exported file
      5. Observe the "Last Viewed" and "Views" columns

      Expected Result

      The exported CSV should reflect the same view data as the Page Analytics UI and the Analytics View Count API. If a page has views within the last 12 months, the export should show the correct "Last Viewed" date and view count.

      Actual Result

      Data Source Result
      Page Analytics UI Shows recent activity ✅
      Analytics View Count API Returns correct view count ✅
      Exported Space Analytics CSV Last Viewed = 0, Views = 0 ❌

      Impact

      • Content governance at scale is unreliable: Customers building automation workflows to label/archive inactive pages cannot trust the exported analytics data
      • Risk of data loss: Active pages may be incorrectly identified as inactive and archived or deleted
      • No scalable workaround: The per-page Analytics View Count API returns accurate data, but calling it individually for every page in a large space is not practical for bulk operations

      Additional Observations

      • The discrepancy appears to affect pages where the engagement type is "brief"
      • Pages with no views in the last 12 months correctly show empty/0 values — the issue is specifically with pages that do have views but are reported as 0 in the export
      • The Confluence Automation "For each inactive page" branch rule appears to evaluate correctly in most cases, but the exported data used for validation does not match

      Workaround

      Use the Analytics View Count API directly on a per-page basis to get accurate view data:
       GET /rest/api/analytics/content/{contentId}/views?fromDate=YYYY-MM-DD
       

              Assignee:
              Unassigned
              Reporter:
              Tanya -
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: