Does anyone use Google-Analytics to track the DNN usage?

Does anyone have a suggestion on how to configure my DNN Portal to leverage Google Analytics?  I added the necessary script on the default.aspx page and things seem to work okay as long as I don't switch over to SSL during the login process.  I noticed that when a user gets to the login page they are informed that not all of the data is using SSL (http://www.google-analytics.com/urchin.js).  I tried to simply change the call to goole to always use Https but the name of the certificate is google.com and the link I need is google-analytics, thus causing a challenge to the user...

By the way, the way I make SSL work for my site is using an auto-switching script found in these forums...

<script type="text/javascript">
    if(location.protocol.toLowerCase() =='http:' &&
        location.href.toLowerCase().indexOf('login') > -1 ) 
             location.href = location.href.replace('http:','https:');

    if(location.protocol.toLowerCase() =='https:' &&
         location.href.toLowerCase().indexOf('login') == -1 )
             location.href = location.href.replace('https:','http:');
</script >

I encapsulate the Google Analytics urchin.js in an ASP.NET custom control that gets used on each page...and it in turn determines whether the protocol prefix should be HTTP:// or HTTPS://.   This somewhat simplifies the process.  With respect to SSL support...

SSLRedirect is an excellent add-on for SSL securing DNN web pages.  SSLRedirect provides the flexibility of using Regular Expressions to define which web pages should be SSL secured.  SSLRedirect also provides an output filtering feature which assists in eliminating the mixed content message sometimes received when flowing from HTTP to HTTPS web pages.  SSLRedirect is the ONE SSL enabling component which works equally as well with native ASP.NET apps as with DNN apps.  SSLRedirect also works with single domain SSL Certificates or wildcard SSL Certificates.

CLICK HERE  to review a product brief.

CLICK HERE  to download product documentation.

You can put the https:// google analytics on every page if you want. Technically that is ok, but it may hurt performance.

You could also copy your skin, and put the secure GA code in one, and the non-secure in the other, then apply the SSL skin to your SSL pages.