Opened 3 years ago

Last modified 13 days ago

#2541 new New feature

Aggregate data for multiple (groups) of websites

Reported by: matt Owned by:
Priority: normal Milestone: Future releases
Component: Core Keywords:
Cc: Sensitive: no


Placeholder ticket for processing aggregated reports for multiple websites.

For example, API functions could accept idSite=1,2,3,4 to return "top keywords" for the websites 1,2,3,4. This would be a useful feature for large Piwik setups, where one customer would "own" several websites and would like to see aggregated stats for all his/her websites.

Change History (5)

comment:1 Changed 3 years ago by TheDudeAbides

The basic stats implementation could be similar to how "profiles" work in google analytics, so you could create, edit, assign and delete websites from groups at will, and view the main traffic numbers for each via the All Websites Dashboard. Adding individual or expand/collapse all functionality to that dashboard would also be helpful.

comment:2 Changed 3 years ago by matt (mattab)

Some thoughts on this feature...

1) Report aggregate
a- Aggregate "numbers" like visits, actions, time on site, revenue, conversions, ecommerce orders, ecommerce cart abandoned.
b- Aggregate "reports" like: Top keywords, top websites, visits per hour, top page URLs, page titles, ecommerce products, etc.

I assume that both aggregates are important/nice to have.

The algorithms to sum reports are more or less already there in the code (used for the "Date Range" feature for example).

The question remains regarding how to request reports.

2) Requesting reports

We could allow to request the consolidated report for "all site in a group", "all sites for a user"... or we could at first, allow consolidated report of a comma separated list of IDs: &idSite=1,4,55,332 which users would build (by getting site IDs from a website group, or site ID for a given user).

3) User Interface VS API
Implementing in the API only is the first step.

Then, we could also somehow display the consolidated reports in Piwik UI, but maybe this is not needed in V1.

4) Pre-processing reports?

We could maybe pre-process the reports, or we could simply wait until they are requested and then fetch all reports for each site in the request, and sum in real time. This should be fairly fast since there are no logs to run a query against (we assume that all individual website reports are themselves pre-processed).

I propose that at first we don't pre-process the "consolidated" reports. We can expect response time in the range of 1 second if requesting consolidated "Top Keywords" for around 10-20 websites.

comment:3 Changed 14 months ago by pebosi

Any updates on this?

comment:4 Changed 13 months ago by matt (mattab)

@pebosi, no update

comment:5 Changed 13 days ago by matt (mattab)

  • Priority changed from major to normal
Note: See TracTickets for help on using tickets.