-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add "bot" (flags) detection #46
Comments
That feature can be abstracted and combined with existing operating system feature. We wouldn't need to add feature over feature, but implement a single flexible feature. |
Blocks proper tests for this: TYPO3/testing-framework#256 |
Ensures pageview and recordview are tracked as expected. Relates: #46
Ensures pageview and recordview are tracked as expected. Relates: #46
Ensures pageview and recordview are tracked as expected. Relates: #46
Already worked on this, see commits and Branch feature/46-add-flags-feature (as well as first attempt in branch feature/bot-support which won't make it due to more flexible approach in new branch). Blocker right now: This will be breaking and data migration takes way to long right now. Further work (funding) needed to provide a smother migration. |
What do you think about requiring/suggesting https://github.com/JayBizzle/Crawler-Detect and making it available in the Expression Language as Absolutely wonderful project by the way :) Thank you! |
I've integrated https://packagist.org/packages/matomo/device-detector within the feature branch already. All requests will be tragged but can have arbitrary trags. E.g. a feature flag "isBot:yes" or flag "botName:Google". See: https://github.com/DanielSiepmann/tracking/blob/feature/46-add-flags-feature/Documentation/Changelog/2.0.0.rst#features and https://github.com/DanielSiepmann/tracking/blob/feature/46-add-flags-feature/Documentation/Tags.rst Widgets will be extended to allow filtering by tags. That way the extension is not limited to anything, e.g. bots, but open for anything. Developers can add further extractors to extract tags from request which will be attached as well. Integrators can then create fine grained widgets, e.g. top bots, top pages by bots, etc. Developers are also able to replace extractors, e.g. if you prefer another crawler library. The only issue left is a proper migration which doesn't take ages on large datasets. And proper documentation, especially on how to migrate the whole yaml setup. |
I worked on a command which will migrate a configurable amount of record each run. On the other hand … its up to everyone to stay on v1 and we could just release v2 with the migration path and new features. Maybe people give it a try and provide feedback if that approach doesn't work … we then could still provide v2.x which provides compatibility with both and allow a smoother transition. |
I am not sure I understand the problem. |
Yes, that's the "big" problem I see. Furthermore, one has to adjust the Let's see when I find time to finish. I'll then use the new version on my own site for a while before I'll merge and release the new version. |
We need to ensure that existing ignores are kept, e.g. #105 |
Right now the extension is not aware of bots.
It would make sense to add a flag to all records that define whether the tracking was triggered by a bot.
Those should then be allowed to be excluded from widgets. That way widgets can be created for humans as well as bots.
This way one can check which pages are called by humans and by bots, as well as which operating systems are used by bots and humans.
The existing rule should remove all the bot logic.
Instead a new option should be introduced which contains the logic.
Integrated into the existing update logic, existing records can be marked as bots afterwards. No existing data should be lost.
Open Todos:
Unkown
The text was updated successfully, but these errors were encountered: