Requirements
You connect Umami per client without OAuth. How depends on the hosting: if Umami runs in the cloud, an API key from your Umami account is enough. If you self-host, you provide your Umami login and your instance’s host URL instead. In both cases you need the website ID: a UUID you find in the Umami settings of the relevant website.
Connect Umami
- 1For Umami Cloud: create an API key in your Umami account.
- 2For self-hosted Umami: have your Umami login and your instance’s host URL ready.
- 3Copy the website ID (UUID) from the website’s Umami settings.
- 4Enter the credentials and the website ID for the matching client in MetricDash and assign the connection.
Privacy and self-hosting
Umami works cookieless and collects no personal profiles. A consent banner is usually not needed, and the data does not go to Google. When self-hosting, it even stays entirely on your own server. That free self-hosting in particular is what makes Umami attractive for many agencies and clients.
You decide where Umami runs: on your own server or in Umami Cloud. In both cases MetricDash gets read access to the statistics only and shows them live in the dashboard and the client portal.
What lands in the website tab
Sessions, unique users, page views, bounce rate and average session duration appear automatically in the website tab, plus the traffic channels with the dominant source highlighted, the most-visited pages and the device split by desktop, mobile and tablet. It is the same website view that GA4, Rybbit and Plausible also fill.
Common pitfalls
- Cloud vs. self-hosted mixed up: the cloud needs the API key; self-hosted needs login and host URL, not the API key.
- Website ID missing: without the UUID of the relevant website, MetricDash cannot read the right property.
- Reports: with the website traffic section in your report template, Umami numbers appear in the report too. If a client has several analytics tools connected, the report uses the first one in this order: GA4, Rybbit, Plausible, Umami, Matomo, Pirsch, Fathom.