-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
allow grouping by dimension in reporting API #6227
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
Comments
+1 this is a killer feature indeed! Unfortunately not trivial. We could start making it work for one level Note: The beauty of this solution is that it will enable Custom Reports ie. create any combination of dimensions and sub-tables. This is the first step required for #4776 Custom Reports, Pivot table feature for Piwik |
If implemented, perhaps site ID and period can be turned into segments so there is just the segment query. Just an idea that popped into my head, maybe not a good idea, but seems like it would make the API more generic. |
If implemented efficiently, we can remove 'subtable' archiving code for reports like Referrers.getKeywords and Events.getName, since we can just use a groupBy in archiving. Actions will still need subtables though. |
this would also allow a fix for #11755, right? |
BTW this can be done with Custom Reports. You can create a report via the API and specify by what it should be grouped, then fetch the report... Learn more about the power of Custom Reports in the user guide: https://piwik.org/docs/custom-reports/ or FAQ: https://piwik.org/faq/custom-reports/ This premium plugin can be purchased here: https://plugins.piwik.org/CustomReports |
@tsteur if this functionality is provided by a plugin, can this be closed? |
Considered done as it is available in custom reports product: https://piwik.org/docs/custom-reports/ |
Too bad this gets closed, as the plugin/product is apparently not free: https://plugins.matomo.org/CustomReports |
This ticket is for allowing some way to specify one or more dimensions that can be used to group metric result. For example, the query: groupBy=city&method=Referrers.getKeywords could result in:
To accomplish efficiently this will require changing the archiving code significantly and should wait until it is refactored.
The text was updated successfully, but these errors were encountered: