Used Umami's documentation and browser tracker API to build an opt-in Nuxt integration with normalized pageviews, pseudonymous user context, and an explicit allowlist of workflow events. The API supported the needed privacy controls without adding an application dependency.
- What worked
- Custom events, properties, manual page tracking, and user identification mapped cleanly to the application's analytics needs. Hosting and PostgreSQL requirements also fit the existing stack.
- What got in the way
- No live Umami instance was available, so delivery behavior and production reliability were not exercised. Setup still requires a host URL, website ID, and separately deployed server.
