<?xml version="1.0"  encoding="utf-8"?>
	<feed xmlns="http://www.w3.org/2005/Atom">
		<title>Comments to Google Analytics&#039; Security Warnings</title>
		<link href="http://www.practicalecommerce.com/atom/article/406/" rel="self"/>
  	<updated>2008-06-03T09:51:58-07:00</updated>
		<author>
  	  <name>Practical Ecommerce</name>
			<email>info@practicalecommerce.com</email>
  	</author>
  	<id>http://www.practicalecommerce.com/</id>
		<rights>Copyright 2007 Confluence Publishing DBA Practical Ecommerce</rights>
		<entry>
			<title>hatch</title>
			<link href="http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment12500" rel="alternate"/>
			<id>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment12500</id>
			<updated>2008-06-03T09:51:58-07:00</updated>
			<summary>If you have a common footer for all your pages, you can use javascript to dynamically sense the protocol (http: or https:) and switch to the proper include file:


var gaJsHost = ((&quot;https:&quot; == document.location.protocol) ? &quot;https://ssl.&quot; : &quot;http://www.&quot;);
document.write(unescape(&quot;%3Cscript src=&#039;&quot; + gaJsHost + &quot;google-analytics.com/ga.js&#039; type=&#039;text/javascript&#039;%3E%3C/script%3E&quot;));

</summary>
			</entry>
			
				<entry>
			<title>Sergiy Lavryk</title>
			<link href="http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment8355" rel="alternate"/>
			<id>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment8355</id>
			<updated>2008-04-02T21:14:07-07:00</updated>
			<summary>http://www.google.com/support/analytics/bin/answer.py?hl=en&amp;answer=55483</summary>
			</entry>
			
				<entry>
			<title>John</title>
			<link href="http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment4322" rel="alternate"/>
			<id>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment4322</id>
			<updated>2007-12-07T15:46:51-07:00</updated>
			<summary>Mel&#039;s response above worked!!!

Change the reference to the javascript include from &quot;http://www.&quot; to &quot;https://ssl.&quot;

</summary>
			</entry>
			
				<entry>
			<title>Lalit Mehta</title>
			<link href="http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment3468" rel="alternate"/>
			<id>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment3468</id>
			<updated>2007-08-16T14:22:21-07:00</updated>
			<summary>I don&#039;t know if this is new, but when you add the website for Google Analytics, you can select whether your website is http:// or https://

You get the correct js code to add depending on what you select.</summary>
			</entry>
			
				<entry>
			<title>rod</title>
			<link href="http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment3399" rel="alternate"/>
			<id>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment3399</id>
			<updated>2007-07-31T10:54:24-07:00</updated>
			<summary>After I changed my website url to https and got the ssl script... Do I have to change it into original form (http://) or leave it as it is?

</summary>
			</entry>
			
				<entry>
			<title>Pete</title>
			<link href="http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment2992" rel="alternate"/>
			<id>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment2992</id>
			<updated>2007-06-05T02:08:45-07:00</updated>
			<summary>Once you have signed into google analytics go to the  http://www.google.com/support/analytics/bin/answer.py?answer=31846&amp;topic=7175 page</summary>
			</entry>
			
				<entry>
			<title>Mel</title>
			<link href="http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment1100" rel="alternate"/>
			<id>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment1100</id>
			<updated>2007-04-05T15:15:59-07:00</updated>
			<summary>From the Analytics support page, this is the proper solution:

change &quot;http://www&quot; to &quot;https://ssl&quot;</summary>
			</entry>
			
				<entry>
			<title>Mel</title>
			<link href="http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment1099" rel="alternate"/>
			<id>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment1099</id>
			<updated>2007-04-05T15:08:55-07:00</updated>
			<summary>Both these solutions lead to a JavaScript error for me.</summary>
			</entry>
			
				<entry>
			<title>Ryan</title>
			<link href="http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment263" rel="alternate"/>
			<id>http://www.practicalecommerce.com/articles/406/Google-Analytics-Security-Warnings/#comment263</id>
			<updated>2007-02-08T08:34:30-07:00</updated>
			<summary>Just change the reference to the script to &quot;//{url}&quot; instead of &quot;http://{url}&quot; and youre set for both http and https pages...</summary>
			</entry>
			
				
	</feed>