<?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: Back to basics &#8211; props, eVars and events</title>
	<atom:link href="http://www.elephantsandanalytics.com.au/blogposts/back-to-basics-props-evars-and-events/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.elephantsandanalytics.com.au/blogposts/back-to-basics-props-evars-and-events/</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: Tim Elleston</title>
		<link>http://www.elephantsandanalytics.com.au/blogposts/back-to-basics-props-evars-and-events/comment-page-1/#comment-1307</link>
		<dc:creator>Tim Elleston</dc:creator>
		<pubDate>Mon, 16 Apr 2012 10:57:24 +0000</pubDate>
		<guid isPermaLink="false">http://www.elephantsandanalytics.com.au/?p=437#comment-1307</guid>
		<description>Hey Neha
Best thing for you to do is to set an eVar with the value of the pageName before setting the event and firing s.tl() - that way you should be able to apply the success event to the evar properly to see the correct values.  I&#039;m assuming that you want to see which pages were &quot;liked&quot; by your audiences...  Don&#039;t forget to set s.linkTrackVars and s.linkTrackEvents during the onClick - check out page 104 of the implementation guide as it has specific info on this type of measurement.

In terms of the buttons and add to cart question - when success events are applied across the Pages report, they are done so using linear allocation, which is why you&#039;re getting data applied to those pages even though there is no ability to purchase from those pages - the purchase is still being &quot;attributed&quot; to those pages.

Hope that helps.
Tim</description>
		<content:encoded><![CDATA[<p>Hey Neha<br />
Best thing for you to do is to set an eVar with the value of the pageName before setting the event and firing s.tl() &#8211; that way you should be able to apply the success event to the evar properly to see the correct values.  I&#8217;m assuming that you want to see which pages were &#8220;liked&#8221; by your audiences&#8230;  Don&#8217;t forget to set s.linkTrackVars and s.linkTrackEvents during the onClick &#8211; check out page 104 of the implementation guide as it has specific info on this type of measurement.</p>
<p>In terms of the buttons and add to cart question &#8211; when success events are applied across the Pages report, they are done so using linear allocation, which is why you&#8217;re getting data applied to those pages even though there is no ability to purchase from those pages &#8211; the purchase is still being &#8220;attributed&#8221; to those pages.</p>
<p>Hope that helps.<br />
Tim</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Neha</title>
		<link>http://www.elephantsandanalytics.com.au/blogposts/back-to-basics-props-evars-and-events/comment-page-1/#comment-1305</link>
		<dc:creator>Neha</dc:creator>
		<pubDate>Sat, 14 Apr 2012 08:41:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.elephantsandanalytics.com.au/?p=437#comment-1305</guid>
		<description>Hi Tim, 

I have a question about Success events.  When I an event in a javascript function that is called by the onClick trigger . And i record the event using s.tl() and not s.t(). Do I need to set  s.pageName again inside the function to know what page the button was clicked on? 
For example, if i have a &quot;Like&quot; button on my website. i will set
s.events = event16  (assuming event16 is set for like by admin)

now do i need to set s.pageName = My article ?  along with event16? or will the event be tied to the pagename set when the pagename was loaded? 

I ask this because my javascript events seem to be reported for pages that don&#039;t contain those buttons, i have no idea how &#039;add to cart&#039; can happen on the homepage when there is no add to cart button on our homepage.</description>
		<content:encoded><![CDATA[<p>Hi Tim, </p>
<p>I have a question about Success events.  When I an event in a javascript function that is called by the onClick trigger . And i record the event using s.tl() and not s.t(). Do I need to set  s.pageName again inside the function to know what page the button was clicked on?<br />
For example, if i have a &#8220;Like&#8221; button on my website. i will set<br />
s.events = event16  (assuming event16 is set for like by admin)</p>
<p>now do i need to set s.pageName = My article ?  along with event16? or will the event be tied to the pagename set when the pagename was loaded? </p>
<p>I ask this because my javascript events seem to be reported for pages that don&#8217;t contain those buttons, i have no idea how &#8216;add to cart&#8217; can happen on the homepage when there is no add to cart button on our homepage.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phlebotomy Certification</title>
		<link>http://www.elephantsandanalytics.com.au/blogposts/back-to-basics-props-evars-and-events/comment-page-1/#comment-546</link>
		<dc:creator>Phlebotomy Certification</dc:creator>
		<pubDate>Wed, 19 Jan 2011 17:35:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.elephantsandanalytics.com.au/?p=437#comment-546</guid>
		<description>found your site on del.icio.us today and really liked it.. i bookmarked it and will be back to check it out some more later</description>
		<content:encoded><![CDATA[<p>found your site on del.icio.us today and really liked it.. i bookmarked it and will be back to check it out some more later</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gilberto Mayzes</title>
		<link>http://www.elephantsandanalytics.com.au/blogposts/back-to-basics-props-evars-and-events/comment-page-1/#comment-543</link>
		<dc:creator>Gilberto Mayzes</dc:creator>
		<pubDate>Mon, 17 Jan 2011 12:48:23 +0000</pubDate>
		<guid isPermaLink="false">http://www.elephantsandanalytics.com.au/?p=437#comment-543</guid>
		<description>I’ve read some good stuff here. Definitely worth bookmarking for revisiting.</description>
		<content:encoded><![CDATA[<p>I’ve read some good stuff here. Definitely worth bookmarking for revisiting.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Elleston</title>
		<link>http://www.elephantsandanalytics.com.au/blogposts/back-to-basics-props-evars-and-events/comment-page-1/#comment-540</link>
		<dc:creator>Tim Elleston</dc:creator>
		<pubDate>Wed, 12 Jan 2011 12:54:36 +0000</pubDate>
		<guid isPermaLink="false">http://www.elephantsandanalytics.com.au/?p=437#comment-540</guid>
		<description>The next post describes value from s.props, using them for &lt;a href=&quot;http://www.elephantsandanalytics.com.au/blogposts/enabling-customer-segmentation/&quot; rel=&quot;nofollow&quot;&gt;segmentation purposes&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>The next post describes value from s.props, using them for <a href="http://www.elephantsandanalytics.com.au/blogposts/enabling-customer-segmentation/" rel="nofollow">segmentation purposes</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tim Elleston</title>
		<link>http://www.elephantsandanalytics.com.au/blogposts/back-to-basics-props-evars-and-events/comment-page-1/#comment-527</link>
		<dc:creator>Tim Elleston</dc:creator>
		<pubDate>Mon, 27 Dec 2010 05:46:52 +0000</pubDate>
		<guid isPermaLink="false">http://www.elephantsandanalytics.com.au/?p=437#comment-527</guid>
		<description>Thanks for the comment Doug - I&#039;ll put a post together to show how props are useful.  

You are largely correct though, the majority of value comes from eVars and events.  You can however correlate props together, breaking one down by another.  They break down as a 1x1 or a 5x5 breakdown.  You&#039;ll need to set up the correlation in the admin section.  

The other thing you might want to look at is the hier1-5 variables if you&#039;re looking at drilldown reporting.  

Enabling pathing on props...there&#039;s a couple of interesting things you can get out of it.  If you are concatenating values together, such as User Type (customer, non customer) + page name into a prop, or campaign name + pagename, or keyword + pagename etc, and enable pathing on the prop, you can see where users go, and, more importantly sometime, adding pathing to props enables other key metrics on custom traffic variables.

So, I&#039;ll definitely put a post together about props... :)</description>
		<content:encoded><![CDATA[<p>Thanks for the comment Doug &#8211; I&#8217;ll put a post together to show how props are useful.  </p>
<p>You are largely correct though, the majority of value comes from eVars and events.  You can however correlate props together, breaking one down by another.  They break down as a 1&#215;1 or a 5&#215;5 breakdown.  You&#8217;ll need to set up the correlation in the admin section.  </p>
<p>The other thing you might want to look at is the hier1-5 variables if you&#8217;re looking at drilldown reporting.  </p>
<p>Enabling pathing on props&#8230;there&#8217;s a couple of interesting things you can get out of it.  If you are concatenating values together, such as User Type (customer, non customer) + page name into a prop, or campaign name + pagename, or keyword + pagename etc, and enable pathing on the prop, you can see where users go, and, more importantly sometime, adding pathing to props enables other key metrics on custom traffic variables.</p>
<p>So, I&#8217;ll definitely put a post together about props&#8230; <img src='http://www.elephantsandanalytics.com.au/wp-includes/images/smilies/icon_smile.gif' alt=':)' class='wp-smiley' /> </p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Doug</title>
		<link>http://www.elephantsandanalytics.com.au/blogposts/back-to-basics-props-evars-and-events/comment-page-1/#comment-526</link>
		<dc:creator>Doug</dc:creator>
		<pubDate>Sun, 26 Dec 2010 15:36:59 +0000</pubDate>
		<guid isPermaLink="false">http://www.elephantsandanalytics.com.au/?p=437#comment-526</guid>
		<description>See, the more I read about this, and the more I look at the omniture reports, the less enthusiastic I am about props.

Looking through your post it struck me again; why, in the absence of Discover, would you actually use props for anything at all? 

You can&#039;t correlate the information to anything, and you end up setting and eVar when you set a prop anyway for anything useful. You can&#039;t even breakdown props into a hierarchy (eg. sub-section must include section in the value, because section is completely independent to sub-section in reporting).

All you get is yet another page views style custom report. It&#039;s just as bad as link tracking.

Your diagram mentions enabling pathing for props; even then, surely only a handful of your props are useful (site sections, perhaps?)

I&#039;d be thrilled to see a blog post from you describing how props are actually useful...</description>
		<content:encoded><![CDATA[<p>See, the more I read about this, and the more I look at the omniture reports, the less enthusiastic I am about props.</p>
<p>Looking through your post it struck me again; why, in the absence of Discover, would you actually use props for anything at all? </p>
<p>You can&#8217;t correlate the information to anything, and you end up setting and eVar when you set a prop anyway for anything useful. You can&#8217;t even breakdown props into a hierarchy (eg. sub-section must include section in the value, because section is completely independent to sub-section in reporting).</p>
<p>All you get is yet another page views style custom report. It&#8217;s just as bad as link tracking.</p>
<p>Your diagram mentions enabling pathing for props; even then, surely only a handful of your props are useful (site sections, perhaps?)</p>
<p>I&#8217;d be thrilled to see a blog post from you describing how props are actually useful&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>

