Skip to main content

Introduction

Matomo (formerly Piwik) is an open-source web analytics platform that can be self-hosted or used as Matomo Cloud. The connector queries the Matomo Reporting API for visitor traffic, behavior, and conversion data scoped to a single tracked site. The connector does not distinguish between self-hosted Matomo and Matomo Cloud — both are reached through the same Reporting API, and only the base URL differs. As an analytics connector, session, event, and breakdown data are standardized so widgets can aggregate alongside ad-platform sources. To connect this data source, see How to connect Matomo to Adriel.

Data refresh strategy

Architecture data

Account structure — the Matomo instance and the list of tracked sites available to the supplied token — is resolved at connection time from the MultiSites.getAll report. The selected site ID is stored on the data source, and one data source corresponds to a single Matomo site.

Reports data

Reports data is fetched on demand. Fresh data is requested from the Matomo Reporting API whenever a widget renders — there is no nightly snapshot or daily cache tier. Returned rows reflect the Matomo instance’s current processing state, so performance on long date ranges depends on how the instance is configured to archive report data.

Architecture levels

Matomo instance → Site (idsite) → Visit → Action / Goal One Adriel data source maps to a single Matomo site. To report on multiple sites, create additional data sources.

Date range limits

The Matomo Reporting API itself accepts arbitrary date ranges. The caps above apply to the Daily and Weekly time groupings: when a query exceeds them, data outside the range may be truncated. Monthly, quarterly, and yearly groupings have no connector-side cap.

Metrics

How to read the columnsCode style like nb_visits is the literal Matomo Reporting API field name. Italic text describes how a value is produced when it doesn’t map cleanly to a single Matomo field or when it’s computed by Adriel.Data type vocabulary: Number, Currency, Percentage, Ratio, Duration, Date, Text, URL, Array, Boolean.

Users & sessions

Engagement

Events & conversions

Ecommerce

Pages & screens

Breakdowns

How to read the columnsFor platform breakdowns, the API Key is the Matomo Reporting API method that supplies the values (e.g. UserCountry.getCountry). Italic text describes a value produced by Adriel rather than returned directly by Matomo.

Geography

Devices & software

Visitor behavior

Pages & actions

Several page and action breakdowns above also have an “Exact” variant (for example, Exact Page URLs, Exact Entry pages, Exact Event Names) that returns a flat, non-hierarchical list of the same values. The Exact variants call the same Matomo methods with flat=1&expanded=1.

Events

Content

Traffic acquisition

Campaigns

Ecommerce & goals

Sites

Matomo instances can define Custom Reports. When present, these appear as additional breakdowns (for example, Klaviyo Campaigns, Google Ads Traffic Over Time, Revenue Over Time), all served by CustomReports.getCustomReport. Because they are configured per Matomo instance, the exact list varies by account.

Time & date grouping

Adriel groups Matomo’s results into these standard time views for reporting alongside other connectors.
Partial-period rows: when the “from” and “to” filters do not align with the start and end of a period (week, month, quarter, or year), the entire period is still displayed. The “from” and “to” filters continue to apply to the Total row.

Other Adriel breakdowns

These breakdowns are added by Adriel and are available across analytics connectors.

Limitations

Based on the current connector, Matomo has:
  • One site per data source — a connection scopes to a single idsite. Reporting on multiple sites requires additional data sources.
  • Live queries with no cache — every widget render issues a fresh call to the Matomo Reporting API, so performance on long date ranges depends on the Matomo instance’s archive configuration.
  • A 93-day cap on the Daily breakdown and a 1-year cap on the Weekly breakdown — data outside these ranges may be truncated.
  • No deleted elements — the connector does not surface data for deleted items.
  • User ID dependency — the Users metric (nb_users) is zero unless the site tracks visitors with User IDs.
  • Ecommerce tracking dependency — several ecommerce metrics appear only when Matomo product/category page tracking is configured; abandoned-cart metrics require the abandonedCarts request flag.
  • Cross-connector blending — Matomo report data may require blend settings before it can be combined with other data sources in the same widget.

API references

See also