Umami
Privacy-friendly web analytics for marketing sites
Review status: Evaluated. Read the evidence and pilot limits below before choosing.
Official Website · Source Code
oss-osi-approved full guide featuredOverview
Umami is a simple, privacy-focused analytics platform. Marketing teams measure site traffic for tour landing pages without heavy third-party trackers.
At a glance
| Field | Value |
|---|---|
| Categories | analytics-bi |
| Deployment | self-hosted, managed-saas |
| License class | oss-osi-approved (MIT) |
| Cost model | freemium |
| Implementation difficulty | easy |
| Maintenance burden | medium |
| Maturity | stable |
| Freshness status | partially-verified (2026-07-17) |
| Completeness | editorially-reviewed |
| Confidence | medium |
| Directory tier | evaluated |
Cost reality
Self-host free; Umami Cloud has paid plans—check official pricing.
Pricing and free-tier limits change frequently; re-check official pricing before budget decisions.
Tasks reduced or augmented
Software does not replace community or ops staff. It may reduce or augment:
- Measuring landing-page conversion funnels
- Reducing reliance on invasive analytics
Human oversight still needed
- Cookie/consent policy alignment
- Access to analytics dashboards
Manual process this can replace
analyze-campaign-performance
- Relationship: reporting layer
- Automation level: assisted
- Manual process this can replace: Manually copying basic website pageview and event counts into an ad hoc campaign report.
- Tasks it can reduce: Collects and presents website traffic and configured event evidence for campaign review.
- Role it assists: marketing-manager
- What still requires a person: Validate tracking and consent, reconcile web evidence with spend and qualified outcomes, explain attribution limits, and approve any campaign change.
- What happens if it fails: Missing, duplicated, or misconfigured events can produce a confident but false campaign conclusion.
- How to measure the pilot: Each pilot campaign review uses validated web metrics and records attribution and data-quality caveats before a decision.
- Confidence: medium
Data held
-
pageviews
-
events
-
device/browser metadata
-
Personal data: no / limited
-
Payment data: no / not primary
Risks
| Area | Notes |
|---|---|
| Vendor lock-in | Evaluate export formats and API completeness before deep customization. |
| Security | Apply updates promptly; restrict admin access; enable TLS. |
| Compliance | Operator remains responsible for privacy and local regulatory obligations. |
| Licensing | Confirm license fits commercial coworking use. |
| Operational | Plan backups, monitoring, and a restore drill before production use. |
Coworking fit
Roles: marketing, owner-operator, technical-operator
Workflows: marketing-campaigns, reporting-kpis
Problems: privacy-compliance, grow-pipeline, self-host-for-data-control
Smallest useful experiment
Deploy Umami, add tracking script to the marketing site staging slot, validate pageviews for tour CTAs.
Initial planning estimate (unverified): 1–3 days
Links
Implementation guide
See the human-written implementation guide.
Verification
- Status:
partially-verified - Completeness:
editorially-reviewed - Confidence:
medium - Tier:
evaluated - Last reviewed:
2026-07-17 - Sources:
Editorial evaluation based on the listed official product, repository, documentation, and pricing pages. Task fit has not been implementation-tested and does not establish end-to-end campaign attribution.