Check for Google Analytics Using MooTools 1.2

By  on  

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.

Recent Features

  • By
    JavaScript Promise API

    While synchronous code is easier to follow and debug, async is generally better for performance and flexibility. Why "hold up the show" when you can trigger numerous requests at once and then handle them when each is ready?  Promises are becoming a big part of the JavaScript world...

  • By
    5 Ways that CSS and JavaScript Interact That You May Not Know About

    CSS and JavaScript:  the lines seemingly get blurred by each browser release.  They have always done a very different job but in the end they are both front-end technologies so they need do need to work closely.  We have our .js files and our .css, but...

Incredible Demos

  • By
    CSS Sprites

    The idea of CSS sprites is pretty genius. For those of you who don't know the idea of a sprite, a sprite is basically multiple graphics compiled into one image. The advantages of using sprites are: Fewer images for the browser to download, which means...

  • By
    Sliding Labels Using MooTools

    A week back I saw a great effect created by CSSKarma: input labels being animated horizontally. The idea is everything positive: elegant, practical, unobtrusive, and requires very little jQuery code. Luckily the effect doesn't require much MooTools code either! The HTML A...

Discussion

  1. Jeff Hartman

    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!

  2. @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.

  3. @Jeff: Simply put….I was lazy with my own site and paid the price for it.

  4. 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.

  5. @Sameer: Very true!

  6. 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.

  7. 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?

Wrap your code in <pre class="{language}"></pre> tags, link to a GitHub gist, JSFiddle fiddle, or CodePen pen to embed!