-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I can't get analytics to work #1560
Comments
Try using the same URL as your |
I'm not sure what you mean, sorry :( but thanks for answering. So, here's my Quartz setup:
and this is what I have in Umami: I can't put that full URL in Umami tho, no forward slashes nor https in that textbox |
Your URL isn't |
I can put it into the Quartz config, but I can put it that way on Umami.. do I need a custom domain? |
Hold on, based on the docs, shouldn't your Umami URL point to your Umami hosting? Not your Quartz site. |
by "Umami URL" you mean the URL in the Quartz config? if I'm just using Umami from their free tier, what would my hosting be? I'm not self-hosting |
|
That is not the correct Assuming you have no custom domain and are using GitHub Pages, it should be See: |
Hi, I believe that when you finished setting umami, umami would give a html tag like this: <script defer src="https://cloud.umami.is/script.js" data-website-id="xxxxx"></script> You could get this in the Then, you should set the analytics: {
provider: "umami",
websiteId: "xxxxxx",
host: "https://cloud.umami.is/script.js"
}, The Hope this helps. |
I will close given that it seems like a user setup problem. |
I am trying to add Umami analytics to my Quartz setup, but it's not hooking up correctly. I tried to put my IDs and URLs in different formats, with <>, without, with http, https, without... Umami is not picking it up.
I'm not tech savvy enough to properly fill-in this bug report, but I have a feeling it might be because Umami doesn't support github pages URLs like https://unapologeticaf.github.io/digital-garden/?
If so of course this is not a bug report 😅
The text was updated successfully, but these errors were encountered: