<?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: Omniture SiteCatalyst Variables 101</title>
	<atom:link href="http://jebstone.com/2009/10/omniture-sitecatalyst-variables-101/feed/" rel="self" type="application/rss+xml" />
	<link>http://jebstone.com/2009/10/omniture-sitecatalyst-variables-101/</link>
	<description>Observation, commentary, and helpful hints at the intersection of web analytics and social science</description>
	<lastBuildDate>Fri, 06 Aug 2010 21:21:48 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: jebstone</title>
		<link>http://jebstone.com/2009/10/omniture-sitecatalyst-variables-101/comment-page-1/#comment-28</link>
		<dc:creator>jebstone</dc:creator>
		<pubDate>Sat, 03 Apr 2010 14:41:10 +0000</pubDate>
		<guid isPermaLink="false">http://jebstone.com/?p=22#comment-28</guid>
		<description>Just a note: Since sProps are page-level dimensions and success events are session-level measures, you can&#039;t break down your success events by sProp.  That&#039;s what Conversion eVars are for -- and that&#039;s why your list of sProps and eVars should usually be very similar: you want to be able to break down visits/page views and your key success events by the same variables.</description>
		<content:encoded><![CDATA[<p>Just a note: Since sProps are page-level dimensions and success events are session-level measures, you can&#8217;t break down your success events by sProp.  That&#8217;s what Conversion eVars are for &#8212; and that&#8217;s why your list of sProps and eVars should usually be very similar: you want to be able to break down visits/page views and your key success events by the same variables.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
