<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/2.0.4" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments for Willeitner Blog</title>
	<link>http://www.willeitner.org?tid=commentsrss2feed</link>
	<description>Internet Marketing Insights</description>
	<pubDate>Mon, 06 Sep 2010 17:13:56 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.0.4</generator>

	<item>
		<title>Comment on Where Does Google&#8217;s Name Come From? by Joyce Alcantara</title>
		<link>http://www.willeitner.org/2007/01/23/where-does-googles-name-come-from/#comment-9312?tid=commentsrss2feed</link>
		<pubDate>Fri, 09 Jan 2009 01:37:28 +0000</pubDate>
		<guid>http://www.willeitner.org/2007/01/23/where-does-googles-name-come-from/#comment-9312?tid=commentsrss2feed</guid>
					<description>that is kinda cool.. i never knew about it before.. lol..</description>
		<content:encoded><![CDATA[<p>that is kinda cool.. i never knew about it before.. lol..
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Tracking With First-Party Cookies by Kevin</title>
		<link>http://www.willeitner.org/2008/08/21/tracking-with-first-party-cookies/#comment-7158?tid=commentsrss2feed</link>
		<pubDate>Fri, 22 Aug 2008 19:10:35 +0000</pubDate>
		<guid>http://www.willeitner.org/2008/08/21/tracking-with-first-party-cookies/#comment-7158?tid=commentsrss2feed</guid>
					<description>You bring up a good point about friendly third-party cookies. If you just have a single domain then you will almost always want to go with first-party cookies because of the higher acceptance rate. However, if you have multiple domains and you want to share a common visitor id then friendly third-party cookies are very useful. They are friendly because they are likely not a well known tracking domain and if the user is familiar with your other sites then then they may welcome it. With a friendly third-party cookie you can have all of your individual domains combine into a global report suite and the visitor id will be consistent for a visitor even if they move across domains. If you don't have a global suite or you don't care about looking at a visitor across sites or spending the money for the SSL certificate for each domain isn't a problem then going with a first-party cookie is the way to go.</description>
		<content:encoded><![CDATA[<p>You bring up a good point about friendly third-party cookies. If you just have a single domain then you will almost always want to go with first-party cookies because of the higher acceptance rate. However, if you have multiple domains and you want to share a common visitor id then friendly third-party cookies are very useful. They are friendly because they are likely not a well known tracking domain and if the user is familiar with your other sites then then they may welcome it. With a friendly third-party cookie you can have all of your individual domains combine into a global report suite and the visitor id will be consistent for a visitor even if they move across domains. If you don&#8217;t have a global suite or you don&#8217;t care about looking at a visitor across sites or spending the money for the SSL certificate for each domain isn&#8217;t a problem then going with a first-party cookie is the way to go.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Tracking With First-Party Cookies by Ted McDonald</title>
		<link>http://www.willeitner.org/2008/08/21/tracking-with-first-party-cookies/#comment-7157?tid=commentsrss2feed</link>
		<pubDate>Fri, 22 Aug 2008 17:40:55 +0000</pubDate>
		<guid>http://www.willeitner.org/2008/08/21/tracking-with-first-party-cookies/#comment-7157?tid=commentsrss2feed</guid>
					<description>Indeed - I have consultants from both Omniture and other companies tell us to move to a first-party cookie. The wheels were in motion until I found this tidbit in Omniture's knowledge base the other day:

Friendly Third-Party Cookies for Multi-Suite Tagging Implementations

In certain situations, you may have a report suite that spans several of your domains. In this situation, Omniture recommends using a friendly third-party approach. The friendly third-party approach calls for a cookie that is set on a single "metrics collection subdomain" that has a friendly name.

Consider the scenario in which a hypothetical media conglomerate named NewsNow, Inc. owns ten different domains. To ensure accurate data collection, NewsNow would set its friendly third-party cookie to omn.newsnow.com. The benefit to this approach is that NewsNow could continue to have insight into the global view of all of their domains (e.g. de-duplicated visits, de-duplicated visitors, cross-domain campaign tracking, et cetera) by utilizing the cross-domain functionality that third-party cookies satisfy.

We use multi-suite tagging and multiple domains (okay...dozens), so I'm now waiting to hear back from Omniture Support on next steps to take.</description>
		<content:encoded><![CDATA[<p>Indeed - I have consultants from both Omniture and other companies tell us to move to a first-party cookie. The wheels were in motion until I found this tidbit in Omniture&#8217;s knowledge base the other day:</p>
<p>Friendly Third-Party Cookies for Multi-Suite Tagging Implementations</p>
<p>In certain situations, you may have a report suite that spans several of your domains. In this situation, Omniture recommends using a friendly third-party approach. The friendly third-party approach calls for a cookie that is set on a single &#8220;metrics collection subdomain&#8221; that has a friendly name.</p>
<p>Consider the scenario in which a hypothetical media conglomerate named NewsNow, Inc. owns ten different domains. To ensure accurate data collection, NewsNow would set its friendly third-party cookie to omn.newsnow.com. The benefit to this approach is that NewsNow could continue to have insight into the global view of all of their domains (e.g. de-duplicated visits, de-duplicated visitors, cross-domain campaign tracking, et cetera) by utilizing the cross-domain functionality that third-party cookies satisfy.</p>
<p>We use multi-suite tagging and multiple domains (okay&#8230;dozens), so I&#8217;m now waiting to hear back from Omniture Support on next steps to take.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Automatic Sort by Friar</title>
		<link>http://www.willeitner.org/2007/05/21/automatic-sort/#comment-5344?tid=commentsrss2feed</link>
		<pubDate>Sun, 30 Dec 2007 01:31:25 +0000</pubDate>
		<guid>http://www.willeitner.org/2007/05/21/automatic-sort/#comment-5344?tid=commentsrss2feed</guid>
					<description>Hello
Nice work well done
I am facing the same problem as Mike Lescai
Any news????</description>
		<content:encoded><![CDATA[<p>Hello<br />
Nice work well done<br />
I am facing the same problem as Mike Lescai<br />
Any news????
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Munich Lion by Dave Ash</title>
		<link>http://www.willeitner.org/2006/08/14/munich-lion/#comment-5277?tid=commentsrss2feed</link>
		<pubDate>Sat, 15 Dec 2007 09:32:54 +0000</pubDate>
		<guid>http://www.willeitner.org/2006/08/14/munich-lion/#comment-5277?tid=commentsrss2feed</guid>
					<description>Lovely picture. It is one of two lions actually situated at one of the most famous squares in Munich. The Odeanplatz is the square where all SS soilders swore loyalty to Hitler and was also the scene of the famous Munich Pursh where Hitler led the revolution which started the Nazi Pary. Several men were killed and a plaque to comemorate the event actually lies in the pavement just in front of the left hand lion.</description>
		<content:encoded><![CDATA[<p>Lovely picture. It is one of two lions actually situated at one of the most famous squares in Munich. The Odeanplatz is the square where all SS soilders swore loyalty to Hitler and was also the scene of the famous Munich Pursh where Hitler led the revolution which started the Nazi Pary. Several men were killed and a plaque to comemorate the event actually lies in the pavement just in front of the left hand lion.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Comparing BlueHost and HostMonster by walter</title>
		<link>http://www.willeitner.org/2006/10/05/comapring-bluehost-and-hostmonster/#comment-4286?tid=commentsrss2feed</link>
		<pubDate>Thu, 16 Aug 2007 18:50:43 +0000</pubDate>
		<guid>http://www.willeitner.org/2006/10/05/comapring-bluehost-and-hostmonster/#comment-4286?tid=commentsrss2feed</guid>
					<description>nothing is worse than hostingplex.  i'm trying to switch but i think they blocked my phone number.  my account has been suspended for 3 days now and no one seems to know how to fix it</description>
		<content:encoded><![CDATA[<p>nothing is worse than hostingplex.  i&#8217;m trying to switch but i think they blocked my phone number.  my account has been suspended for 3 days now and no one seems to know how to fix it
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Automatic Sort by Mike Lescai</title>
		<link>http://www.willeitner.org/2007/05/21/automatic-sort/#comment-3962?tid=commentsrss2feed</link>
		<pubDate>Sat, 21 Jul 2007 00:38:46 +0000</pubDate>
		<guid>http://www.willeitner.org/2007/05/21/automatic-sort/#comment-3962?tid=commentsrss2feed</guid>
					<description>Tried to do the multiple column sort but struck a problem when using [lookup value] where there were 2 or more of the same value. With a match type of 0 I get the first lookup value. I'm working on it.</description>
		<content:encoded><![CDATA[<p>Tried to do the multiple column sort but struck a problem when using [lookup value] where there were 2 or more of the same value. With a match type of 0 I get the first lookup value. I&#8217;m working on it.
</p>
]]></content:encoded>
				</item>
	<item>
		<title>Comment on Automatic Sort by Mike Lescai</title>
		<link>http://www.willeitner.org/2007/05/21/automatic-sort/#comment-3961?tid=commentsrss2feed</link>
		<pubDate>Fri, 20 Jul 2007 23:33:21 +0000</pubDate>
		<guid>http://www.willeitner.org/2007/05/21/automatic-sort/#comment-3961?tid=commentsrss2feed</guid>
					<description>This was a sensational tip. Many Thanks!</description>
		<content:encoded><![CDATA[<p>This was a sensational tip. Many Thanks!
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
