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
JS Tracker: enable alwaysUseSendBeacon by default #13681
Comments
Keep in mind that a large portion of users have sendbeacon disabled for privacy reasons. Disabling in Firefox via the So we should do a lot of testing to avoid the fallback not working (e.g. if |
One thing to keep in mind is that the callback parameter won't work anymore (because there is no event or what so ever when the request is finished). Some users rely on this see eg #13679 (comment) |
Actually, callbacks won't be a problem cause we call the callback if the browser confirms it sent the request. |
|
They are sent as request parameters unless the request is large AFAIK |
Also we just found out that when closing the tab/window, Chrome seems to not execute sendBeacon on beforeunload unfortunately!? so we wouldn't want to rely on this feature probably... |
@mattab it's still good for sending requests when the browser closes. It will be more reliable than the XHR. It just means we can't collect all requests, optimize them, and send them at the end of the page view. Like instead of pinging Matomo every 15s using heartbeat it would have better to send only one request when the browser closes... but this won't work reliably |
fixed with #15405, will be included in Matomo 4 |
BTW a benefit is that it will improve page load time when using send beacon. |
assuming that the trial went well, then in Matomo 4.0.0 we would like to enable the feature
alwaysUseSendBeacon
by default.see #13451 #6641
The text was updated successfully, but these errors were encountered: