-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
Wrong URL reported with SvelteKit client-side navigation #2637
Comments
Same issue here, any luck solving it? |
Me too :( |
Same issue here using self hosted umami v2.11.0. Although, is showing only the path really the intended behavior? With two domains I could not differentiate between them anymore. |
The two domains should have different site IDs probably. |
Should be fixed by this PR, #2679. We will release a hotfix. |
Fixed in v2.11.2. |
@mikecao, upgrading to >2.11.2 fixed the issue, but I have a significant amount of data captured before the fix was released which is a little troublesome when generating reports. For example, when generating a report for the last 12 months I still see split metrics for the https://.../blog and /blog variants from before I upgraded. Is there a way to merge these datasets retroactively? |
@acerasoni You would have to run a script to update your data. |
@mikecao What script should be run? |
@madmax You would have to come up with it. You can probably do it in pure SQL |
Describe the Bug
The full URL is reported when navigating using SvelteKit client-side navigation (clicking a link on the hydrated page).
The correct URL is reported when reloading page, even if the tracker script is inserted during hydration (SSR page does not include it).
E.g. the analytics page shows
https://example.com/contact/
instead of/contact/
for pages that are navigated client-side.This causes incorrect statistics, as one page can have 2 URLs (relative with direct navigation and absolute with client-side navigation) which have separate view counting.
Database
Umami Cloud
Relevant log output
No response
Which Umami version are you using? (if relevant)
Umami Cloud
Which browser are you using? (if relevant)
Firefox
How are you deploying your application? (if relevant)
Umami Cloud
The text was updated successfully, but these errors were encountered: