Umami

Notra loads the Umami tracker on every live page and allows its script and collection origins in the CSP, and the only value it needs is your public Website ID, not an API key.

Copy your Website ID

In Umami, edit the website you want to track, open Tracking code and copy the UUID from data-website-id. See Umami’s tracking setup.

Add it to Notra

Open Studio → Sites, select your site, open Integrations and click Add Umami. Paste the UUID into Website ID and leave the URL fields empty for Umami Cloud. To configure it in your repository instead, add it to blog.json:

blog.json

{
  "$schema": "https://usenotra.com/schemas/blog.json",
  "name": "Acme",
  "integrations": {
    "umami": {
      "websiteId": "94db1cb1-74f4-4a40-ad6c-962362670409"
    }
  }
}

Publish and verify

After you publish the change and the production deployment finishes, visit your live site and check that the visit appears in the matching Umami website dashboard.

With no URLs set, Notra loads https://cloud.umami.is/script.js and allows the collection endpoint at https://gateway.umami.is.

Self-hosted Umami

Copy the full HTTPS script URL from your tracking code into Script URL or set scriptUrl, which can include a custom path and HTTPS port.

blog.json

{
  "$schema": "https://usenotra.com/schemas/blog.json",
  "name": "Acme",
  "integrations": {
    "umami": {
      "websiteId": "94db1cb1-74f4-4a40-ad6c-962362670409",
      "scriptUrl": "https://stats.acme.com/script.js"
    }
  }
}

Self-hosted scripts send events to their own origin by default. If your tracking code uses data-host-url, for example because a reverse proxy sends events to a different endpoint, enter its HTTPS base URL in Collection URL or set hostUrl. See Umami’s tracker configuration.

Last modified on October 9, 2026

Get started

Domains

Write content

Components

Customize

Integrations

Publish

Reference

Self-hosted Umami

​Self-hosted Umami

Self-hosted Umami