You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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.
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: