Make Visitor log a central tool, to bundle & standardise actions "on" and "learning from" tracked data

[hpvd]

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: 1) delete Visit 2) delete the visitor belonging to this visit (and all of his visits) 3) delete all visits and visitors of one IP 4) this is a bot (bot list learning) 5) mark/flag Visit 6) mark/flag the visitor belonging to this visit

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

• an element to select a visit
• an element to select an action
• an element to put in details (if selected action need some)
• an element to apply everything

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)

[hpvd]

an other idea for extension, similar to "bot list learning" (nr 4 on list above) 7) easy way for "device learning": could be done of course in own Piwiks on sites,in a developement site or on a central site of Piwik team. The steps are the following:

1. Visit a site,
2. find visit in visitorlog (e.g. via time & IP),
3. see device type is "unknown" press "Tool button",
4. select action "add device information",
5. put in information,
6. press apply button, done

in best way this updated device list is synced back to Piwik...

9183

[hpvd]

with this one could detail the technics behind the scene: there should be a standard scheme for developers for how to define new actions (which are shown in popup for selection by the user), consisting at least of

• action name
• allowed circumstances, definition of circumstances when it's allowed (possible) to apply this action e.g. device type is "unknown"
• needed details: a form, shown to the user with standardized options (possible types: e.g. text line, text field, dropdown, multiselect; a possibility to make each option mandatory or optional) to collect the needed data for this action
• the technical logic code what happens with the data of the user input

[hpvd]

when syncing the by the users enhanced bot-list and device-list back to piwik, one could make the power of the crowd (all these non-developer users out there) accessible to make piwik better and better (=> of course this is an topic for an extra ticket, edit: #9183)

[tsteur]

:+1: like that :)

[hpvd]

other action for this tool: 8) receive optimized/best detailed geoip data on click for a visit using advanced, non free databases as webservices (payed per use) see https://github.com/piwik/piwik/issues/8121

[hpvd]

for further enhancement: making "mass actions" possible: Applying the same action on several, selectable visits with minimum effort see #9197

[hpvd]

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. For each step a own issue could be opened to document and discuss the details. Doing this one could simply copy already available details from this ticket to the new one.

A good start could be the implementation of the delete feature (idea 1 and idea 2) which is already discussed to be highly needed in #3385 Here you find this 1. step: general setup + actions of type delete #9204

[atom-box]

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.'