kalnyc67 / analytics-issues

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

incorrect weekly data #80

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

Issue summary:
Provide a brief summary of the issue you're experiencing.
I am seeing the incorrect data from the Query Explorer. I was looking for
the weekly data from 2009-03-21 to 2010-02-04 for this table id ga:5757708.
Interestingly, I found out that the data displayed for total visiting
number is not match the one I add up regarding to week 12 which only have
one date that is 03/21/2009. The query Explorer display 597, but when I try
to add up all the urls visiting numbers, I got only 580. Please refer to my
attached xls file.

Follow this, it looks like all the weekly data doesn't have the right
value. Please tell me what I am missing. I have attached my own table that
shows each week total visiting number for all the urls.
Steps to reproduce issue:
1. enter table ID: ga:5757708
2. enter dimension: ga:week,ga:year,ga:pagePath
3. enter ga:visits,ga:pageviews,ga:timeOnPage,ga:exits
4  enter sort: ga:year
5. enter start-date:2009-03-21
6. enter end-date: 2010-02-04
7. enter max-result:50

Expected output:
What do you expect to see after performing the above steps?
I should see 580 for total visiting in week 12
Actual results:
What do you actually see after performing the above steps?
597
Notes:
Provide any additional information which might be useful here. Feel free to
attach screenshots or sample code which demonstrates the issue being
described.

Original issue reported on code.google.com by kevin...@glic.com on 29 May 2010 at 1:00

Attachments:

GoogleCodeExporter commented 9 years ago
How do I get the attention from google regarding to this issue?

Original comment by kevin...@glic.com on 15 Jun 2010 at 2:59

GoogleCodeExporter commented 9 years ago
We need a little clarification to investigate - Where did you pull the numbers 
shown in your spreadsheet?  Is it an export via the Analytics web interface, or 
a third party app using the API?

Also, what happens when you use the exact same dimensions & metrics in Query 
Explorer that are shown in the spreadsheet (Your Query Explorer query does not 
currently include ga:pagePath) ? Same thing, or do the numbers match up now?

Original comment by api.alex...@gtempaccount.com on 15 Jun 2010 at 5:13

GoogleCodeExporter commented 9 years ago

Original comment by api.alex...@gtempaccount.com on 15 Jun 2010 at 5:14

GoogleCodeExporter commented 9 years ago
Hi,

Thank you for your reply.
To clarify, I did three comparisons. The CSV is where I copy the result from 
the Query Explorer and dump it into XLS in order to calculate the total 
visiting number. When I did that I got 580. Notice that, that query include 
ga:pagePath, so that I can get all the visit number for every path.
The second one, I directly ran from query browser without ga:pagePath and it 
gave me 597. 
Then, the last thing I need is to use API to grap the data with ga:pagePath and 
do the aggregation from my program. Then I got 580.
Hope it is clear.
P.S. I redo again and got the same result. Also, I have submit another ticket 
which is 2097. That one is more interesting.

Original comment by kevin...@glic.com on 15 Jun 2010 at 6:29

GoogleCodeExporter commented 9 years ago
Thanks for the extra information, Kevin!  We'll investigate.

Original comment by api.alex...@gtempaccount.com on 1 Jul 2010 at 8:13

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