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

[mattab]

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]

at the same time, should we fix #1125 ?

[anonymous-matomo-user]

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]

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]

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

[mattab]

• 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]

+1

[tsteur]

In 7c15116: refs #1816 return ratio in API

[tsteur]

In 06cfef9: refs #1816 display ratio on hover

[tsteur]

In 4eba9c5: refs #1816 prevent line break

[tsteur]

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

[tsteur]

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

[tsteur]

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

[tsteur]

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

[tsteur]

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

[tsteur]

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

[tsteur]

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

[tsteur]

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

[tsteur]

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

[tsteur]

In 57a0a86: refs #1816 coding style

[tsteur]

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

[tsteur]

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

[tsteur]

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]

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]

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

[anonymous-matomo-user]

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]

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]

Me too on the unsubscribe.

[gaumondp]

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

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

Dali

[tsteur]

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]

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