How to Set Up Umami (Step by Step)

Handle the unglamorous checks before you touch the Umami installer, because skipping them is what turns a five-minute setup into a support ticket: verify it actually supports the platform you run, and line up the account it will ask for, which for a free listing means an account rather than a card. Given its lean toward analytics and privacy, also confirm the neighbouring tools it needs to talk to are already in place, so nothing stalls the first run.

Most people race through installing a analytics product and only slow down once something is already wrong, so treat the install itself as worth five careful minutes: start from Umami's own site rather than a search result or a mirror, since that is the only place the current build and correct defaults are guaranteed to live. Open source alternative to Google Analytics. Self-hostable. No cookies, no tracking scripts that follow users. Clean dashboard. Focus on page views and referrers without the surveillance. Built by Mike Cao and open-sourced from its first version, per its own documentation it is MIT-licensed and avoids cookies and personal-data collection to stay GDPR and CCPA compliant out of the box, self-hosted on a small Node.js and PostgreSQL server or run through Umami Cloud. Read each prompt as it appears rather than clicking through, permissions requested, workspace access, any account it wants to connect, because these are far easier to grant deliberately during setup than to walk back afterward.

The settings worth opening first in Umami are the ones that are awkward to change later: where your data lives, who else can see it, and what it connects to. Its excellent privacy classification on Noizz is a starting signal, not a substitute for reading the actual toggles, set them to what you need rather than accepting defaults. Given its analytics emphasis, spend the extra minutes on that area of the settings, since that is where you will live day to day.

Resist configuring everything at once. Pick the single job you got Umami for and take it end to end, one real task, start to finish, because that tells you more in ten minutes than a week of reading feature lists. Its analytics and privacy focus is the obvious place to start, and if the product is going to disappoint you it usually shows on that first real pass.

When Umami misbehaves early on, the cause is rarely a defect in the product itself: far more often it is a permission you never granted, a plan tier that does not include the feature you are trying to use, or a connected tool whose authorisation quietly expired. Work through those three possibilities in order before you conclude anything is actually broken, since each one is fixable in minutes and none of them requires contacting support. Only once you have ruled all three out does it make sense to go looking elsewhere, and at that point the product's own status page, its documentation, and its issue tracker will get you an answer faster than a general web search, because they are specific to Umami rather than to the analytics category at large. There is active community discussion of Umami on Noizz worth reading alongside this analysis.