Secure (SSL) Google Analytics

By  on  

Google Analytics is a tremendous tool, especially when your customer wants an eCommerce website. Analytics is even more powerful when your customer uses Adwords to drive in traffic.

Google provides the following code for you to add to your page footer so that Analytics can grab statistics:


The problem with this is that if you're pulling this code in on a secure page, a security warning will pop up mentioning that the page is loading both secure and non-secure items. How do you prevent this issue (as well as trust issues with the user)? Simply import the secure version of Google Analytics:


For websites that have some pages secure and others not HTTPS protected, I recommend always calling the secure version of Google Analytics' urchin.js.

Recent Features

  • By
    Creating Scrolling Parallax Effects with CSS

    Introduction For quite a long time now websites with the so called "parallax" effect have been really popular. In case you have not heard of this effect, it basically includes different layers of images that are moving in different directions or with different speed. This leads to a...

  • By
    Being a Dev Dad

    I get asked loads of questions every day but I'm always surprised that they're rarely questions about code or even tech -- many of the questions I get are more about non-dev stuff like what my office is like, what software I use, and oftentimes...

Incredible Demos

  • By
    jQuery Chosen Plugin

    Without a doubt, my least favorite form element is the SELECT element.  The element is almost unstylable, looks different across platforms, has had inconsistent value access, and disaster that is the result of multiple=true is, well, a disaster.  Needless to say, whenever a developer goes...

  • By
    dat.gui:  Exceptional JavaScript Interface Controller

    We all love trusted JavaScript frameworks like MooTools, jQuery, and Dojo, but there's a big push toward using focused micro-frameworks for smaller purposes. Of course, there are positives and negatives to using them.  Positives include smaller JS footprint (especially good for mobile) and less cruft, negatives...

Discussion

  1. Nice post! Google Analytics has a new tracking code option, ga.js instead of the urchin.js, that handles the ssl component. Here’s a look:

    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("UA-xxxxxxx-x");
    pageTracker._initData();
    pageTracker._trackPageview();
    
    
  2. muddy

    The answer to my ssl headaches! Didn’t think to check if Google Analytics offered a secure tracking code. Will be so happy to say goodbye to that annoying “non-secure” pop-up.

    Thank ya thank ya thank ya.

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