@milexjaro opened this issue on February 24th 2016

I have an issue regarding to the title, when a visitor visited a page at 24th Feb 2016 and the last visit was at 18th Feb 2016, why is the visitors->engagement tab not showing the 'days since last visit' table correctly? It's supposed to have a number in '6 days' row, right?

@tsteur commented on February 24th 2016

Thx for creating the issue, this looks like a bug indeed! Maybe it's related to date ranges. Can you see "6 days" when selecting the "Day Feb 24th"?

@milexjaro commented on February 25th 2016

Thanks for replying, and here are the screenshots, and I still can't see "6 days" when selected the "Day Feb 24th"

@tsteur commented on February 25th 2016

Sorry but one more question: Have you seen this problem also for other visitors? It's possible that maybe just the database had once a connection problem or so and one update was not written on a tracking request. Maybe it works for other visitors?

@mattab commented on March 31st 2016

it is possible that the user could connect to your website from several devices. As you are using User ID feature, the visitor is correctly recognised, but the "Visits by days since last visit" relies on First Party Cookies (FAQ) so if your user has used different devices or browsers, it could explain that "Days since last visit" is not correctly set.

@tsteur commented on April 3rd 2016

@mattab I reckon the reason visits since last days is not calculated server side is re archiving performance?

@mattab commented on April 4th 2016

Yes, it would be slow because we don't have the data available in easy to query format. Unless we would select the past historical visits which would be too costly. In the future this could be improved when we store users in a user table (eg log_user, which will be needed for several important features such as Life Time Revenue LTV https://github.com/piwik/piwik/issues/2750 or multi channel attribution modelling #6064

@milexjaro commented on April 7th 2016

Hi, sorry for the late reply, and I found this issue is experienced by other visitors

@mattab commented on August 23rd 2016

We haven't been able to reproduce unfortunately. Maybe someone else has experienced this issue?

Powered by GitHub Issue Mirror