Google Analytics on site with secure and non secure pages?

joer80 · #1 (**permalink**) 11-22-2005, 08:47 AM

I cant figure out how to add the google analytics counter to my secure and non secure pages under 1 site.

I can get the non secure code but if i put it on my secure pages it gives an error, and as far as i can see, to get secure code i have to create a different site which would kill my conversion numbers?? Can anyone help? I emailed the help section it offers but have not got a response.

Thanks!

**brian.mark** · #2 (**permalink**) 11-22-2005, 03:20 PM

The simple answer is to take your non-secure code and just make the reference to https://ssl.google-analytics.com/urchin.js instead of http://www.google-analytics.com/urchin.js for the secure pages. Other than that, the code is the same.

Brian.

joer80 · #3 (**permalink**) 11-23-2005, 01:27 PM

Thats what i thought but it gave a warning on my page when i changed it. I can try it again maybe?

Are you sure this works and there isnt a validation in the code that i pass to google?

If you have done this with success it would give me more hope for writing it off as a dumb mistake. :)

**brian.mark** · #4 (**permalink**) 11-23-2005, 01:41 PM

I've done this on www.toolpartsdirect.com and had no issues. When I changed it to https://www.google-analytics.com/urchin.js, that gave a warning. When I made it ssl.google-analytics.com that worked without the error. Just make sure you include the s in the protocol as well and you'll be good.

Brian.

Millenium · #5 (**permalink**) 11-26-2005, 01:04 AM

What I have found that works just as well is to remove the http// or https:// from the code altogether. The server or the browser will fetch the code in whatever the current state is. I've done it myself and it works just fine.

**brian.mark** · #6 (**permalink**) 11-26-2005, 11:27 PM

Quote:

Originally Posted by Millenium

What I have found that works just as well is to remove the http// or https:// from the code altogether. The server or the browser will fetch the code in whatever the current state is. I've done it myself and it works just fine.

The only issue is people with Macs. That has a tendency to crash their browser. It's always a good idea to use the protocol when specifying any sort of a link (JavaScript, image, href or otherwise).

Brian.

joer80 · #7 (**permalink**) 12-06-2005, 07:52 AM

Google suggested using the secure code on all pages. Anyone tried this?

**brian.mark** · #8 (**permalink**) 12-07-2005, 12:15 AM

That was one easy way to do things. Given the authentication path that SSL pages require, modem users don't get counted as accurately when using SSL for all pages. This is the reason we split it up.

Using the method I described above works flawless. I sure haven't had any issues with it.

Brian.