Forum Moderators: DixonJones
The only problem I'm having with it is that in my log files I'm seeing quite a few 404's with URLs like:
"GET /myrealfolder/google-analytics.com HTTP/1.1" 404
With the old one however I was seeing a similar problem:
"GET /__utm.gif HTTP/1.1" 404
I have no idea why some browsers are triggering those errors, I've seen them happen to other files on that site that are properly linked, including full, absolute URLs so I'm not sure this is even an G. Analytics issue.
We are also seeing some differences in qauntity. We've started recording the ecommerce code that our site has generated and are comparing it with what Analytics eventually reports. Interestingly, the log suggests the code is working perfectly, but analytics isn't always outputting what the code has generated.
We've run a number of tests and are now in talks with Google about this. There are quite a few threads now appearing online with people highlighting similar issues.
Are these the sorts of issues you are experiencing.
Before I even contacted Google I started recording the values transmitted to them and everything looks fine - but doesn't show up in the Analytics reporting.
On all transactions, the individual products and revenue are being recorded correctly, it's simply the transaction revenue total that shows $0
William.
Showing a few weeks later is OK in some instances, but when your comparing daily performances of various campaigns, waiting a week or 2 really doesn't help.
Basically in the overlay I'm getting the same number, waaaay over what it should be, on three links. It's as if it's reading three completely different links to different page as if they are all the same one.
Is GA's new javascript tracking code working fine?
Not for us it isn't. We are continually getting 404's with the google-analytics.com/ga.js call. A recent response from my programmer in regards to this issue...
It's the javascript not executing properly for them. I'm not sure why it is executing incorrectly. BTW, the proper way should be window.location.protocol.Below you'll notice that it will append the [ssl....] or [www....] depending on the host. Somehow host value was not set so you get...
<script src='google-anayltics.com/ga.js' type='text'></script>That's why you have the 404.
We micro-manage 404s and this is a pain in the arse as our mailboxes get diluged with 404 errors throughout the day. :(
2008-01-29T08:55:00-0700 - The GA js is causing 404's right at this very moment.
The downside is that it is one of the more important parts of the software where the issues are occuring - ecommerce. We're lucky we record this through other channels at the same time, otherwise we'd have a greater urgency to change tracking.
We're still seeing a bit too many 404s from Google Analytics. Anyone else out there doing finite tracking of 404s and seeing these on a daily basis?
google-analytics.com/ga.js
In speaking with my programming team, they inform me that it appears to have something to do with the second call to Google's server, the http vs https, we're not 100% sure just yet. I want to find out if anyone else is tracking these and if they've determined how to prevent them or can tell me not to worry about them, all is okay. ;)