Hi community,
More Confluence data has come into Atlassian Analytics!
New tables for Confluence attachments, whiteboards, databases and space permission are now available. On top of this, we’ve also added new attribute columns to existing Confluence tables. With these new data points, you'll be able to see a deeper picture of how your teams interact with content in Confluence and much more.
Refer to our schema documentation for details on all the tables and columns mentioned below.
Here’s a demo with several examples of how to use the new Confluence tables:
Confluence content types are expanding. In addition to the existing page and blog post data, data for whiteboards and databases are now available.
In the schema browser for visual mode queries, you’ll find a new Whiteboard table and Database table, as well as a new mapping and metadata tables that start with Content:
Database
Whiteboard
Content label
Content property
Content restriction
Content contributor mapping
Content favorited by mapping
Content updated by mapping
Content watcher mapping
The “Whiteboard” and “Database” tables only contain data for their respective content types. However, the tables that start with “Content” contain data for all content types (pages, blog posts, databases, and whiteboards). For example, in the “Content contributor mapping” table, each contributor for each content type will have one row.
Note about existing page-specific mapping tables
Since the new “Content” tables duplicate data in existing tables, we’ll deprecate the following seven tables in the future:
Page contributor mapping
Page favorited by mapping
Page label
Page property
Page restriction
Page updated by mapping
Page watcher mapping
We’ll send out a separate notice to make sure you have enough time to make changes to your existing dashboards. But we highly recommend you use and migrate to the new “Content” tables as soon as possible to minimize your migration effort later on.
To go deeper into your Confluence ecosystem, you now have visibility into all your attachments through these three new tables:
Attachment
Attachment label
Attachment property
Through the existing “Space viewer mapping” table, you can already see which user or group can view a space. With the new Space permission mapping table, you’ll be able to get the permission type (either space admin or anonymous) that each user or group has for a space.
The “Links” column stores hyperlinks that are present in the comment, page, or blog post, and the “Extensions” column stores the extensions that are present.
Note that the values for both columns are stored in arrays, so all hyperlinks or extensions for a particular comment, page, or blog post are stored in one row.
The content hierarchy in Confluence is very flexible. For example, you can have a parent database with child pages or a parent page with child whiteboards and so on. For more comprehensive reporting on this hierarchy, we’ve added two parent ID columns to the “Comment” and “Page” tables:
Parent database ID
Parent whiteboard ID
For new Data Lake connections, the new tables and columns will automatically be available.
For existing Data Lake connections, an organization admin needs to edit the connections to get the new tables and columns. They can edit the connection and save it without making any changes. Read more about editing Data Lake connections.
Now that we have data for more content types, we’re working on new dashboard templates to further speed up your Confluence reporting. Stay tuned!
Comment below or contact support if you have any questions or concerns. Thanks!
Tina Ling
1 comment