Closed (fixed)
Project:
Google Analytics
Version:
5.x-1.5
Component:
Code
Priority:
Normal
Category:
Support request
Assigned:
Unassigned
Reporter:
Created:
30 May 2008 at 00:12 UTC
Updated:
14 Jun 2008 at 08:31 UTC
Hi,
I've installed the module and have inserted the tracking code into the "custom java script code" field. I have removed the script tags (the snippet now looks like this"
var gaJsHost = (("https:" == document.location.protocol) ? "https://ssl." : "http://www.");
document.write(unescape("%3Cscript src='" + gaJsHost + "google-analytics.com/ga.js' type='text/javascript'%3E%3C/script%3E"));
var pageTracker = _gat._getTracker("xx-xxxxxxx-x");
pageTracker._initData();
pageTracker._trackPageview();and I have selected the "latest tracking code" option. However, I am still getting a "tracking unknown" message on the GA site. Clearly I'm doing something wrong but I can't figure out what it is.
Any help would be greatly appreciated.
Many thanks,
Ole
site: http://cleftworld.com
Comments
Comment #1
hass commentedOnly a few very simply questions i need an answer for...
PLEASE give me a hint what we could approve after we added the word CUSTOM and why nobody can read the description text of the Custom JavaScript code? Keep in mind the word custom...
1. Why is it so impossible to read the description?
2. What would a user think if he/she read custom?
3. Why are users trying to add standard code to a text area with a custom title and a description linked to documentation pages with very good examples what a custom javascript code is?
I *really* thought long time how to improve the text and changed it 5 or 6 times and I finally do not understand what is so impossible to understand on the above description.
Thank you for your answers.
Comment #2
stormer commentedHi Haas,
apologies for not understanding the instructions. I guess part of the problem is that you assume people are familiar with all these terms and have some kind of background relating to all of this. Unfortunately I am not one of those people - I am a designer and animator with absolutely no experience in css, php, java etc. Should that exclude me from using Drupal? I don't think so, after all, isn't that Dries' aim, to make Drupal accessible to everyone? I think Dries and the Drupal community have done an incredible job with this software - it's just astounding how much someone like myself can put together but, there's a lot that's beyond the likes of myself.
As to your text, "You can add custom Google Analytics code snippets ..." doesn't say an awful lot to me. When I saw the word "custom" I thought it referred to the Google code that I am supposed to insert to activate GA - after all, it IS custom code since my bit of code is not exactly the same as the code someone else inserts (I assume). From your post I assume that I am not the first one to make this mistake so clearly things need to be reworded (again) - perhaps you should be telling people what NOT to do eg: "You can add custom Google Analytics code snippets. These snippets are NOT to be confused with the code snippet (or even better, the "activation code") that Google asks you to insert in order to activate GA".
So, now that I know this is the wrong field for the activation code, I'll keep hunting around.
Many thanks for your hard work that has obviously gone into this module - it's pretty much made the whole SEO thing something that even inexperienced users like myself can eventually manage.
Regards,
Ole
Comment #3
hass commentedWell - you are not the first and i really hoped to have this *finally* solved in 5.x-1.5 and 6.x-1.1, but it seems not. :-(
I'd simply like to understand why people using "Advanced" functions for highly *experienced* GA users and "Custom" textareas in "Advanced" fieldset sections and refuse to read the documentation in the module and the handbook that both are telling what this field is for. If people would read the README or handbook we wouldn't have this support issues.
I think i will add a validation check for GA code parts on this field and provide an error message that this field is NOT for this original GA code stuff. I'm sure this will nevertheless not stop people trying to insert this code there.
Comment #4
hass commentedMore validation has been added.
Comment #5
Anonymous (not verified) commentedAutomatically closed -- issue fixed for two weeks with no activity.