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
Make Visitor log a central tool, to bundle & standardise actions "on" and "learning from" tracked data #9182
Comments
an other idea for extension, similar to "bot list learning" (nr 4 on list above)
in best way this updated device list is synced back to Piwik... |
with this one could detail the technics behind the scene:
|
when syncing the by the users enhanced bot-list and device-list back to piwik, |
👍 like that :) |
other action for this tool: |
for further enhancement: |
this issue could be a collection of ideas what could be done with this vistor log tool (at this time 8 different types of action) and how it could be done in general. Since this is a standardized approach, the different types of action could be implemented step by step. A good start could be the implementation of the delete feature (idea 1 and idea 2) which is already |
A user suggests: 'In rare cases, I receive bot calls. These distort the statistics by hundreds or thousands of clicks and deleting the data points from the Matomo database is unnecessarily complex. A button in the dashboard similar to "Treat session as spam" would be ideal here. Attached to this, it would be an idea to record the bot attacks separately.' |
Enhance Visitor log to be a central tool,
to bundle and standardise actions
a) doing on tracked data and
b) learning from tracked data,
where you can do several things already described within several issues:
This general approach will help greatly to keep look and feel and also all technical processes in background clean and straight forward.
Details:
for 1) delete e.g. because you noticed it was you/ your colleague, it was a developer test etc...
#3385
for 2) delete e.g. because you noticed it was you/ your colleague, it was a developer test etc...
for 3) delete e.g. because you noticed it was you/ your colleague, it was a developer test etc...
from comments in #3385
for 4) bot list learning: put on bot list and don't show again/exclude from statistic but do not delete
related to #9067
in best way this updated bot list is synced back to Piwik...
#9183
for 5) give an extra "name" which could be used in segmentation afterwards or input "additional information" e.g. if there was something wrong and another developer should look on this
#8161
for 6) give an extra "name" which could be used in segmentation afterwards or input "additional information" e.g. if there was something wrong and another developer should look on this
How could this be done?
4 Elements are needed
One idea is to put these elements in a popup which can be brought up with a small button
on each visit in visitor log
A 5th element "an undo-Button" on top of visitorlog would complete it (idea from #9181)
The text was updated successfully, but these errors were encountered: