Connect Matomo

Connect Matomo once at the org level, cloud or self-hosted. Same connect-once shape as Plausible: your URL, your token, every site inherits.

Matomo connects once at the org level. Drop in your URL and an auth token, and every site you add inherits the connection. Cloud or self-hosted: same shape.

If you’ve already connected Plausible, this’ll feel familiar. It’s the same pattern.

Before you start

You’ll need two things:

  • Your Matomo URL (e.g. https://analytics.youragency.com for self-hosted, or https://yourname.matomo.cloud for cloud)
  • An auth token with read access to the sites you want to report on

To grab a token in Matomo, go to your user menu, then Personal → Security → Auth tokens → Create new token. Give it a name you’ll recognise later (“SendTidings” works), and set it to read-only.

Connect at the org level

In SendTidings, open the Organisation page, go to Integrations, and find the Matomo section, then Connect.

Paste in:

  • URL: the root of your Matomo instance, no trailing slash
  • Token: the auth token you generated

Hit Connect. We’ll verify the token against your Matomo instance and pull the list of available sites.

That’s it. You don’t connect Matomo per site. Once it’s on the org, every site you add can pick from the Matomo sites already exposed by that token.

Pick the matching site

When you add or edit a site in SendTidings, you’ll see Matomo in the analytics dropdown. Pick the corresponding Matomo site from the list; we match on the idSite value.

If you set Matomo as the site’s report source (Use for reports, in the site’s Analytics section), that’s where the report’s numbers come from. You can have GA4 or Plausible also connected — only the chosen one feeds the report.

Self-hosted notes

Self-hosted Matomo works the same way. The URL is whatever you’ve put your instance on. If you’ve got multiple instances (e.g. one per client cluster), connect each one as a separate integration — the picker handles it.

A few things worth checking on self-hosted:

  • The instance is reachable from the public internet (we call the Reporting API on a schedule)
  • The token user has view access to the sites you care about
  • CORS isn’t relevant here — we call server-to-server, not from a browser

When the numbers look off

If a report shows 0 visitors but you know there’s traffic, it’s almost always one of:

  • Wrong site picked in the dropdown (easy to do if you’ve got similarly-named sites)
  • Matomo isn’t the primary provider: switch it in the site’s analytics settings, one click
  • The token doesn’t have view access to that specific site

See also: Connect Plausible · Primary provider explained