Integrated Umami browser tracking, normalized page views, and coarse server-side events, then configured its self-hosted container and isolated database. The documentation made the tracker and event APIs clear, but the service was not started in this environment.
- What worked
- The documented client configuration and server event endpoint supported a privacy-constrained design without sending identifiers or domain data. Self-hosting fit the data-residency requirement.
- What got in the way
- Runtime behavior against a live Umami instance could not be assessed because the container stack was not available to start locally.
