Replace Plausible analytics with Umami#95
Merged
Conversation
Switch from Plausible to self-hosted Umami analytics. https://claude.ai/code/session_01XmivDu6jtVzWBiL8pLnYgi
Dokploy Preview Deployment
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR replaces the Plausible analytics service with Umami for website analytics tracking. The change simplifies the analytics setup by removing the dual-script Plausible configuration and replacing it with a single Umami script tag.
Changes:
script.hash.outbound-links.jsand inline initialization)1ad3dc22-6b89-43d2-b38b-95bb1ffbc95dhttps://umami.damien-schneider.pro/script.jsType of Change
Checklist
Additional Context
This migration from Plausible to Umami provides an alternative analytics solution. The Umami script is configured to automatically track page views and events on the production environment.