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

Better Real Time reporting in Matomo: Actions in Real-time #2439

Closed
anonymous-matomo-user opened this issue May 20, 2011 · 7 comments
Closed
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently. duplicate For issues that already existed in our issue tracker and were reported previously. 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.

Comments

@anonymous-matomo-user
Copy link

Suggestion to have an "Actions in Real Time" widget... I think you already show this data in the real time visitors module but I have to hover over a lot of the recent pages viewed to try to determine what people are looking at. This is a proposal to do something like ChartBeat where you organize that info to display what content is popular NOW. I will try to attache a screen shot to this ticket.

This could be very similar to the "Visitors in Real Time" but instead of grouping pages for each visitor on one line, you would do the opposite... each line would be for a page of content (by title) and you would list little icons representing visitors underneath the page title.

The widget would be ranked by whatever pages have the most recent actions, perhaps in the last 15 minutes or so (or make this a configured option by the user). I also think it would be best to only represent a unique user a SINGLE time within the entire module... that user would appear on the content they most recently viewed. That way, if a user goes randomly clicking a dozen pages on the site without really looking at them, it doesn't skew the numbers too much. The main idea is to show what pages on a site where users are at the moment, and they can't be paying attention to more than one page (for the most part).

You might also check out how ChartBeat works, as this is a proposal for similar functionality to the major focus of their product. In my opinion, this is the biggest thing missing from Piwik for people like myself wanting to switch from ChartBeat. Piwik is SO much more robust than ChartBeat in other areas, but it is hugely helpful to see how content is performing on the site grouped by activity on each piece of content in real time. I monitor chartbeat very closely and within 2 or 3 minutes of putting up a new post on my blog I can tell if it is a winner or loser. I can also immediately see if I suddenly am getting a BIG link driving a lot of traffic to a post.

Thanks so much for considering this!

@anonymous-matomo-user
Copy link
Author

Attachment: Screenshot of Chartbeat Dashboard
chartbeat-avc-dashboard.jpg

@mattab
Copy link
Member

mattab commented May 21, 2011

Look it would be really fantastic to improve Real time reporting in Piwik... if you can sponsor this work please contact us via: https://piwik.org/contact

If anyone has suggestions or ideas, feel free to leave a comment - What do you most need from Piwik in real time?

@anonymous-matomo-user
Copy link
Author

Hi Matt, unfortunately I'm not in a position to sponsor a feature at the moment.

But while I'm here, let me just add a little more info about how ChartBeat does this in case someone decides to look at this in the future. My proposal above is for something more simplified than what they do, and something that I think would be easier to implement with the existing framework of Piwik.

ChartBeat, on the other hand, attempts to measure user activity on the page and how long people stay on it. They breakout reading, writing and idle activity types. So I suppose they are keeping the user included in the statistics as long as the browser window is open.... and I'd also assume that a user could be counted as on multiple pages at once. If you ask me, I think this is overly complex and probably imprecise anyway. It can also lead to some incorrect assumptions about "current" activity on a website if a lot of the content that appears active is really only windows that were left open. That's why my original post in this ticket proposes that a single user is only counted under a single page at any one time, and that the users just time out after a set period unless it would be easy to determine exactly when they've left a page (and the site for the current visit).

@anonymous-matomo-user anonymous-matomo-user added this to the 2.x - The Great Piwik 2.x Backlog milestone Jul 8, 2014
@mattab mattab removed the Major label Aug 3, 2014
@mattab mattab added c: Usability For issues that let users achieve a defined goal more effectively or efficiently. and removed c: UI - UX (AngularJS twig less) labels Oct 12, 2014
@mattab mattab added the Major Indicates the severity or impact or benefit of an issue is much higher than normal but not critical. label May 27, 2016
@mattab mattab modified the milestones: Mid term, Long term May 27, 2016
@lemon2015
Copy link

If the administrator can see who is visiting the website and who left the website, it would be perfect.

@mattab mattab changed the title Better Real Time reporting in Piwik Better Real Time reporting in Piwik: Actions in Real-time Oct 30, 2018
@mattab mattab changed the title Better Real Time reporting in Piwik: Actions in Real-time Better Real Time reporting in Matomo: Actions in Real-time Oct 21, 2019
@mattab mattab removed this from the Priority Backlog (Help wanted) milestone Nov 3, 2019
@mattab
Copy link
Member

mattab commented Nov 3, 2019

Great mockup suggested by a user for a Real-time Pages based reporting:
IMG_0082

@mattab
Copy link
Member

mattab commented Nov 3, 2019

Also received these screenshots of other similar apps:

another2

another

@mattab
Copy link
Member

mattab commented Jul 4, 2022

Duplicates #14392

@mattab mattab closed this as not planned Won't fix, can't repro, duplicate, stale Jul 4, 2022
@justinvelluppillai justinvelluppillai added the duplicate For issues that already existed in our issue tracker and were reported previously. label Sep 29, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Usability For issues that let users achieve a defined goal more effectively or efficiently. duplicate For issues that already existed in our issue tracker and were reported previously. 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.
Projects
None yet
Development

No branches or pull requests

4 participants