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

Add a new column in all reports for % percentage of visits #1816

Closed
mattab opened this issue Nov 15, 2010 · 63 comments
Closed

Add a new column in all reports for % percentage of visits #1816

mattab opened this issue Nov 15, 2010 · 63 comments
Assignees
Labels
Critical Indicates the severity of an issue is very critical and the issue has a very high priority. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Milestone

Comments

@mattab
Copy link
Member

mattab commented Nov 15, 2010

From email "I have always missed the simple ability to view the stats in percentages (as a third column). Most of the time, the percentage (let's say the percentage of mobile users as an example) is much more useful than the absolute numbers."

This would be a simple yet very useful add to Piwik.
Some challenges are:

  • do we display % visits, % unique visitors or % pages? not obvious, even though % visits is the most commonly useful.
  • do we add a new column in all widgets (in dashboard), or only in the main reports (when clicking on the menu)?
    Adding a new column in all widgets is a 'major' presentation change, but maybe worth it.
  • Add % visits, normalized data, in the Row Evolution report, useful to compare eg. browser usage share Show normalized visit stats in RowEvolution #3729
@mattab
Copy link
Member Author

mattab commented Nov 16, 2010

at the same time, should we fix #1125 ?

@anonymous-matomo-user
Copy link

I would like to extend this feature request to all widgets where it makes sense. I'm missing such a feature for many widgets heavily.

For instance Browsers or Visitor Continent, Countries, Search engines, Keywords, Referrers (external websites). e.g. percentages for the first 10 entries (Browsers widget calls this "low population") and a percentage for all others.

I'm also missing a figure for the totals, this could be displayed either in the title of a widget (e.g. "Visitor browsers (Total: nnnnn)" or in the first row of the first column that shows the column name (e.g. "Browser: Total: nnnn) or as the first data row ("All browsers ......"). I think the last version would be the one that fits all purposes because there's often more data than just one column (e.g. with browsers you can also show Actions, Bounce Rate etc.), so the display as a normal extra first data row would make for the best display.

Without percentages and totals the figures miss a lot of "interpretability". I can see trends and evolution, but I don't have statistics to which "groups" I cater unless I get my calculator and crush numbers myself.

@mattab
Copy link
Member Author

mattab commented May 25, 2011

Could we have the column also have a vertical bar in the background, or width proportional to the % ? that would allow visual overview of importance of each row

@anonymous-matomo-user
Copy link

I too would much like to view stats as percentages. I really miss this when trying to quickly compare browser versions etc.

@mattab
Copy link
Member Author

mattab commented Sep 15, 2011

  • Maybe we put the % visits next to Visits, in the same cell, in light grey? So that it is visible only when you look for it, otherwise does not add complexity or clutter to the UI? Add on sorted column only.
  • NOTE: see function addVisitsPercentColumn
  • This should also show up in scheduled report
  • Should be a new column, and shows Metadata, Piwik Mobile, Email reports, in reports where it makes sense

@DaSchTour
Copy link
Contributor

+1

@tsteur
Copy link
Member

tsteur commented Nov 19, 2013

In 7c15116: refs #1816 return ratio in API

@tsteur
Copy link
Member

tsteur commented Nov 19, 2013

In 06cfef9: refs #1816 display ratio on hover

@tsteur
Copy link
Member

tsteur commented Nov 19, 2013

In 4eba9c5: refs #1816 prevent line break

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In 6a77087: refs #1816 made it a bit more generic, request first level table only if needed, handle ecommerce columns

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In a782e06: refs #1816 only calculate it for reports having a dimension

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In 552874c: refs #1816 ratio calculation should be a bit faster this way

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In 721eac9: refs #1816 small ui tweak, align percentage value right

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In 4cec24f: refs #1816 use a gray that we already use somewhere else

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In 4793bc7: refs #1816 do not create metrics for ratio, instead add total values to tableMetadata and generate ratio in view

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In bb0e02d: refs #1816 display tooltip which explains percentage value in detail

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In c6240e6: refs #1816 it is a bit better readable this way, need to create a translation

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In e9e0c46: refs #1816 only display the first 40 chars of the label

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In 57a0a86: refs #1816 coding style

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In eaf9951: refs #1816 reportTotal is clearer instead of total

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In b0d7a5c: refs #1816 should not make any difference but make sure we get all rows

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In 4c87bcd: refs #1816 do not set an API request for each datatable, only request once, it is still not 100% right as the same total value is set for each dataTable

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In 4d4cbf4: refs #1816 this should set the correct value in case we are dealing with dataTable\maps, probably there will be still an issue with idSubtables

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In 803c3bc: refs #1816 this should fix calculation in case we are dealing with a datatable\map and a subtable

@anonymous-matomo-user
Copy link

Please, is there a way to stop the email for each single edit? I did not subscribe to any of this and I can't find an option to unsubscribe in settings of this trac account. If there is a way, please unsubscribe me silently. Thanks!

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In 5e56949: refs #1816 we always have to request the first level table to make sure we get all rows, not only the filtered ones

@anonymous-matomo-user
Copy link

Me too on the unsubscribe.

@gaumondp
Copy link

Guys, to unsubscribe I think you just need to go there:

http://lists.piwik.org/cgi-bin/mailman/listinfo/piwik-trac

Dali

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In c097f42: refs #1816 by generating total values before the generic filters, we only have to request the first level dataTable in case it is a subtable

@tsteur
Copy link
Member

tsteur commented Nov 20, 2013

In 1226e65: refs #1816 do not display second part of the tooltip if the total value is smaller than the report value to workaround reportTotalUniquePageviews are compared with Visits because UniquePageviews uses metric nb_visits

sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…eems to be not the case for instance if flat=1. Reproduceable if clicking flatten in custom variables
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…of date strings in case for instance when handling period=month
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…Method is not set. This means basically "do not run datamanipulators". It happens for instance when flat is enabled and it tries to load all subtables, there should be no need to calculate the datatable for each of those then
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…DecodeLabel, to not escape: otherwise error message non utf8 character might occur
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
…o request API summary as there will be no tooltip anyway
sabl0r pushed a commit to sabl0r/piwik that referenced this issue Sep 23, 2014
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Critical Indicates the severity of an issue is very critical and the issue has a very high priority. Enhancement For new feature suggestions that enhance Matomo's capabilities or add a new report, new API etc.
Projects
None yet
Development

No branches or pull requests

5 participants