I see you’ve identified an error in the way “session duration” and concurrently “time on page” is tracked.
I’m trying to communicate to my team members the possible implications of this error however large or small they may be. I can’t find any other information about this issues, which is why I’m writing here.
The error states an issue in the way time is measured precisely. Are we still able to rely on both dimensions for general time-measurement? Will there be a correction to our data for the error?
Due to the aforementioned issue, the heartbeat ping mechanism (labelled “Measure session duration precisely” in the Piwik PRO UI) did not work correctly during this period.
Depending on the site/application content and the visitor behaviour (e.g. leaving the page open without generating additional events), the time on page or session time dimension could be less accurate as the additional ping events were not collected.
Unfortunately, it’s not possible to make the data more accurate as the events that Piwik PRO uses to calculate these dimensions are missing.
I just checked our reports. The error message specificly states that data will be inaccurate between November 7th and December 7th.
In my report on average time on page, I am seeing a fairly large drop from November 7th. It doesn’t seem to recover after December 7th. Why does it not bounce back up again after December 7th?
