-
Notifications
You must be signed in to change notification settings - Fork 7
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
[BUG] Check client hints for headless browsers #108
Comments
Hi @peterbo . Thank you for taking the time to create this issue. I was unable to reproduce the problem. I tested with Matomo 5.0.2, TrackingSpamPrevention version 5.0.0, and Headlesss Chrome 121.1. When TrackingSpamPrevention was enabled, requests weren't tracked from the headless browser and they were when the plugin was disabled. Could you please provide more background information, like your Matomo/plugin version? |
Hi @snake14 - we're seeing a lot of those in different instances. The problem seems to be, that bots use a "normal" chrome as a user agent, but identify as a headless chrome in the client hints:
The client hints seem to be reported in the end. Therefore, TrackingSpamPrevention should also check client hints, if the browser identifies as headless, i.e. https://github.com/matomo-org/matomo/blob/de2d14a6dda52c3445cfdcce50dcadaa1e87d7da/plugins/DevicesDetection/Columns/BrowserEngine.php#L40 |
Thank you @peterbo . That's very helpful. I'll mark this issue for our Product team to review and prioritise. |
Joined from the matomo forum ... The User Agent has nothing information to detect the browser as an Headless Browser: Matomo used a Device Detector: https://github.com/matomo-org/device-detector/ More Infos about The possible Solution is, that the TrackingSpamPrevention Plugin used this information. But i have no idea how comes the |
Another user reported this today
|
A user reported many headless browsers are still undetected:
|
Option "block headless browsers" is active in TrackingSpamPrevention, but headless browsers are tracked nevertheless:
The text was updated successfully, but these errors were encountered: