0 Sekunden Aufenthaltsdauer pro URL

melbao · March 11, 2023, 9:59am

Hallo Falk, schau dir mal die Tracking Codes ab diesem Beitrag abwärts an:

Mehr Infos zu _paq.push(['enableHeartBeatTimer', 5]); und dessen Umstellung im Jahr 2020 hier:

github.com/matomo-org/matomo

Clarify in docs that "enableHeartBeatTimer" JS feature does not actually simply send a "ping" every x seconds

opened 04:14PM - 17 Jan 23 UTC

matomoto

c: Documentation

Matomo Version: 4.13.1 Matomo Update History: 4.11.0,4.10.1,4.9.1,4.7.0,4.6.2,4….6.1 Matomo Install Version: Unknown - pre 3.8. Latest Available Version: 4.13.1 Hello, i have a question about the `enableHeartBeatTimer` in case of the setting of the seconds like `_paq.push(['enableHeartBeatTimer', 30]);`. I have used a `_paq.push(['enableHeartBeatTimer', 1]);` and have observed, that the Heart Beat Timer do not accept a value lower than 5, also 5 seconds is the minimum. It is also only possible to set the Heart Beat Timer max or higher than 5 seconds. This information is missing in the documentation. https://developer.matomo.org/api-reference/tracking-javascript https://developer.matomo.org/guides/tracking-javascript-guide The next matter is, that the information about the "sent" of data is not correct. Matomo sent only when the real view-time on page is greater than 4 seconds and the leaving of the page is detected by matomo. In other cases no data will be sent. The next matter is the information: > ... then a ping request will be sent "Ping" is a bit misleading in the context of specifying seconds. Not every x seconds a ping is sent, but only one by leaving the active view of the page. Concluding The name `enableHeartBeatTimer` is a little bit misleading, because it is not a interval (setInterval). It is more/near a `beforeunload` (but not really a `beforeunload`). It is a `leaveactiveview`. Somewhere the false information is circulating that the heart beat timer should not be set to too fast (less than 15 or 30 seconds), so that the requests are not too high. But - since only a maximum of 1 request is sent with the heart beat timer anyway - the question is: why it is not set to 1 second by default? Then there is finally an accurate measurement result.