@metalocator opened this Issue on April 13th 2018


We are tracking twice the visits in Matomo 3.4 v.s. 2.16.5.

We’re running both servers (3.4 v.s. 2.16.5) side-by-side and our expectation would be that they would track the same numbers in all cases.

We created the 3.4 server by duplicating our existing 2.16.5 server and running a manual upgrade. The config is the same, (minus the trusted/allowed hosts setting).

We’re funneling data from our customer Web sites to both servers by using the dual tracker method described here:

I looked at the apache log files and both servers show the same number of log entries for the same date range.

This picture of the visitor log shows it most concisely.


Notice their visit is cut arbitrarily into two visits.

That exact same user, tracking in our 2.16.5 instance is shown as a single visit.

2 16 5

The first screenshot shows more actions due to the Content impressions we track are shown as actions in 3.4, which is great.

The total visit count is roughly doubled

We are also tracking this same site in Google Analytics, and the visit count agrees with the 2.16.5 numbers.

We can't upgrade to 3.4 until we resolve this, so any feedback, or even a hint of where to look, would be sincerely appreciated. Beyond appreciation, we are also willing to pay for assistance.

@mattab commented on September 25th 2018 Member

Hi @metalocator
Could you please check with our latest 3.6.0-b2 beta if this issue may be fixed for you?
see http://piwik.org/faq/how-to-update/faq_159/

@fatica commented on September 25th 2018


We saw this bug while running multiple trackers in parallel in production in a testing preparation for a cut over from 2.16.5 to 3.4.

We found that running the QueuedTracking/Redis plugin solved the problem and have been using that ever since.

Unfortunately it would be very difficult to orchestrate a test since we don't maintain parallel environments like this. Additionally we only saw the issue for our sites under medium to heavy load and I'm not sure how to simulate that. Basically when many requests would hit the log "simultaneously" according to apache log granularity.

In theory. to reproduce the issue, set up 3 environments. 2.16.5, 3.4 and the new beta. Throw the exact same high load at them quickly and see if 3.4 shows fewer visits than 2.16.5 and the new beta.

Thanks for looking into it, and sorry I can't be of more help testing.

Powered by GitHub Issue Mirror