Uploaded image for project: 'Analytics'
  1. Analytics
  2. ANALYTICS-129

Confluence page view data in Atlassian Data Lake

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      User Problem

      I want to be able to build charts from Atlassian Analytics that look at the number of views per Confluence page and space. This will help me understand Confluence usage in my organization and assist in cleanup activities such as archiving old/unused pages.

      Suggested Solutions

      Add additional Confluence data to the Atlassian Data Lake around page views and user usage.

      Current Workarounds

      This data can be viewed via the in-product Confluence analytics feature.

            [ANALYTICS-129] Confluence page view data in Atlassian Data Lake

            Sam Bennett added a comment -

            This would be super powerful if individual user view data was made accessible. We'd be able to track:

            • Who is looking at what pages
            • ^how often?
            • What are their emails (so we can compare against our own internal staff list)
            • ^using this, what kind of roles / seniorities are using our internal templates and resources?

            This would unlock some really powerful insights to help guide our team which supports internal staff.

            Sam Bennett added a comment - This would be super powerful if individual user view data was made accessible. We'd be able to track: Who is looking at what pages ^how often? What are their emails (so we can compare against our own internal staff list) ^using this, what kind of roles / seniorities are using our internal templates and resources? This would unlock some really powerful insights to help guide our team which supports internal staff.

            Sam Bennett added a comment -

            +1!  

            tling@atlassian.com 1 year seems an ok limitation if it helps this functionality come in quicker! It's easy to download data in Atlassian analytics, so people can manually download if they're interested in tracking over a long time. We'd be limited in historic analysis, but I think it's an ok tradeoff. My vote would be: start with 12 months' history, get the functionality out there, and if there's a demand for more history later on, investigate adding! 

            Looking forward to this

            Sam Bennett added a comment - +1!   tling@atlassian.com 1 year seems an ok limitation if it helps this functionality come in quicker! It's easy to download data in Atlassian analytics, so people can manually download if they're interested in tracking over a long time. We'd be limited in historic analysis, but I think it's an ok tradeoff. My vote would be: start with 12 months' history, get the functionality out there, and if there's a demand for more history later on, investigate adding!  Looking forward to this

            Tina Ling added a comment -

            Hi everyone,  Are there any preference or thoughts on how far back you would like to have this data?  Will  6 months or 1 year good enough?  other preferences?   This will help us make a decision on data ingestion as we finalize Confluence page view data. Thank you

            Tina Ling added a comment - Hi everyone,  Are there any preference or thoughts on how far back you would like to have this data?  Will  6 months or 1 year good enough?  other preferences?   This will help us make a decision on data ingestion as we finalize Confluence page view data. Thank you

            Italo Lobato added a comment -

            +1

            Italo Lobato added a comment - +1

              tling@atlassian.com Tina Ling
              f88288d89e3b Tracy Chow
              Votes:
              48 Vote for this issue
              Watchers:
              36 Start watching this issue

                Created:
                Updated: