Most teams start using Confluence tables with high hopes. They create pages to track KPIs, monitor performance, and share updates across teams. At first, it works.

But over time, things break down.

Data gets outdated, pages get duplicated, and metrics such as KPI lose consistency. Eventually, teams move their tracking back to spreadsheets.

This isn’t a team problem. It’s a tooling gap.

And it becomes especially visible as organizations try to scale Confluence KPI tracking and project management in Confluence.

The problem with native Confluence Tables

For some teams, a typical KPI table in Confluence looks like this: rows for campaigns or initiatives, columns for owners, deadlines, statuses, and metrics. It’s a reasonable starting structure. But the moment the dataset grows, the cracks appear fast.

Native Confluence tables offer limited filtering and grouping capabilities. You can’t easily filter by owner or status, group by team or priority, or dynamically sort large datasets. Updates rely entirely on people remembering to come back and edit the page.

So teams compensate in predictable ways, duplicating pages for different views, exporting to spreadsheets, and maintaining multiple versions of the same dataset just to answer simple questions.

Smart Tables: a structured layer inside Confluence

Smart Tables addresses the root limitation directly. Rather than treating Confluence pages as documents with embedded tables, Smart Tables turns those tables into interactive, structured datasets without requiring teams to leave the workspace.

The shift sounds subtle. Its effects are not.

• Filtering
  Each stakeholder sees only their slice of data, by team, status, quarter, or priority. What makes this powerful is that filters are persistent, reusable views built on top of a consistent schema, so they never break and always reflect live data. One table replaces what used to require multiple duplicated pages, each drifting out of sync.

• Grouping
  As KPI data grows, a long flat list of metrics becomes impossible to scan for different teams, statuses, and priorities all mixed together with no visual hierarchy. Grouping solves this by organizing data into meaningful categories on the fly. Group by team to see how each department is performing at a glance. Group by status to instantly separate what’s on track from what’s at risk. The data doesn’t change just how you navigate it.

• Sorting
  Without sorting, the answers to the most critical questions, which KPIs are underperforming, which campaigns are delivering, and what needs immediate attention, are buried inside the data. Sorting brings them to the surface instantly. Sort by lowest performance to identify risks before they escalate. Sort by highest impact to highlight wins worth sharing. Sort by deadline to stay ahead of what’s coming. Any field, any direction, actionable in seconds.

The foundation of effective Smart Tables tracking is a consistent data structure. Each row represents a single unit of measurement: a campaign, a sprint, or a product initiative. Each column is a defined, standardized field: metric name, owner, team, status, priority, reporting period, performance value.

When every row follows the same schema, the entire table becomes a queryable dataset; that consistency is what transforms a table from a formatted list into a system.

The Atlassian Teamwork Collection: tools becoming a system

With the Atlassian Teamwork Collection, the company is making a deliberate architectural shift: away from individual apps used side by side toward a unified system where planning, documentation, and execution are deeply connected.

This reflects something real about how work actually happens. A decision made in a Confluence page triggers a project tracked in Jira. A sprint outcome updates a KPI that lives in a doc. When tools are isolated, context is lost at every handoff. The Teamwork model is designed to close those gaps.

Even within a better-connected Atlassian ecosystem, Confluence had a specific problem: the moment documentation became operational, tracking deliverables, monitoring KPIs, and managing live project data, its tables became a liability. Static by default, prone to drift, dependent on manual exports. The Teamwork vision needed Confluence to do more.

The bigger shift: from documentation to operations

Together, Smart Tables and the Teamwork Collection represent a broader transformation in how teams manage work.

Reporting consistency, one of the most persistent pain points in project management, gets addressed at the source. KPIs are defined once in a structured format in Confluence. Every stakeholder sees the same data in the same format. Reports are generated from the live source, not assembled from exported fragments.

Just as importantly, this shift doesn’t require teams to change how they work inside Confluence.

Smart Tables works effectively with native Confluence macros and elements, including smart links, attachments, code snippets, decision macros, and user mentions. Tables remain fully integrated with the rest of the page, whether it’s linking to a Jira issue, displaying media, or exporting to PDF.

What this means in practice

A team lead filters the KPI table in Confluence to view only their team’s metrics. A manager groups data by status to spot risks, while an executive sorts by performance to identify priorities before a review. No exports, no duplicate reports, no need to search for the latest version.

This is the experience that Smart Tables enables and that the Atlassian Teamwork Collection is designed to support.

Confluence KPI tracking isn’t about adding more tools or pages. It’s about making existing data structured, consistent, and interactive, with Smart Tables providing the foundation and Atlassian delivering the system that connects it all.

We’ll walk through methodology, side-by-side results, pros/cons, use-case recommendations, and a verdict. The goal: help Confluence users and decision-makers (especially those evaluating switching or upgrades) choose wisely.

Methodology & Benchmark Criteria

To make this comparison fair and meaningful, we defined the following criteria and approach:

Test setup & process

To ensure a fair and comprehensive evaluation, we created identical test tables and converted or wrapped them within each plugin. We then performed a series of common data-management tasks such as applying multiple filters, sorting by several columns, adding formulas (SUM, IF…), building pivots, exporting to CSV and PDF, and reverting changes. Throughout the process, we recorded errors, and noted points of friction that could impact the user experience.

To validate our findings, we also cross-checked vendor documentation, user reviews, and community feedback. The results below present a detailed comparison of each tool, complete with insights, commentary, and direct links to supporting documentation.

A full comparison: Smart Tables vs Table Filter vs Aura Table Filter

Below is a comparison table summarizing feature support (✓ = supported, ✗ = not supported).

Tables main features

Features	Smart Tables	Table Filter	Aura Table Filter
Live edit in Confluence pages
Consistent filtering
Calculations & excel like functions	Smart Tables supported functions	(Supports only 5 formulas for calculating columns and only 7 formulas for calculating rows)
Charts	(7 chart types, 4 themes, labels)	(15 chart types, Appearance, themes)	(Less configuration and customizations)
Pivot tables
SQL queries	Coming soon
Spreadsheets macro
Collaborative editing in Spreadsheet
Convert Confluence tables into spreadsheet
Sorting
Grouping
Search in the entire table
Sample table
Revert to Confluence table
Export table	(XLSX, CSV, Word, PDF)	(CSV, Word, PDF)	(CSV, Word, PDF)
Import table	(XLSX, CSV)	(CSV, JSON)
Tabs mode
Pagination
Support	(For every subscription)	(Premium support for advanced plans)	(Only for pro plan)

Native Confluence macro support

Macro/App	Smart Tables ( Creativas)	Table Filter & Spreadsheets (Stiltsoft)	Aura (Appanvil)
Support Atlassian smart links (Confluence page, Jira ticket)
Support external smart links
Table respects the Confluence page width and does not exceed it when media files are used
Display attachments and media files in the page viewer
View attached files right from the page viewer
Faithful Confluence page PDF export style		(Wide media files cause the table to be cropped)	(Does not support macros)
Support expand macro			(Macro titles and buttons are not visible)
Support quotes			(Displays only the text)
Support code snippets		(The native line numbering is removed)	(Displays only the text)
Support Decision macro
Clicking the mentioned username directs you to their profile
Interaction with Action item macro			(Cannot be selected)
Support Info panel macro		(Except the note panel)

Keynotes & observations

Each of the evaluated Confluence table apps brings its own strengths and focus areas, offering different approaches to data management and collaboration within Confluence.

• Smart Tables for Confluence delivers a modern experience with strong performance, intuitive design, and advanced features like global search, sorting, grouping, and import/export. Its seamless integration with Smart Links, Live Docs, and mentions makes it a solid choice for teams seeking a complete, collaborative solution.
• Table Filter by Stiltsoft remains a well-established and reliable tool, offering comprehensive filtering and pivot functionality. While its interface feels more traditional, it continues to serve teams that value stability and proven analytical capabilities.
• Aura Table Filter for Confluence focuses on simplicity and visual presentation. It offers core filtering and sorting options, making it a great fit for teams that prioritize page design and readability over advanced data manipulation.
• Support, documentation, and community involvement matter greatly when users bump into issues. Creativas, Stiltsoft, and Appanvil are active on the Atlassian community and provide tutorial resources.

In the end, all three tools address different needs, from analytical power to visual clarity, allowing teams to choose the solution that best aligns with their workflows and goals.

Usecase: Project Management with Confluence

A project management team maintains a quarterly performance report in Confluence. The report includes multiple tables summarizing:

• Project timelines and completion rates
• Team workloads and logged hours
• Budget vs. actual spend per department

The team needs to combine data from several pages, perform calculations, and group information by department to prepare a shareable PDF report for leadership.

However, native Confluence tables make this process time-consuming and inconsistent; formulas aren’t supported, data formatting often breaks during export, and preserving Atlassian’s macro design in exports is unreliable while using some marketplace apps for Confluence tables.

Solution with Smart Tables

Smart Tables allows users to apply advanced formulas to calculate totals, variances, or completion averages directly inside Confluence. The team can then use grouping to organize results by department, sorting to highlight projects with the largest budget gaps or lowest completion rates.

For deeper insights, users can apply filters to focus on specific quarters, departments, or project statuses, for example, isolating only “In Progress” projects or reviewing results from a single department. In addition, Smart Tables supports pivot tables, enabling teams to summarize complex datasets into clear, aggregated views. For example, this allows them to compare total spend versus planned budget across all departments or review average completion rates per quarter. When exporting to PDF, Smart Tables preserves the original Atlassian macro design and table layout, ensuring that charts, panels, and formatting appear consistently. This makes report sharing with leadership smooth, professional, and visually accurate.

Solution with Table Filter

Table Filter by Stiltsoft supports the team’s need for data analysis through its pivot and formula macros, allowing basic calculations for light comparisons. The team can filter by department or project status and generate summarized overviews using the Pivot Table macro. While it does not support inline grouping in the same way as Smart Tables, grouping can be simulated through pivot configuration. PDF export works reliably for table data but may not fully preserve Atlassian macro styling or complex visual layouts, sometimes requiring post-editing. Overall, it enables solid analytical reporting within Confluence but demands slightly more setup and macro configuration.

Solution with Aura Table Filter

Aura Table Filter helps the team display their quarterly report in a clean, visually structured format. It supports basic sorting, grouping and filtering, allowing managers to quickly narrow down data by department, project status, or timeframe. However, it does not support adding formulas for calculations, which limits its analytical capabilities. Additionally, Aura Table Filter is not fully compatible with most native Confluence macros, which can affect how the layout and styling are preserved during PDF export. As a result, exported pages may not fully match the original design. Aura remains a solid choice for teams that value presentation and visual clarity over in-depth data processing.

In 2025, Smart Tables for Confluence offers one of the most substantial balances of interactivity, formula power, usability, and flexibility, particularly for teams that want to work inside Confluence rather than hopping to Excel. Meanwhile, Table Filter & Spreadsheets remains a compelling, macro-rich option for advanced users building dashboards, merging data, or needing deep macro integration. The Aura table filter still may serve in simpler environments where ease and minimality are priorities.