AbdFatah / analytics-issues

Automatically exported from code.google.com/p/analytics-issues
0 stars 0 forks source link

Combinatorial Results when doing a dimension request #20

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
--------------------------------------------------------------------------
NOTE: This issue tracking system is for developer products only.  If you
are not a developer/programmer and have a problem with a Google web site,
please report the problem to the appropriate group.  More information can
be found here: http://www.google.com/support/
--------------------------------------------------------------------------

Name of API affected:
Analytics Data Export API

Request summary:
Currently, when you do a request for a metric on multiple dimensions you get 
back ONE entry for each combination.  So when 
you do a request for say new visits by source, country and medium you would get 
each combination of source, country and 
medium WITH THE EXCEPTION of each dimension as a NULL case.  

This means that if I want to see new visits by JUST source or JUST source + 
medium I need to do yet another request, take up 
time and processing for both of us.

Instead, if you returned the combinatorial possibilities of any multi-dimension 
request (or provided an option for it) then 
everything could be returned in a single call, which is far more efficient.  
The use case gives an example below.

Use Cases:
Say I wanted new visits by source, medium AND country.  I would request 
ga:newVisits with dimensions ga:source, ga:medium 
and ga:country and maybe add something like "permutations=true" or whatever.

Then, the feed would return new visits segmented by the following:

source ALONE
medium ALONE
country ALONE
source + medium 
source + country
medium + country
source + medium + country

The response object doesnt need to change, except the client would need to 
realize that all three requested dimensions are 
not going to appear in every entry since you are returning permutations, which 
should be the correct behavior.

Original issue reported on code.google.com by jlippi...@gmail.com on 20 Sep 2009 at 5:01

GoogleCodeExporter commented 9 years ago
Removing an obsolete label that was used when these issues were in the 
gdata-issues project.

Original comment by jrobbins@google.com on 21 Jul 2011 at 10:04

GoogleCodeExporter commented 9 years ago
Changing the issue type to match the organization desired in this project.

Original comment by jrobbins@google.com on 21 Jul 2011 at 10:06