melbao
January 30, 2023, 10:39pm
2
Hallo 8ung,
das 0 Sekunden Problem ist ein altes und mir bekannt. Bei mir war/ist es das Direkt View + 1 Page + 0 Sekunden. Das habe ich in den letzten Monaten in Angriff genommen. Dokumentiert habe ich es hier (am Ende eine mögliche Lösung):
Hallo, ich nehme in meinem Matomo Tracking seit einiger Zeit sowas wie ein Tracking-Rauschen wahr. Soll heißen, es wird getrackt, aber das scheinen keine natürlichen Personen zu sein. Jetzt ist zwar bekannt, dass nicht alle Bots gefiltert werden können, weil einiger diese sich wie natürlichen Person zu erkennen geben und verhalten, aber es gibt da auch sehr eigenartige Vorfälle.
Eigentlich könnte ich zig Themen öffnen, um jede einzelne Beobachtung zu diskutieren. Ich will hier nur eines zum The…
Ich habe jedoch weiterhin Direkt View + 1 Page + 0 Sekunden, auch wenn die scheinbar weniger geworden sind. Dagegen ist wohl nichts mehr zu machen. Das liegt wohl an den Devices oder irgendwelchen Browser Plugins, die verwendet werden.
Im Prinzip - soweit ich mich erinnere - fängt matomo erst ab 30 Sekunden an zu zählen. Alles unter 30 Sekunden = 0 Sekunden.
Es gibt aber noch ein anderes 0 Sekunden Problem, das hier beschrieben ist:
opened 08:57PM - 13 Jan 23 UTC
closed 09:57PM - 09 Oct 23 UTC
duplicate
Matomo Version: 4.13.0
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.0
I have seen a mistake by the "Time on page" popup in the real-time page by the last visit page, when the time on page is under 30 seconds (i think). I have a own 1 seconds heartbeat (ping) for the first 10 seconds and a matomo heartbeat with 10 seconds. The matomo script starts after a timeout of 1 second (prevent tracking of 0 seconds viewer).
Here by a visitor, there leave the page after visit 10 pages.
Time in first page popup: 21:10:52
Time in last page popup: 21:12:06
= 1:16
Last time: 21:12:06
Time on page: (1min 16s)
In the popup by the last page: 0s
Here by a visitor, there leave the page after visit it. The Time on page is 10 seconds, but in the popup 0 seconds.
By another viewer with more than 30 seconds time on page in the last page is the "Time on page" greater than 30 seconds. I think for the calculation of the time on page in the popup there is a 30 seconds barrier?
**Edit**: A better example.
2 actions
Time on page: (1 min 16 sec)
Time in first page popup (below): 21:30:48
Time in last page popup (above): 21:32:00
= 1:12
The viewer was also 4 seconds on the last page.
By another 1 action viewer with time on page 13 seconds, there was 13 seconds in the popup. It is also not on all time a mistake/bug or a calc time barrier. Its difficult.
**Edit 2**:
Its possible not a 30 seconds barrier, rather 10 seconds, but it seems its not barrier, rather the firered pings in the first 10 seconds with a setInterval are ignored in the popup time on page calc and only the matomo heartbeat (10 seconds) are in use of the time calculation in this case. But also this is not really the cause. Its difficult.
Der heartbeat wurde in seiner Funktion vor wenigen Jahren geändert. In der matomo Dokumentation wurde das aber nicht wirklich vermittelt. Er sendet keine Pings mehr in einem Intervall, sondern checkt ob die Page im “Fokus” ist oder verlassen wird.
opened 04:14PM - 17 Jan 23 UTC
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.