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
Time spent on page calculation is buggy #9198
Comments
uuh good find.- that's quite important! |
Seems like we are experiencing this too -> http://forum.piwik.org/t/update-to-2-15-changed-average-visit-duration-and-time-on-page/16744 |
I think the issue I mentioned here has been an issue for a long time and not only since the last update. From which Piwik version did you update? I presume the problem you are describing might be actually a different one |
@tsteur : from 2.14.3 to 2.15.0 |
Main Question is: which counting is correct? |
@SR-mkuhn this particular issue has been buggy for quite a while and not only since last update I think. |
@SR-mkuhn maybe create a new issue for your problem and describe it there |
I've also encountered this issue recently. And I've found that there is problem with Metric calculation: Time spent on site is defined as
The problem is that COUNT(*) counts all rows, even those containing NULL value. So average value isn't average at all. Solution would be use of |
I’ve just encountered the same issue. Checking at the Visitor Profile, I can see that if I look at interactions where we have a page with lots of tracking events occurring, the Page View event gets a minimal time whereas the events are given times between each interaction. As such the user could be interacting on a page for say a minute or more, triggering numerous events, but the page dwell time would be still close to zero. Surely this is a major bug. This means that any page which has subsequent events occurring will have a incorrect dwell time. |
Would agree this bug is quite major as it is causing the Time on page to be wrong, for any page tracking events. |
Possibly there is a strong relationship to: |
Has it been already solved? We had Piwik 2.something, now we are in upgrade process to matomo 3.7. and I am wondering if it will be correct. I have checked the previous data in database. Zou can easily see, when filter one specific idvisit in piwik_log_link_action_table and you will see, that every event will close the time on pageview. Especially if you are usinng some events like formSeen, bannerImpression etc. you will understand that it is not correct. And also time spent with some events is soo funny. Thank you also for pointing me to some another issue etc. |
As the issue is still open I don't think anything has been solved here yet AFAIK. @mattab that might be indeed quite important to fix the time on page. |
I also encountered this issue getting wrong time on page. |
I'm being hit by this problem, too - my "AVG. TIME ON PAGE" numbers are coming out as near-zero due to events on the page. How do we get this bug prioritised for fixing, please? In case it's helpful to anyone, in my local Matomo deployment I unashamedly hacked my ./plugins/Actions/Archiver.php file and commented-out the line which restricts by
Informally, this worked for my use case - I haven't given any thought about whether this is a robust solution. |
How can this issue still be open after 7 years? Just wondered why the big gap between GA3 (Universal) data and this one could be and found out that his has been discussed a few times. Is there any ohter workaround in the code for that to ignore the users that spent 0 time in the "avg time on page" row? |
time_spent_ref_action
divided by the number of visitsnb_visits
. Not all visits havetime_spent_ref_action
though. Insteadsum_time_spent
should be divided by something likenb_hits_with_time_spent
.time_spent_ref_action
wrong. It calculatesvisit_last_action_time - currentTimestamp
butvisit_last_action_time
is updated on any tracking call, meaning also on any hit.To make it a bit more clear let's say there are the following tracking calls
The time spent for first pageview is calculated by the time difference between the event and the pageview, not between the two pageviews. This means for many common scenarios where one triggers a pageview and then an event, search, content impression, ... the time spent information is not accurate.
The text was updated successfully, but these errors were encountered: