<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: 1 million rows and SAINT still wants more</title>
	<atom:link href="http://www.elephantsandanalytics.com.au/blogposts/1-million-rows-and-saint-still-wants-more/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.elephantsandanalytics.com.au/blogposts/1-million-rows-and-saint-still-wants-more/</link>
	<description>&#34;Elephant in the corner&#34; is an English idiom for an obvious truth that is being ignored or goes unaddressed.</description>
	<lastBuildDate>Wed, 02 May 2012 02:59:10 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: What are our members doing? &#124; Elephants and Analytics</title>
		<link>http://www.elephantsandanalytics.com.au/blogposts/1-million-rows-and-saint-still-wants-more/comment-page-1/#comment-620</link>
		<dc:creator>What are our members doing? &#124; Elephants and Analytics</dc:creator>
		<pubDate>Wed, 17 Aug 2011 15:47:22 +0000</pubDate>
		<guid isPermaLink="false">http://www.elephantsandanalytics.com.au/blogposts/1-million-rows-and-saint-still-wants-more/#comment-620</guid>
		<description>[...] additional business segments, using extracts from your customer database.&#160; Take a look at 1 million rows and it still wants more, for an understanding of how that [...]</description>
		<content:encoded><![CDATA[<p>[...] additional business segments, using extracts from your customer database.&#160; Take a look at 1 million rows and it still wants more, for an understanding of how that [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Elleston</title>
		<link>http://www.elephantsandanalytics.com.au/blogposts/1-million-rows-and-saint-still-wants-more/comment-page-1/#comment-601</link>
		<dc:creator>Tim Elleston</dc:creator>
		<pubDate>Thu, 07 Jul 2011 12:23:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.elephantsandanalytics.com.au/blogposts/1-million-rows-and-saint-still-wants-more/#comment-601</guid>
		<description>Thanks Dan and Harini.  Yes, I think it&#039;s very underused...and it&#039;s so flexible.  One of the greatest things is the fact it&#039;s retroactive...don&#039;t like what it&#039;s showing, or changed your hierarchy, or need to add/edit/delete a column of data and apply back to the beginning...then SAINT&#039;s the way to go.  

And you can not only classify conversion eVars, but you can also classify traffic props too.  So for instance, keywords is a favorite to classify into Branded or Non Branded terms, so that you can aggregate them all together; Percent of Page viewed is best done with classifications on the prop, classified in buckets (1-25%, 26-50% etc).

Of course Visitor Scoring also utilizes SAINT classifications, again into buckets where the engagement score is classified.

If you use the VISTA Unified Traffic Sources rule, that&#039;s another classification that goes (typically) into your Campaign SAINT file.

And, one the great things using the FTP Import is that you can import SAINT files across multiple report suites, without having to manage them separately.  This is a real bonus, especially if you have lots of report suites that all use the same classifications.</description>
		<content:encoded><![CDATA[<p>Thanks Dan and Harini.  Yes, I think it&#8217;s very underused&#8230;and it&#8217;s so flexible.  One of the greatest things is the fact it&#8217;s retroactive&#8230;don&#8217;t like what it&#8217;s showing, or changed your hierarchy, or need to add/edit/delete a column of data and apply back to the beginning&#8230;then SAINT&#8217;s the way to go.  </p>
<p>And you can not only classify conversion eVars, but you can also classify traffic props too.  So for instance, keywords is a favorite to classify into Branded or Non Branded terms, so that you can aggregate them all together; Percent of Page viewed is best done with classifications on the prop, classified in buckets (1-25%, 26-50% etc).</p>
<p>Of course Visitor Scoring also utilizes SAINT classifications, again into buckets where the engagement score is classified.</p>
<p>If you use the VISTA Unified Traffic Sources rule, that&#8217;s another classification that goes (typically) into your Campaign SAINT file.</p>
<p>And, one the great things using the FTP Import is that you can import SAINT files across multiple report suites, without having to manage them separately.  This is a real bonus, especially if you have lots of report suites that all use the same classifications.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Harini</title>
		<link>http://www.elephantsandanalytics.com.au/blogposts/1-million-rows-and-saint-still-wants-more/comment-page-1/#comment-600</link>
		<dc:creator>Harini</dc:creator>
		<pubDate>Thu, 07 Jul 2011 06:02:40 +0000</pubDate>
		<guid isPermaLink="false">http://www.elephantsandanalytics.com.au/blogposts/1-million-rows-and-saint-still-wants-more/#comment-600</guid>
		<description>Tim

Great article. SAINT is such an under utilized feature for most Omniture implementations. Your article really simplifies the process at the same time driving the value of segmentation.

@Dan, incidentally there is &lt;b&gt;no cost&lt;/b&gt; associated with SAINT. Its out of the box, ready to enhance the value of your data. Its retrospective and completely flexible if you want to change the information in the META DATA.</description>
		<content:encoded><![CDATA[<p>Tim</p>
<p>Great article. SAINT is such an under utilized feature for most Omniture implementations. Your article really simplifies the process at the same time driving the value of segmentation.</p>
<p>@Dan, incidentally there is <b>no cost</b> associated with SAINT. Its out of the box, ready to enhance the value of your data. Its retrospective and completely flexible if you want to change the information in the META DATA.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dan Grainger</title>
		<link>http://www.elephantsandanalytics.com.au/blogposts/1-million-rows-and-saint-still-wants-more/comment-page-1/#comment-599</link>
		<dc:creator>Dan Grainger</dc:creator>
		<pubDate>Wed, 06 Jul 2011 20:55:11 +0000</pubDate>
		<guid isPermaLink="false">http://www.elephantsandanalytics.com.au/blogposts/1-million-rows-and-saint-still-wants-more/#comment-599</guid>
		<description>I&#039;ll be doing this I&#039;m sure....but the question of associated cost springs to mind. I know contracts with Adobe Omniture generally run on a server call basis, but how would a massive data import such as this be costed in your contract?</description>
		<content:encoded><![CDATA[<p>I&#8217;ll be doing this I&#8217;m sure&#8230;.but the question of associated cost springs to mind. I know contracts with Adobe Omniture generally run on a server call basis, but how would a massive data import such as this be costed in your contract?</p>
]]></content:encoded>
	</item>
</channel>
</rss>

