Loading Profile...
Identification issue with GA? How do we know if code is running or not.
Hi,
Is WASP still having a problem to identify GA? For a web page http://brandstack.com, it does not identify GA when the source code shows it.
Also it will be great if you can tell us what the identification limitations of WASP currently are.
Thanks so much.
Romy
Is WASP still having a problem to identify GA? For a web page http://brandstack.com, it does not identify GA when the source code shows it.
Also it will be great if you can tell us what the identification limitations of WASP currently are.
Thanks so much.
Romy
I’m confused
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 company marked this question as answered.
Create a customer community for your own organization
Plans starting at $19/month
-
Inappropriate?WASP detects ClickTale and Clicky on your pages, but somehow, GA doesn't seems to fire. Even if you see it in the source code it doesn't mean the code actually works. WASP looks at the running code, not the source code. If it doesn't show GA in the status bar, there is a very high chance the code isn't working. Do you see stats in GA at all?
You might want to try removing the "try/catch" around the GA code while you are testing, so if there's a JavaScript error at least you will know about it.
The company says
this answers the question
-
Inappropriate?Yes that's what surprised me. I am seeing GA stats bu they are 6 times lower than that of clicky!. If I wouldn't be seeing GA stats at all, I would understand more, but do you have some idea as to why is there a partial execution of the code at times?
Web developer is detecting JS of GA though. Thanks so much for replying!
I’m feeling better
1 Comment Add a comment
This answers the question
-
I think I've seen somewhere there was some conflicts between Clicky or ClickTale and GA, not sure (you might want to search for that on Google). Make sure to remove the "catch/try" from there while you debug... Use something like Firebug to see if there are any errors, etc. At this point, it's not a WASP bug and if you need more help I'll be glad to look into it as part of my consulting practice.
EMPLOYEE
