Check for Google Analytics Using MooTools 1.2
When I launched my new design last week, I used PHP to comment out Google Analytics because I didn't want to skew the stats. Well, I did skew my stats that day because I forgot to uncomment the damn GA code. Rook move, I know. With that in mind, I've created a MooTools script that checks to make sure Google Analytics is loaded. If not, you get a friendly JavaScript alert() reminder.
The MooTools 1.2 Code
window.addEvent('load', function() {
if(typeof(eval(window)['_ufsc']) == 'undefined') {
alert('David, turn on GA!');
}
});
Not having 10 hours worth of stats is a big deal. This code will (hopefully) prevent this from happening again in the future.
![7 Essential JavaScript Functions]()
I remember the early days of JavaScript where you needed a simple function for just about everything because the browser vendors implemented features differently, and not just edge features, basic features, like addEventListener and attachEvent. Times have changed but there are still a few functions each developer should...
![Detect DOM Node Insertions with JavaScript and CSS Animations]()
I work with an awesome cast of developers at Mozilla, and one of them in Daniel Buchner. Daniel's shared with me an awesome strategy for detecting when nodes have been injected into a parent node without using the deprecated DOM Events API.
![Drag and Drop Z-Index Stacking]()
![5 More HTML5 APIs You Didn’t Know Existed]()
The HTML5 revolution has provided us some awesome JavaScript and HTML APIs. Some are APIs we knew we've needed for years, others are cutting edge mobile and desktop helpers. Regardless of API strength or purpose, anything to help us better do our job is a...
Why aren’t you using the same if statement as you do for your config file as mentioned in a previous post?
http://davidwalsh.name/knowing-website-state-php
As a matter of fact, you commented on your own post saying you use it for Google Analytics!
@Jeff: Because I wasn’t developing locally, per say. I was dragging each file to my desktop, and then reuploading as I changed it. Again, not the best way of doing things.
I do, however, use my “website state” strategy at work.
@Jeff: Simply put….I was lazy with my own site and paid the price for it.
Works great unless you are the type to upload something and not confirm the changes (and then have all your visitors get the popup). Hey, if you can make one lazy mistake you can make another, haha.
@Sameer: Very true!
A much simpler and easier to manage solution is to set up a filter in google analytics itself.
For example, “exclude all traffic from user agents marked ‘website-tester.'” Then simply use Firefox’s user-agent switcher extension to use ‘website-tester’ whilst testing.
This also allows more flexibility than the “website state” strategy as PHP, Google Analytics etc… can be clever about your own use of the site for testing purposes even on a website that is live and working for everybody else.
Obviously the website state idea still has validity when when you have two near identical sites, one for production and the other live. As an example my platform generates a robots.txt automatically and on the staging site adds the “Disallow: /” directive to prevent the staging site from being indexed and all those duplicate content issues.
Hey David, this post is a few years old now and it still works! :D but have you come across any new ways of detecting Google Analytics?