docs: add example of src overwriting for US umami.is tracking #822
+3
−0
Conversation
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
|
Someone is attempting to deploy a commit to a Personal Account owned by @timlrx on Vercel. @timlrx first needs to authorize it. |
|
Really love your change was also thinking of pushing this. I had to contact Umami cloud support before they confirmed I was sending data to EU.. Perhaps we can also send feedback to Umami to highlight this either as FAQ or in docs. |
|
I was also running into this missing data problem and sent a support request to Umami. It was so strange since all requests to send data to Umami were successful. Umami support got back to me and confirmed my data was being sent to the EU region. |
Owner
|
Sorry for the late reply but thanks for the additional note. It seems like many people found it useful as well :) |
Meez25
pushed a commit
to Meez25/Blog
that referenced
this pull request
Jun 17, 2024
…ructions docs: add example of src overwriting for US umami.is tracking
bhiwagade-rahul
pushed a commit
to bhiwagade-rahul/tailwind-nextjs-starter-blog
that referenced
this pull request
Sep 22, 2025
…ructions docs: add example of src overwriting for US umami.is tracking
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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.
Context
Choosing to store Umami tracking data in the US (instead of the EU, which may have been the historic default) actually requires loading a different script and setting a different CSP header (since the data instead goes to
us.umami.isinstead ofanalytics.umami.is).I wasn't able to tell this without a little poking around and pestering folks on Discord / reading of https://github.com/timlrx/pliny to realize there was an option to do so.
Discord thread: https://discord.com/channels/951898446804172840/1195052582645801010/1195055451285504040
I'm happy to tweak the language or make other updates, but this at least would give someone a thread to pull on. I spent a fair amount of time trying to figure out what could be going wrong since Umami handles the (misdirected) tracking requests fine (responds with 200 for the
sendcall), but then no data ends up populating in the dashboard.