Multi-site organisations require a reporting structure that is both consolidated and precise. Group-level teams need a reliable view of performance across brands, regions, applications, or business units, while local teams need access to detailed data relevant to their own operations.

Matomo can support both requirements when the underlying measurement model is designed deliberately. Separate measurable properties, Roll-Up Reporting, custom dimensions, segmentation and permissions can be combined to create centralised reporting without removing the distinction between individual sites.

TagDataTrust is the only certified Matomo Implementation Partner in the UK. Its Matomo services support the design, implementation, governance and quality assurance of analytics environments for organisations operating across multiple websites, applications and markets.

1. The reporting problem in multi-site environments

A multi-site organisation commonly has several overlapping reporting requirements:

• A central team needs total traffic, conversions and revenue across the estate.
• Brand or regional teams need reports limited to their own websites.
• Product teams need to compare journeys across applications or digital services.
• Governance teams need consistent definitions, permissions and data controls.
• Analysts need to investigate individual sites without relying on aggregated summaries.

A single undifferentiated reporting property may simplify consolidation, but it can make ownership, permissions and analysis more difficult. Conversely, completely separate Matomo properties preserve independence but create repetitive reporting processes and make enterprise-wide analysis more difficult.

The objective is not simply to combine data. It is to establish a reporting architecture that provides aggregation where appropriate, while keeping the original level of detail intact.

Recommended action: Define the reporting audiences, data boundaries and required levels of aggregation before configuring Matomo properties. The reporting structure should reflect the organisation’s operating model rather than being based solely on the number of domains.

2. Separate measurables and the role of site IDs

Matomo allows multiple websites, applications and shops to be managed within one environment. Each measurable can have its own site ID, tracking configuration and reporting permissions.

A separate measurable is generally appropriate where a site or application has:

• Its own operational owner.
• A distinct brand or legal entity.
• Separate reporting requirements.
• Different access restrictions.
• A different tracking lifecycle.
• A need to be analysed independently from other properties.

This structure retains the original data context. Reports for each site remain available, while you can create broader reporting later through Matomo’s aggregation features.

For sections of a larger site, the design decision requires more care. Matomo’s documentation describes two principal approaches:

1. Track each section as a separate website and combine the results with Roll-Up Reporting.
2. Track one website and distinguish sections through custom dimensions, custom reports and segments.

The first approach provides stronger separation and more straightforward permissions. The second can reduce administrative overhead where the sections are closely connected and do not require separate access controls.

The Matomo guidance on tracking page sections provides a useful comparison of these approaches.

Recommended action: Use separate measurable properties where ownership, access or reporting independence is important. Use custom dimensions where the sections form part of one operating property and separation at the property level would add unnecessary complexity.

3. Consolidating reporting with Roll-Up Reporting

Roll-Up Reporting is Matomo’s principal method for aggregating data from multiple websites and applications into a single reporting view.

A Roll-Up measurable can combine selected source measurables so that central teams can report on:

• Total visits and users across a group of sites.
• Combined page views, events and goals.
• Ecommerce activity across multiple shops.
• Campaign performance across several brands.
• Comparisons between regions, products or business units.
• Consolidated real-time activity.

The source measurables remain available individually. Roll-Up Reporting therefore supports aggregation without replacing the underlying site-level reports.

Matomo’s official guide to creating and analysing Roll-Ups describes the standard configuration process:

1. Open the website or measurable management area.
2. Select Add a new measurable.
3. Choose Roll-Up.
4. Select the source websites or applications.
5. Configure the relevant currency and time zone.
6. Save the Roll-Up configuration.

Roll-Ups can be structured according to the reporting hierarchy. For example, an enterprise may require:

• One global Roll-Up.
• Separate Roll-Ups for Europe, North America and Asia-Pacific.
• Brand-specific Roll-Ups.
• A Roll-Up combining websites and mobile applications for one customer journey.

Roll-Up Reporting is a premium Matomo capability. It is included in Matomo Cloud Business plans or can be purchased through the Matomo Marketplace for self-hosted Matomo On-Premise environments.

4. Preserving granularity with dimensions and segmentation

Consolidated reporting is only useful when the results can still be interpreted by the relevant business dimensions. A total for all sites may be suitable for executive reporting but insufficient for operational decisions.

Custom dimensions can preserve context such as:

• Brand.
• Region.
• Market.
• Language.
• Business unit.
• Product category.
• Customer type.
• Application area.

Matomo supports custom dimensions at action and visit scope. An action-scoped dimension can associate a value with individual page views or actions. A visit-scoped dimension can support analysis of conversions, goals and ecommerce activity by the relevant category.

For example, a multi-market organisation could define a Market custom dimension and populate it consistently across its websites. A central report could then be segmented by market while retaining the total consolidated view.

You can also apply segments to reports and API requests. A segment such as “visits where Market is United Kingdom” can isolate relevant activity without requiring a separate reporting property for every analysis question.

However, segmentation does not create a new data boundary. It filters the available data for analysis. It should therefore not be treated as a substitute for property-level access control where strict separation is required.

Recommended action: Establish a controlled taxonomy for dimensions and segments. Definitions should be documented centrally, implemented consistently and reviewed as new sites, markets or applications are introduced.

5. What this approach does not solve

A multi-site Matomo architecture with Roll-Up Reporting does not solve every reporting or governance problem.

It does not automatically:

• Correct inconsistent tracking implementations between sites.
• Standardise event names, goal definitions or ecommerce values.
• Resolve differences in consent collection or privacy configuration.
• Reconcile historical data collected using different definitions.
• Establish a single customer identity across unrelated properties.
• Replace data quality monitoring and implementation testing.
• Remove the need for documented ownership and change control.
• Guarantee that aggregated data is suitable for every business question.

Cross-domain tracking also requires a separate architectural decision. Matomo distinguishes between tracking multiple domains as one website and aggregating separate websites through a Roll-Up. These approaches are not interchangeable. Where a continuous visitor journey across domains is required, cross-domain configuration may be appropriate within one measurable. Where separation between sites is required, separate measurables and a Roll-Up may be more suitable.

The Matomo documentation on Roll-Up Reporting should be reviewed alongside the organisation’s identity, privacy and reporting requirements.

6. Permissions and data access

Multi-site reporting introduces an important access-control consideration. Local teams may need access to their own measurable, while central teams may require access to an aggregated Roll-Up.

Matomo supports permissions at the measurable level, including view, write and administration access. This allows access to be aligned with operational responsibility.

A Roll-Up should not, however, be regarded as a neutral summary. Access to a Roll-Up provides access to aggregated data from its assigned source measurables. Depending on the configuration and available reports, segmentation may expose detailed patterns within the aggregated data.

This has particular importance where brands, regions or legal entities must remain operationally separate. A user who should not access one brand’s reporting may not be suitable for access to a Roll-Up containing that brand’s data.

A practical permission model may include:

• Local teams: view access to their own measurable.
• Site owners: write access for approved configuration responsibilities.
• Central analytics teams: access to relevant Roll-Ups and source measurables.
• Governance teams: administrative access subject to strict control.
• External stakeholders: access to narrowly scoped reports or scheduled outputs.

Recommended action: Review Roll-Up membership as part of the access-control process. Assess access against the full range of data that aggregation and segmentation may make visible.

7. APIs, dashboards and operating governance

Large estates often require reporting beyond the standard Matomo interface. Matomo provides APIs for multi-site reporting, Roll-Up management and segmentation.

The Multi Sites API can support overview reporting across accessible sites. The Roll-Up Reporting API provides endpoints for managing Roll-Up measurables and source-site assignments. The Reporting API documentation provides further detail on reports and segmentation.

These capabilities can support:

• Enterprise dashboards.
• Automated reporting pipelines.
• Scheduled performance summaries.
• Data quality checks across source measurables.
• Monitoring of newly created or retired sites.
• Controlled extracts for business intelligence platforms.

Automation should be governed carefully. A dashboard that combines inconsistent event names or conversion definitions may create a false sense of comparability. Technical consolidation must therefore be supported by a measurement framework, naming standards and documented ownership.

8. A practical implementation approach

A controlled implementation can be organised into the following stages:

1. Inventory the digital estate

Document all websites, applications, subdomains, brands, markets and reporting owners. Identify which properties are active, planned or being retired.

2. Define the reporting hierarchy

Specify which properties require independent reporting and which should contribute to regional, brand or global Roll-Ups.

3. Establish the measurement model

Agree event names, goals, ecommerce definitions, custom dimensions, campaign conventions and required data exclusions.

4. Configure Matomo measurables

Create the required site IDs, tracking configurations and property-level permissions. Where appropriate, configure Roll-Up measurables after the source structure has been validated.

5. Implement consent and tracking controls

Ensure that tracking behaviour reflects the organisation’s consent requirements. Matomo configuration should be aligned with the relevant CMP integration and privacy implementation approach.

6. Validate source and aggregate reports

Test individual measurables before validating Roll-Up totals. Reconcile visits, goals, revenue and key dimensions across representative reporting periods.

7. Document and monitor the environment

Maintain a register of measurables, owners, dimensions, segments, Roll-Ups and permissions. Ongoing analytics data quality monitoring is necessary as sites and tracking requirements change.

Conclusion

Matomo can support consolidated reporting for multi-site enterprises without removing site-level detail. In most cases, the most reliable model combines separate measurables for clear ownership and access control, Roll-Up Reporting for enterprise aggregation, custom dimensions for business context, and segmentation for structured analysis.

The technology does not replace measurement governance or implementation quality. It provides the reporting framework, but the reliability of the outcome depends on consistent tracking, clear definitions, controlled permissions and ongoing validation.

TagDataTrust is the only certified Matomo Implementation Partner in the UK, providing platform-agnostic support for Matomo architecture, implementation, privacy configuration and data quality assurance.

If you’d like to hear more on this topic and set up a 1:1 call with us, please use the contact form. Contact a Consultant