AbdFatah / analytics-issues

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

Add ga:isoYear as dimension. #321

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
Name of related component: Core Reporting API

Request summary:

Currently, there is an ISO week dimension, however, using it is quite hard for 
the reasons outlined here:
<https://groups.google.com/d/msg/google-analytics-data-export-api/6Yyodot3Tws/Oc
s-EdqadNMJ>
An example: when requesting data for the whole year 2012, segmented by 
ga:isoWeek, the result row for week 1 will also contain the data for December 
31st, 2012 (which is in 2013-W01). While this isn't technically wrong, it's 
probably also not very useful. Adding the ga:year dimension doesn't help, 
because the whole dataset is inside the year 2012.
Adding ga:isoYear as an available dimension would circumvent this problem as 
the data for 2012-12-31 in the above example would be labeled 2013;01 instead 
of 2012;01.

Use Cases:

Basically the same as for ga:week; being able to consistently report Analytics 
data segmented by ISO week for an arbitrary time range. 

Original issue reported on code.google.com by dorian.k...@webrepublic.ch on 5 Aug 2013 at 11:49

GoogleCodeExporter commented 9 years ago
I believe this has been fixed. 
https://developers.google.com/analytics/devguides/reporting/core/dimsmets#view=d
etail&group=time&jump=ga_isoyear

Original comment by nat...@chartio.com on 28 Oct 2013 at 7:59

GoogleCodeExporter commented 9 years ago

Original comment by pfrise...@google.com on 28 Oct 2013 at 8:41

GoogleCodeExporter commented 9 years ago
Thanks a lot!

Original comment by dorian.k...@webrepublic.ch on 29 Oct 2013 at 7:26