FeaturesAnalytics
PreviousNext

Umami

Configure Umami analytics provider.

What It Does

Enables Umami tracking through the @kit/umami provider.

When To Use

  • You selected umami in createAnalyticsManager([...]).

Prerequisites

  • Running Umami instance (self-hosted or cloud).
  • Website ID from Umami dashboard.

How To Use

Set client env vars:

NEXT_PUBLIC_UMAMI_HOST=https://your-umami-instance.com
NEXT_PUBLIC_UMAMI_WEBSITE_ID=12345678-1234-1234-1234-123456789abc
NEXT_PUBLIC_UMAMI_DISABLE_LOCALHOST_TRACKING=true

These variables are validated in kit/analytics/umami/envs.ts.

MCP Context

capability: umami_provider
entrypoints:
  - kit/analytics/umami/envs.ts
inputs:
  - NEXT_PUBLIC_UMAMI_HOST
  - NEXT_PUBLIC_UMAMI_WEBSITE_ID
outputs:
  - umami_tracking_enabled
constraints:
  - website id must match configured Umami site
side_effects:
  - client analytics traffic sent to Umami

Agent Recipe

  1. Add Umami env vars.
  2. Ensure provider list includes umami.
  3. Confirm requests appear in Umami dashboard.

Troubleshooting

  • If no hits appear, verify host URL and website ID pair.
  • If localhost should be tracked, set disable flag to false.

How is this guide?

Last updated on 3/23/2026