mcsimpentinen / analytics-issues

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

use the ISO standard week numbering so weeks would always be seven days #55

Closed GoogleCodeExporter closed 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:
use the ISO standard week numbering  so weeks would always be seven days

Use Cases:
ga:week queries which span annual boundaries have to be handled as a
special case since if the week spans the year boundary you don't get data
for a complete week.

Original issue reported on code.google.com by back5...@gmail.com on 27 Jan 2010 at 5:46

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

GoogleCodeExporter commented 9 years ago
Issue 142 has been merged into this issue.

Original comment by n...@google.com on 23 Nov 2011 at 8:06

GoogleCodeExporter commented 9 years ago
Issue 142:

Name of affected component: Data Export API

Issue summary:
ga:week currently starts from Sunday. This is a major issue for most of our 
european clients.

Notes:
I would suggest a new ga:isoweek or something, since a week starts on Monday 
according to the International Standards Organisation. See reference here: 
http://en.wikipedia.org/wiki/ISO_week_date

Original comment by sebastia...@gmail.com on 9 Dec 2011 at 9:09

GoogleCodeExporter commented 9 years ago
(Cross-posted from the google-analytics-api group as it is relevant to this 
issue)

I'm experiencing a peculiar behavior when I request data segmented by 
ga:year,ga:isoWeek whenever a date range is specified that crosses a year 
boundary. An example copied straight from the Google API Explorer, requesting 
data from 2012/12/13 to 2013/01/01:

GET 
https://www.googleapis.com/analytics/v3/data/ga?ids={GA_ACCOUNT}&start-date=2012
-12-31&end-date=2013-01-01&metrics=ga%3Avisits&dimensions=ga%3Ayear%2Cga%3AisoWe
ek&sort=ga%3Ayear%2Cga%3AisoWeek&key={YOUR_API_KEY}

This returns:

 "rows": [
  [
   "2012",
   "01",
   "58974"
  ],
  [
   "2013",
   "01",
   "64839"
  ]
]

If you use ga:year,ga:week as dimensions instead, the return rows look like 
this:

 "rows": [
  [
   "2012",
   "53",
   "58974"
  ],
  [
   "2013",
   "01",
   "64839"
  ]
 ]

This latter looks correct, while the former seems incorrect to me, as December 
31st, 2012 belongs to ISO week 01/2013.

Could someone please take a look at this?

Many thanks and best regards

Original comment by dorian.k...@webrepublic.ch on 12 Jul 2013 at 9:26

GoogleCodeExporter commented 9 years ago
The problem described in the previous message is due to Google Analytics not 
supporting the ISO year in correspondence with the ISO week.  An ISO week is 
quite meaningless if you don't know what year it is associated with.

Original comment by m...@chartio.com on 29 Jul 2013 at 11:47

GoogleCodeExporter commented 9 years ago
The Google Analytics API now supports ga:isoYear and ga:isoYearIsoWeek. 
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 8:01

GoogleCodeExporter commented 9 years ago

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