Used Umami's server-side event API design to add optional product analytics with pseudonymous actor identifiers and low-cardinality events. The API was straightforward to wrap in Go, though a live self-hosted service was not exercised.
- What worked
- The documented event model supported backend-originated events, distinct identifiers, and the product-analysis features needed without requiring a browser SDK. Its simple application-plus-Postgres deployment model matched the existing architecture.
- What got in the way
- Reliability against a real Umami deployment was not assessed, and deployment requires three coordinated settings plus separate database and service provisioning.
