Loading Profile...
GA tracking code said not present by Wasp
Hello - i was having problems with a google analytics link tagging not registering when i discovered wasp. on my site www.riverlife.com.au wasp doesn't actually show that Google analytics is present. Would you know why?
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
The best answer from the company
-
Hi Fabienne, indeed, WASP isn't detecting GA because GA is NOT working on that page. Although the JavaScript code is there, it is not running and thus, WASP doesn't see it.
The exact JavaScript error is: "uncaught exception: Operation is not supported (NS_ERROR_DOM_NOT_SUPPORTED_ERR)" at line 117.
Other GA detection tools generally only look if the .js code is there, while WASP actually look if the code is running. That's why WASP is simply better than other alternatives :)
This tells me in a future releases I should just check if the code is there and show a big red sign saying "code present but not working".
If you need further assistance in implementing Google Analytics I'll be glad to help as part of my consulting services.
Good luck,
Stéphane
I’m confident
The company says
this answers the question
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?Hi Fabienne, indeed, WASP isn't detecting GA because GA is NOT working on that page. Although the JavaScript code is there, it is not running and thus, WASP doesn't see it.
The exact JavaScript error is: "uncaught exception: Operation is not supported (NS_ERROR_DOM_NOT_SUPPORTED_ERR)" at line 117.
Other GA detection tools generally only look if the .js code is there, while WASP actually look if the code is running. That's why WASP is simply better than other alternatives :)
This tells me in a future releases I should just check if the code is there and show a big red sign saying "code present but not working".
If you need further assistance in implementing Google Analytics I'll be glad to help as part of my consulting services.
Good luck,
Stéphane
I’m confident
The company says
this answers the question
-
Inappropriate?Thanks Stephane for your answer. This is very bizarre, I am wondering what this error is related to.
Could you pls let me kn ow how long you anticipate it would take you to help me fix this problem and let me know your rate? Cheers! -
Inappropriate?Please contact me directly at shamel(at)immeria(dot)net.
-
Inappropriate?Hi - I actually figured out what was happening. The document.write function isn't supported by xhtml. I changed the definition to <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd"> and it now works like a charm. WASP sees the code and my original problem of link tagging is also working.
If it wasn't for WASP i wouldn't have known was was happening. Thanks Stephane! And I hope this response gets indexed and helps all other people in the same situation!
I’m so stoked
1 person says
this answers the question
2 Comments Add a comment
This answers the question
-
actually I found this (below) on this site http://www.googleanalyticsresults.com...
XHTML compliant version of the updated ga.js tracking code: -
Fabienne:
Thanks posting this question and thanks for the solution. We can try to implement the XHTML compliant version of the updated ga.js tracking code, which apparently is our issue as well.
Stephane:
I have a related question about WASP's ability to detect GA tracking code that is still not XHTML compliant:
The crawler report shows several pages from a site with "None" as the solution name. However, these pages are actually tagged, and Google Analytics is collecting their data.
In Firefox itself, the WASP status icon and sidebar show the pages as tagged with Google Analytics, but again the crawler reports "None" for the same pages.
The site is blog.insweb.com if you would like to test this out.
Thanks! -
Inappropriate?33b2b: As highlighted in a private email, one of the page the crawler said was not tagged actually has a problem. It seems the HTML is incomplete, there is no closing and the code stops just after the GA code... that could certainly cause intermittent problems! I reloaded the page several times to make sure and noticed it takes some time for the page to load, but each time, the source code was cut at the same location. Could it be a server-side issue?
So indeed, the WASP crawler might have been right in reporting the tags were not firing for those pages, even if looking at the page in the browser seemed to be working fine.
I’m confident
EMPLOYEE
