Thanks for the feedback @matomoto,

From my understanding of https://developer.matomo.org/guides/tracking-javascript-guide#accurately-measure-the-time-spent-on-each-page a heartbeat timer of 10 seconds, eg. _paq.push(['enableHeartBeatTimer', 30]); would mean that only visits of 10 seconds or more on the last page of the visit would record a non-zero "time on page" value.

Does this behaviour change for you with a lower heartbeat timer value?

Hello bx80,

i have a very custom matomo tracking code with own settings. For example, the matomo script is loaded first after 1 second timeout with a setTimeout. This prevents the tracking of 0 seconds views. It is to prevent littering my matomo database. The next is a own heartbeat with a setInterval for the first 11 seconds each second, also with a clearInterval.

var myheartbeat = setInterval(function() {
  _paq.push(['ping']);
}, 1000);
setTimeout(function() {
  clearInterval(myheartbeat);
}, 11000);

With this tracking code i see the time on page in the first 10 seconds (except the first second) more detailed as default. I see also 1 or 2 ... 9 ... 10 second/s time on page values.

Then i have a regular _paq.push(['enableHeartBeatTimer', 10]);.

With a

window.addEventListener('beforeunload', function(e) {
  _paq.push(['ping']);
});

i see also more detailed time on page after 10 seconds.

I have observed, that the "Time on page" in the popup is <11 = 0, like a:

var time_on_page = get_time_on_page();
if (time_on_page < 11) {
  time_on_page = 0;
}

Looking the screenshots, it seems just the last page duration is not taken into account.
In @matomoto first example, the last page time seems to be 2 seconds, but is displayed 0 (21:12:06 - 21:10:52 = 00:01:14) because total visit duration is 00:01:16
In the second example, 21:32:00 - 21:30:48 = 00:01:12. Then the last page duration is 4s. Maybe the page calculation is set only when another page comes after? But the visit duration is well calculated... 🤔

Looking the screenshots, it seems just the last page duration is not taken into account.
Maybe the page calculation is set only when another page comes after?

Not really.
The "Time on Page" in the black popup is "0 seconds", when the Time on page is <11 seconds.

Example: I have by visits with 0 actions and a regular "Time on Page" = 10 seconds a "Time on Page" in the black popup with "0 seconds". With regular 11 seconds, in the popup also 11 seconds. All lower than 11 seconds is 0 seconds in the black popup. That is the situation i observed.

The problem: I don't see, how much time on page is in the last page, when it is lower than 11 seconds. By 0 actions, is see the time on page in the regular box - here it is not a problem. By many pages in one visit i must self calculated the time on page for the last page, when it is lower than 11 seconds.

The problem: I don't see, how much time on page is in the last page, when it is lower than 11 seconds.

Maybe in this case this is the difference between Visit duration and time between last and first page...
In case of last page duration > 10 seconds, my operation (VD - (TLP - TFP)) true or false?

Hello heurteph-ei,
is this a question to me?

The Time on Page calculation in the last page is OK by greater than 10 seconds. My question is: is there a time barrier in the calculation that makes <10 = 0 ? Because that is the fact i observed.

@matomoto, yes the question was for you 😉
Then is seems the total visit duration is well calculated any time, but the last page duration is not set when < 10...
How are configured default_time_one_page_visit? (not sure it could impact your problem...)

global.ini.php

default_time_one_page_visit = 0

untoched. And i don't touch it, because it manipulates the real Time on page. Consider myheartbeat above.

This issue has been mentioned on Matomo forums. There might be relevant details there:

https://forum.matomo.org/t/0-sekunden-aufenthaltsdauer-pro-url/49486/2

After checking this one again, I think it's actually a duplicate of #9539
The time on page for the last page currently isn't set correctly even when using a heatbeat timer.