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
I am currently working on a Single Page Application (SPA) and facing an issue with tracking query strings during page navigation. My goal is to accurately track page views, including the full URL with query strings, whenever the user navigates from one page to another.
I have implemented the following code in my _app file to integrate Matomo tracking:
This setup successfully tracks the full URL, including query strings, as intended. However, I have encountered an issue where each page view is being tracked twice.
I am reaching out to see what adjustments in my setup I need to do to ensure that page views are only tracked once per navigation event.
Thank you.
The text was updated successfully, but these errors were encountered:
Reading the source, looks like it's not possible at the moment to disable the builtin trackPageView if you do it yourself.
We could add a trackQuerystring (default to false) option to the init method that adds the querystring to the builtin setCustomUrl so you wont even have to override onRouteChangeComplete.
What do you think ? Would you like to land a PR for this ?
Hello,
I am currently working on a Single Page Application (SPA) and facing an issue with tracking query strings during page navigation. My goal is to accurately track page views, including the full URL with query strings, whenever the user navigates from one page to another.
I have implemented the following code in my _app file to integrate Matomo tracking:
I've added this in my
_app
:This setup successfully tracks the full URL, including query strings, as intended. However, I have encountered an issue where each page view is being tracked twice.
I am reaching out to see what adjustments in my setup I need to do to ensure that page views are only tracked once per navigation event.
Thank you.
The text was updated successfully, but these errors were encountered: