Skip to content

Umami

Umami shows traffic sources and what visitors do, from viewing a page to completing an action your app records.

Visit Umami

What do you need to start measuring a site in Umami?

Add a website in Umami and install the tracking script for that website. Umami Cloud runs the service. A self-hosted setup uses your own server and PostgreSQL database, so you manage updates and backups.

Start with one question. If you want to know whether visitors get through a signup page, decide whether the useful result is opening the form or successfully creating an account. Record a separate event for the success, then use a funnel to compare it with the earlier step.

How can you check that a success event reaches the right website?

Use a disposable copy of the site and a separate Umami website record. Check one test action before turning the tracker on for visitors.

  1. Check where the event goes before visiting the test site
    Compare the actual tracker destination and website ID with the disposable Umami record. Check any server tracker or tag manager separately. Confirm that app data and connected services are disposable, and that the recorder script and replay are off. If your Cloud plan only has one website slot and it is already used for live traffic, use a separate isolated instance or sketch the expected events on paper.
  2. Compare an attempt with a success
    Use a fictional signup in the test app. Check that opening the form and submitting a rejected entry create no signup success. Then complete one valid fictional signup and look for one success in the test website’s Events view.
  3. Check what the event contains
    Look at the event details and confirm they contain only the labels you intended to collect. A successful check proves what the test app sent. It leaves real visitor behavior unmeasured.

What can link two visits in Umami?

Umami’s standard session grouping uses a generated identifier without cookies. It uses signals such as the visitor’s IP address and browser. People on the same network with the same browser can be hard to distinguish.

A Distinct ID you supply can link sessions to one account. Keep it out if you only need aggregate traffic, and avoid sending an email address as the ID. The replay recorder is separate from regular tracking and captures more detail. Cloud lists replay and heatmaps on Business and Enterprise. Check which pages and fields will be recorded using fictional data before enabling replay for visitors.

What uses the Cloud allowance, and can you save the records?

Cloud Hobby lists 100,000 events per month for one website. A page view or custom action can count once, and stored event properties and session data also count toward usage. A visitor may therefore use several units.

Cloud exports a website’s collected analytics, including page views, events and sessions, as compressed CSV files. Check the plan’s retention window and keep the definitions that explain what the event names mean. For a self-hosted setup, back up the database you maintain.