-
Notifications
You must be signed in to change notification settings - Fork 52
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
New visit created for each action with userid populated since 3.13 #28
Comments
Hi @tolomaus Thanks for the suggestion. Maybe you are able to open a Pull request on this project? This would be very helpful and help solve this issue quickly. |
Hello Matthieu, No problem, but could you explain what should be the logic for populating the visitor id? What I described was just a workaround to avoid the spikes in "new visitors". |
I confirm this problem! This bug appear for user which disable cookies, then matomo for same uid (d2f22ac701961993) generate different cid (8cbf24c93d0f4628 | c3f6fec89ef58cb4) for each visit. Multiple unique visit for each action for same User ID |
Hi Matthieu, Thanks for the follow up. I can confirm that since I upgraded last Friday (17/01) the issue is solved. Many thanks! |
Since upgrading to 3.13 all of the sessions where a user id was set get a new visit created for each action.
I'm using the piwik_java_tracker and looking at the code it puts a new random string the the visitor id of each request. This has worked fine in the past, both when a user id was set and when one was not set.
As a workaround: explicitly setting the visitor id to a hex value derived from the user id whenever a userid is set seems to do the trick.
But ideally it should just follow the same logic as the scenario without a user id. There as well, a unique visitor id is created for each request by the piwik_java_tracker but at least the server side is able to group all actions into one session.
See also matomo-org/matomo#15299
The text was updated successfully, but these errors were encountered: