-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
API Report metadata Improvements list #1491
Labels
Task
Indicates an issue is neither a feature nor a bug and it's purely a "technical" change.
Comments
from #1514
|
See related #2670 |
Moved "add subtable report to call to fetch subdata (eg. keywords BY search engine)" to ticket #2742 |
See also #3242 |
This was referenced Jul 26, 2010
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
This is a followup to #1485
See existing functionnality in API.get* methods from the API page.
Metadata improvement list:
include per goal conversions, revenue and conv. rate for each segmentadd Column description (on hover) in the metadata(Major) Add support for date ranges / time periods (for Piwik Mobile Line Graphs and other evolutional views)The final state could be that each plugin defines in their metadata the default display options for each report. We would then have to set this array of options to the ViewDataTable which would call the specific functions setColumnSorted() setColumnsToDisplay() setFooterMessage() etc.
Other UIs (like Mobile Piwik client) and other report exports (like PDF reports) could benefit from these as well, which would also ensure consistency and make Piwik reports clear to understand.
The text was updated successfully, but these errors were encountered: