For each data record you want as a separate row:
Example of three child pages:
To understand the solution, we must understand the mechanism. The Page Properties macro looks for metadata defined on a page. When the Page Properties Report macro scans that page, it maps the Rank (first column of your properties table) to the Value (second column).
Example Scenario: Imagine you are managing a "Team Skills Matrix." You have a page for "John Doe." On his page, you have a table listing three skills:
When you run the report, the output will typically only show: John Doe | Java | Expert. The subsequent rows are ignored because the report structure expects a unique set of metadata keys per page.
Whichever method you choose, follow these rules to avoid chaos: confluence page properties report multiple rows
On a separate “dashboard” page:
The Page Properties and Page Properties Report macros work together to create structured, table-like data across multiple pages.
When you want the report to show multiple rows (one row per labeled page), you need to set up your content correctly.
If you need a Page Properties Report that shows multiple rows (one row per child page) from Page Properties macros on child pages, use the built-in Page Properties Report macro configured like this:
|| Key || Value ||
| Status | In Progress |
| Owner | Alice |
| Due | 2026-04-15 |
Notes:
If you want, I can generate the exact macro code snippet or a template table for your child pages — tell me the property keys you use. For each data record you want as a separate row:
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.
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.
In Confluence, the Page Properties Report macro is designed to aggregate data from multiple pages into a single table, with each page typically representing one row in the final report. This limitation can be a hurdle for users who need to display multiple distinct records or rows originating from a single page. Understanding the Limitation Example of three child pages: To understand the
The native Page Properties macro is optimized for "key-value" pairs (like Status: Active, Owner: Sarah). When you use a Page Properties Report, Confluence scans pages for specific labels and pulls the first row of data it finds within a Page Properties macro on those pages.
If you have multiple Page Properties macros on one page or a multi-row table inside a single macro, the standard report macro often fails to treat them as separate rows, instead merging them into one entry or only displaying the first one. Method 1: The Multiple Macro "ID" Workaround
You can include multiple Page Properties macros on a single page, but to report on them effectively, you must assign each a unique ID.
Duplicated rows in page properties report - Atlassian Community
If some child pages don't define a property (e.g., one risk has no Impact), the report leaves that cell blank. No error occurs.