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 don't think this was fixed by any recent refactoring. If bulk tracking is actually used in this case then the tracker should not really be a problem I think. Maybe it is a bug in reading the visitor details. I think those actions are ordered by server_time and if they all have the same time, which is likely when using bulk tracking, then those entries might be ordered kinda randomly / differently depending on the version of the database etc.?
Edit: I can reproduce this via bulk tracking and they are recorded in the correct order but as expected reading the logs seems to be the problem (all having same server_time)
Edit 2: The sorting is done in PHP on top so there seems to be the problem
We try to use piwik as a backend for desktop application usage trecking.
We often try to track pageviews and events that are occurred in the same second, but where the order of them is relevant.
We import them via a bulk request and noticed that if we look at them e.g. in the Visitor Log they got disordered.
This is the request (action names go from 1 to 10):
This is the result in Visitor Log:
The text was updated successfully, but these errors were encountered: