Improve UX around setting up Analytics on the status page #4613

New issue

Open

opened 2026-02-28 04:09:14 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-28 04:09:14 -05:00

Owner

Originally created by @RoyvanEmpel on GitHub (Jan 15, 2026).

This issue relates to the following pullrequest https://github.com/louislam/uptime-kuma/pull/5608 and comment https://github.com/louislam/uptime-kuma/pull/5608#issuecomment-3678867287.

🔖 Feature description

Currently with using for example Plausible as a analytics type the inputs are very non-intuitive.

For Plausible Cloud users, you need to enter your status page (sub)domain into the 'Analytics ID' field, and the default script.js (which is the same for every user) into the 'Analytics Script URL'.

For self-hosted Plausible users, the 'Analytics ID' stays the same as for cloud users (the current domain the status page is viewed from), but the 'Script URL' changes to their own self-hosted instance's script.js.

✔️ Solution

There are multiple solutions for this issue.

The first would be to give all analytics types their own input labels. For Plausible, there should be an extra 'self-hosted' switch for the user to enter their own script.
Also, the 'Analytics ID' field could really just be auto-filled with the 'Domain names' (or current domain). This would only differ if the user is using a reverse proxy, but even then, they should still just fill in the domain names section, right?

❓ Alternatives

An alternative that would require less work is to just change the placeholders to represent the right kind of value.
In 'Analytics ID', it could show status.example.com as the placeholder for Plausible. The script URL field could straight-up use https://plausible.io/js/script.js as the placeholder.

Another alternative would be to add a small alert / tooltip with a question mark icon next to the label name.

📝 Additional Context

The real problem is that there is pretty much zero documentation on Plausible's site on how to use the current Uptime Kuma implementation. I found the docs for Shopify by accident, which uses the same implementation as Uptime Kuma.

Originally created by @RoyvanEmpel on GitHub (Jan 15, 2026). ### 📑 I have found these related issues/pull requests This issue relates to the following pullrequest https://github.com/louislam/uptime-kuma/pull/5608 and comment https://github.com/louislam/uptime-kuma/pull/5608#issuecomment-3678867287. ### 🔖 Feature description Currently with using for example Plausible as a analytics type the inputs are very non-intuitive. For Plausible Cloud users, you need to enter your status page (sub)domain into the 'Analytics ID' field, and the default `script.js` (which is the same for every user) into the 'Analytics Script URL'. For self-hosted Plausible users, the 'Analytics ID' stays the same as for cloud users (the current domain the status page is viewed from), but the 'Script URL' changes to their own self-hosted instance's `script.js.` ### ✔️ Solution There are multiple solutions for this issue. The first would be to give all analytics types their own input labels. For Plausible, there should be an extra 'self-hosted' switch for the user to enter their own script. Also, the 'Analytics ID' field could really just be auto-filled with the 'Domain names' (or current domain). This would only differ if the user is using a reverse proxy, but even then, they should still just fill in the domain names section, right? ### ❓ Alternatives An alternative that would require less work is to just change the placeholders to represent the right kind of value. In 'Analytics ID', it could show status.example.com as the placeholder for Plausible. The script URL field could straight-up use https://plausible.io/js/script.js as the placeholder. Another alternative would be to add a small alert / tooltip with a question mark icon next to the label name. ### 📝 Additional Context The real problem is that there is pretty much zero documentation on Plausible's site on how to use the current Uptime Kuma implementation. I found the docs for Shopify by accident, which uses the same implementation as Uptime Kuma. <img width="431" height="396" alt="Image" src="https://github.com/user-attachments/assets/2165643b-29a8-4bf6-b3a3-50ba1fb07fbc" />

deekerman added the

feature-request

A:status-page

A:ui/ux

labels

2026-02-28 04:09:14 -05:00

deekerman commented

2026-02-28 04:09:19 -05:00

Author

Owner

@CommanderStorm commented on GitHub (Jan 15, 2026):

The first would be to give all analytics types their own input labels.
For Plausible, there should be an extra 'self-hosted' switch for the user to enter their own script.

So what would be the thing that goes in there if this is not filled in?
https://plausible.io/js/script.js?

Also, the 'Analytics ID' field could really just be auto-filled with the 'Domain names' (or current domain).
This would only differ if the user is using a reverse proxy, but even then, they should still just fill in the domain names section, right?

Any UX improvements are welcome.

A user always has 2 domains the status page is served under.
The main one and the direct alias (not sure how we name this in the status page).
Basically status.example.com instead of example.com/status/BLOB
With which of these should this field be auto-filled if empty for the plausible status page integration?

@CommanderStorm commented on GitHub (Jan 15, 2026): > The first would be to give all analytics types their own input labels. > For Plausible, there should be an extra 'self-hosted' switch for the user to enter their own script. So what would be the thing that goes in there if this is not filled in? `https://plausible.io/js/script.js`? > Also, the 'Analytics ID' field could really just be auto-filled with the 'Domain names' (or current domain). > This would only differ if the user is using a reverse proxy, but even then, they should still just fill in the domain names section, right? Any UX improvements are welcome. A user always has 2 domains the status page is served under. The main one and the direct alias (not sure how we name this in the status page). Basically `status.example.com` instead of `example.com/status/BLOB` With which of these should this field be auto-filled if empty for the plausible status page integration?

deekerman commented

2026-02-28 04:09:20 -05:00

Author

Owner

@RoyvanEmpel commented on GitHub (Jan 16, 2026):

which of these should this field be auto-filled if empty for the plausible status page integration?

Hmm, by 'autofill,' I actually meant whatever is entered into this specific field:

But another solution might be to default to the current domain the page is being viewed from if this field is left empty. Alternatively, it could just autofill the first domain from the list. However, if the page is served on multiple domains that you want to monitor in Plausible, then the tool would need to automatically detect and use the specific domain the page is currently being viewed from. Maybe it should only do that if the current domain that the page is viewed from is in the "Domain names" list?

@RoyvanEmpel commented on GitHub (Jan 16, 2026): > which of these should this field be auto-filled if empty for the plausible status page integration? Hmm, by 'autofill,' I actually meant whatever is entered into this specific field: <img width="449" height="192" alt="Image" src="https://github.com/user-attachments/assets/466fbaff-b78c-44ad-bf42-7b1669979d70" /> But another solution might be to default to the current domain the page is being viewed from if this field is left empty. Alternatively, it could just autofill the first domain from the list. However, if the page is served on multiple domains that you want to monitor in Plausible, then the tool would need to automatically detect and use the specific domain the page is currently being viewed from. Maybe it should only do that if the current domain that the page is viewed from is in the "Domain names" list?