Confluence Page Properties Report Multiple Rows -

Troubleshooting Confluence: How to Get Multiple Rows in a Page Properties Report

Confluence's Page Properties Report is a powerful tool for building automated dashboards and project summaries. However, many users run into a common roadblock: the macro is designed to display only one row per page.

If you are trying to report on multiple sets of data from a single page, you've likely noticed that the standard report only pulls the first row or aggregates everything into one messy entry. The Limitation: Why it Defaults to One Row

By design, the Page Properties macro captures "key-value" pairs intended to summarize a specific page (e.g., Status: Active, Owner: Sarah). When the Page Properties Report runs, it looks for pages with a specific label and creates one row for each page it finds.

If you put multiple rows in your source table inside the macro, Confluence typically ignores everything after the first row or merges them into a single cell.

Strategy 1: Use Multiple Macros with Unique IDs (Standard Workaround)

If you need to display multiple rows from one page, you can insert several Page Properties macros on that same source page.

Page Properties Report Not Showing All - Atlassian Community confluence page properties report multiple rows

To display multiple rows in a Page Properties Report, you must have multiple Page Properties macros on the source page(s) or multiple pages with the same label. 

By default, the report lists each page as a single row. If you need a single page to contribute multiple rows to a report, follow these steps:  1. Use Multiple Page Properties Macros 

Insert multiple macros: On your source page, add multiple Page Properties macros.

Unique IDs (Optional): If you want to pull only specific rows into different reports, give each macro a unique Property ID in the macro settings.

Standard Table: Inside each macro, insert a two-column table where the left column is the "Header" (key) and the right is the "Value" (data).  2. Configure the Report Macro 

Match Labels: Ensure the Page Properties Report macro is configured to look for the specific Label applied to your source pages.

Show All: If you have multiple Page Properties macros on one page, the report will automatically create a separate row for each macro instance found on that page.  3. Alternative: Table Excerpt (For complex tables)  Troubleshooting Confluence: How to Get Multiple Rows in

If you are trying to report on rows from a standard large table rather than key-value pairs, the native Page Properties macro is limited. Instead, you can use the Table Excerpt and Table Excerpt Include macros from third-party apps like StiltSoft to sync and filter specific table rows across pages.  Best Practices 

Consistent Headers: Use the exact same column headers in every Page Properties macro to ensure the report columns align correctly.

Hidden Macros: If you don't want the data tables visible on the source page, check the Hidden box in the Page Properties macro settings.

Page Labels: Remember that the report only finds pages that have the correct Label applied at the page level.  Page Properties Report Macro | Confluence Data Center 10.2

In Confluence, the Page Properties Report macro is natively designed to display only one row per page. If a single Page Properties macro contains a table with multiple rows, the report will typically only display the first one.

To display multiple rows in a report from a single source page, you can use these official methods and common community workarounds: Official Methods

Multiple Page Properties Macros: You can place several Page Properties macros on one page. If they have different header names, the report may display them in one row; however, if they share common headers, the report will split them into multiple rows for that same page. Better Content Archiving (by Stiltsoft)

Use Unique IDs: Assign a unique Page Properties ID to each macro on your source page. In your Page Properties Report, you can then specify which specific IDs to include, or leave it blank to report on all of them as separate entries.

These add-ons generally cost $10–$50/year for small teams and are worth it if you run operational dashboards.

To choose the right solution, ask yourself: What am I trying to track?

Common scenarios requiring multiple rows per page:

If you answer “yes” to any of the above, you need a way to break free from Confluence’s one-row-per-page constraint.