Skip to content
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

Visitor Log list of ideas and improvements #1839

Closed
mattab opened this issue Nov 24, 2010 · 21 comments
Closed

Visitor Log list of ideas and improvements #1839

mattab opened this issue Nov 24, 2010 · 21 comments
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. worksforme The issue cannot be reproduced and things work as intended.

Comments

@mattab
Copy link
Member

mattab commented Nov 24, 2010

This ticket is a placeholder for potential improvements to the Visitor Log report & Live! widget

Visitor Log ideas promoted to their own tickets

To be discussed / brainstormed

  • DONE ~ Add dropdowns / filter UI to filter visitor-log for specific purposes, e.g show only visitors that converted a goal, did a minimum of xx Actions on the page, bounced immediately (identify bad traffic sources) ~
  • Label Visitors : Possibility to label a visitor IP with a name, and display the label in the row matching this IP.
    • tag users in the Live widget (already suggested for visitor log)
    •   The visitor log could also display the "Sitelink" position of a given click when coming from google search.  
      
    • the paging info should be passed in the hashtag so that when the link is given to a friend the url loads the right paging directly
  • Add a template hook for plugins to augment the Live widget, eg
    • whois lookup
    • chat with visitor

If you have more ideas for features in the Visitor Log, please post a comment.

@anonymous-matomo-user
Copy link

For me now the folder icons for pages have the same color appearance from left to right.

We should make it instead so that the same page has always the same color!
At the first data creation colors should be given to pages opened. Each newly opened page should be given a different color and stored in the database. So if another user opens pages one can see the order of pages they opened from the color of the icon and do not have to mouseover. This would give the admin a real quick overview. Files should start over at the beginning color but with a different icon.

And because the colors would be given by random one could create a pretty high number of colors before they are doubled.

So if one user opens Site 1,2,3,4 (e.g. red,blue,green,yellow) and the other user opens 1,3,2,6 it would be shown as red,green,blue,pink(new color since not opened before).

What do you think?

@mattab
Copy link
Member Author

mattab commented Dec 12, 2010

~~ * see code improvement suggestion in #1120~~

@mattab
Copy link
Member Author

mattab commented Dec 23, 2010

~~ * see request for page title at least (when URL empty when using Image Tracking): http://forum.piwik.org/read.php?3,70034~~

@mattab
Copy link
Member Author

mattab commented Mar 11, 2011

* Visitor Log could show time of each action since we have the data. For example in <accr> markup, or something similar (on hover, not display by default since too much info)

@mattab
Copy link
Member Author

mattab commented Mar 18, 2011

@mattab
Copy link
Member Author

mattab commented Mar 23, 2011

It seems the filter_limit maybe doesn't work in Visitor Log export (see post in http://forum.piwik.org/read.php?2,73962 )

@mattab
Copy link
Member Author

mattab commented Apr 5, 2011

(In [4314]) Refs #1839

  • showing 'page url not defined' when no url in Visitor Log
  • now showing Page title as well as linked Page URL in Visitor Log (and simplyfing API output + 1 extra query instead of 2 extra queries for each visit)
  • also showing, oh hover over the page title & URL, the Time of page view (in website timezone) for each page, in Visitor Log and in Live! widget
  • showing "Goal converted" only for the actual page view that converted the goal (before, the Goal would show for all the same page URLs matching the page URL that matcehd the goal (but in fact, until 1.3 where we implement multiple conversions per visit, only one URL would have triggered the goal)

@mattab
Copy link
Member Author

mattab commented Apr 7, 2011

(In [4349]) Refs #1839 Simplyfying Live! plugin, removing unused code, cleaned up API, only 3 useful functions left with proper names (and more performant too),

  • adding tests, this one dedicated to Anthon ;)

Refs matomo-org/matomo-mobile-2#1956 while Live! is not metadata compliant, I now consider the API stable (efficient + function names & parameters) and Piwik Mobile can start using it :)
Let me know if you need any other api/ doc / info :)

NB: build will fail since it's pending another change in tracking API which I'll commit asap

@mattab
Copy link
Member Author

mattab commented Apr 7, 2011

(In [4351]) Refs #1839
Trying to get the API output right for 1.3,
reusing Segment names when fields are already 'segments' therefore have a 'public friendly name',
adding missing attributes (visit count, days since first / last visit / 16 chars visitor ID)

@mattab
Copy link
Member Author

mattab commented Apr 8, 2011

Cleaned up feature requests in description and moved some of them to #2281.

Created new page Real time analytics to show what is current feature set as it's pretty awesome really :) feedback on this page most welcome by email

@robocoder
Copy link
Contributor

Add a template hook for plugins to augment the Live widget, eg

  • whois lookup
  • chat with visitor

@robocoder
Copy link
Contributor

re: comment:16 could also be used to:

  • tag users in the Live widget (already suggested for visitor log)
  • delete a visit that should have been ignored (i.e., admin forgot to set ignore cookie)

@mattab
Copy link
Member Author

mattab commented May 23, 2011

(In [4774]) Refs #1839 Remove duplicate <ecommerce> entry at the root, listing all ecommerce actions in the visit, because it takes space for no good reason (consumers can use xpath to find ecommerce actions)

@mattab
Copy link
Member Author

mattab commented May 23, 2011

(In [4776]) XML output cleanup: empty elements were displaying as <referrerName></referrerName>, they now display as <referrerName /> Refs #1839

@anonymous-matomo-user
Copy link

I would love it if there was a global search field throughout Piwik so we can search by url, ip address, referrer, time, date, etc.

Maybe even with the ability to select which module to restrict the query to as well?

It would make it so convenient to get more info.

@mattab
Copy link
Member Author

mattab commented Sep 21, 2011

walterfry, filters will be covered with segment creator UI at #2135

  • The visitor log could also display the "Sitelink" position of a given click when coming from google search. reference

@mattab
Copy link
Member Author

mattab commented Nov 12, 2011

  • the paging info should be passed in the hashtag so that when the link is given to a friend the url loads the right paging directly

@mattab
Copy link
Member Author

mattab commented Aug 25, 2012

Including Anthon's ideas in the ticket description.

Moved features to specific tickets:

@anonymous-matomo-user
Copy link

I really love the Visitor Log FILTER Idea!

Just yesterday I was searching for entries with a specific keyword included. This would be really really handy for evaluating the user actions on a specific event.

+1 from me!!

@mattab
Copy link
Member Author

mattab commented Sep 19, 2012

Clarifying roadmap & listed all other tickets about visitor log

@mattab
Copy link
Member Author

mattab commented Apr 6, 2014

@MarcusSmith filters in Visitor log are now implemented. Use custom segments

This ticket is now all done I think, good to see our progress!

This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc. Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. worksforme The issue cannot be reproduced and things work as intended.
Projects
None yet
Development

No branches or pull requests

3 participants