Analytics

[davenquinn]

Macrostrat's v2 codebase is not integrated with an analytics platform to generate insights on usage patterns etc. This is important for reporting and communication of adoption to funding agencies etc. We need to ensure that analytics are integrated into the API and web codebase.

For v1, we've used a combination of approaches:

• Google Analytics for the web and API codebase: this has worked well so far but the coverage is somewhat incomplete and there are privacy and cross-site tracking concerns with this approach.
• Tileserver requests are tracked by a hand-rolled, server-side system, which has worked well

Perhaps we should use a OSS/self-hosted tool like Umami for v2, to reduce platform reliance on Google Services in the future? The v1-to-v2 transition would be a good time to implement this.

[CannonLock]

@davenquinn I started down this path for CHTC as we don't want to use Google. Matomo came up as a solution and from reading it looks like the most direct competitor to Google Analytics.

Shall I spin up a instance in kubernetes and see what it looks like?