search

AbdFatah / analytics-issues

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

Counts discrepancy - GA vs Custom/legacy tracking report #88

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.swc
Analytics Data Export API

Issue summary:

Below code line is used send tracking info to Google Analytics.
  tracker.trackPageview(<<path built in the system>>);
Also the system has got its own tracking mechanism, to track pageviews.

There is a count mismatch between GA and legacy system. Legacy system has got 
85535 hits , but GA is showing arround 55k. There is a deviation of 30k. I 
checked with legacy system tracking details and confirm there the count is 
correct and have the details with dates and IP's , browser agent where they 
have come from.

Any issues with library analytics.swc in this perspective?

Steps to reproduce issue:
1.It is only a comparision over a duration of 60 odd days.

Expected output:
What do you expect to see after performing the above steps?
Count will deviate but it must be due to the processing delay at GA ( last 1-8 
hrs data)

Actual results:
What do you actually see after performing the above steps?
count showing a difference of 30k.

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 vmar...@gmail.com on 28 Jun 2010 at 7:34

GoogleCodeExporter commented 9 years ago 
No two tracking systems ever report identical stats, for several reasons, 
ranging from the way they track hits (log-based vs javascript-based) to how 
they define a session, visit, or visitor.  

The most likely reason for the discrepancy you're seeing is that your custom 
tracking system uses the raw web logs to monitor traffic instead of 
javascript-powered gif requests the way Analytics does.  This results in bots, 
spiders, feed aggregators, web scrapers, background page pre-loaders, etc being 
counted as traffic to your site in your custom solution, but since none of 
these actually fire Javascript, they're not counted in Google Analytics.  This 
would be consistent with the ~%35 difference you're seeing between your custom 
solution and Google Analytics numbers.

That being said, technically this isn't the right place to discuss these issues 
- This bug tracker is for the *Export* API, which is for pulling data out of 
Google Analytics.  If you want to inquire further, please ask in our help forum 
at: 

http://www.google.com/support/forum/p/Google+Analytics?hl=en

Original comment by api.alex...@gtempaccount.com on 28 Jun 2010 at 5:20

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:05