Bring Matomo directly into Microsoft Teams, where decisions actually happen. Zero cost. Zero friction. Real insight.
The Matomo plugin for Microsoft Teams delivers key analytics directly into daily workflows to surface real user behaviour, conversion trends, and anomalies where decisions already happen.
Integrating with collaboration tools like Microsoft Teams reduces reporting delays, fragmented communication, and keeps insights anchored in the conversations that drive action. Faster visibility, shared understanding across teams, and zero budget risk make installation a rational choice, not an experiment.
-
Create and Schedule Report
-
List Schedule Reports
-
Why are my Microsoft Teams messages not delivered on an install that uses an outgoing proxy?
Matomo sends the webhook request over its SSRF safe fetch path, which resolves the webhook host itself
and connects to the address it validated. That path needs the curl PHP extension and cannot go through
a proxy, so on an install that only reaches the internet through a proxy configured in the [proxy]
section of config/config.ini.php every Teams message is refused. Such a refusal is written to the
Matomo log as MicrosoftTeams webhook request to <host> was refused. Sending Teams messages through a
proxy is not supported at the moment.
Why is my webhook URL rejected as invalid?
The webhook host has to be a name that resolves to a public address, because the plugin must not be
able to make Matomo call itself or another host on your network. An IP address, an encoded address such
as 127.1 or 0x7f000001, localhost and the host Matomo itself is reached on are all rejected while
the report or alert is being saved.
Can I use a Teams webhook that is served on a private address?
Yes, if you allow that address explicitly. Add it, or the range it is in, to
allowed_private_egress_ranges in the [General] section of config/config.ini.php. The webhook still
has to be a named host, so an address written directly in the webhook URL stays rejected.
