<?xml version="1.0" encoding="utf-8"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title>Brian Hawkin's Blog at Web Analytics Demystfiied.com - Latest Comments</title><link>http://brianhawkinsblogatwebanalyticsdemystfiiedcom.disqus.com/</link><description></description><atom:link href="https://brianhawkinsblogatwebanalyticsdemystfiiedcom.disqus.com/comments.rss" rel="self"></atom:link><language>en</language><lastBuildDate>Mon, 22 Oct 2012 22:22:12 -0000</lastBuildDate><item><title>Re: The T&amp;#038;T Plugin &amp;#8211; Integrate T&amp;#038;T with Google Analytics</title><link>http://brian.webanalyticsdemystified.com/2012/10/the-tt-plugin-integrate-tt-with-google-analytics.html#comment-689667433</link><description>&lt;p&gt;Thank you Yehoshua.  I really like your point on visitor custom variables.  I will update the post to include your example, like Tim's.  Thanks again!  &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bhawkins</dc:creator><pubDate>Mon, 22 Oct 2012 22:22:12 -0000</pubDate></item><item><title>Re: The T&amp;#038;T Plugin &amp;#8211; Integrate T&amp;#038;T with Google Analytics</title><link>http://brian.webanalyticsdemystified.com/2012/10/the-tt-plugin-integrate-tt-with-google-analytics.html#comment-689666473</link><description>&lt;p&gt;Thanks so much Tim.  Really appreciate you sharing your experiences with Optimizely.  I will be sure to update this post with examples on visit-level variables as I think that can certainly be helpful.  Also, very interesting use of non-interaction events!  &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bhawkins</dc:creator><pubDate>Mon, 22 Oct 2012 22:20:26 -0000</pubDate></item><item><title>Re: The T&amp;#038;T Plugin &amp;#8211; Integrate T&amp;#038;T with Google Analytics</title><link>http://brian.webanalyticsdemystified.com/2012/10/the-tt-plugin-integrate-tt-with-google-analytics.html#comment-689459771</link><description>&lt;p&gt;I share Tim's sentiment - very useful post.  One thing to add would be to assign a visitor level custom variable to the event.  This way conversions can be associated with a particular variation, even if the conversion happened during a different session where they didn't see a page with the T&amp;amp;T variation.  The custom variable key (name) can be Test&amp;amp;Target and the campaign name + recipe name concatenated for the value, or use campaign name for the CV key and recipe name for the value.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Yehoshua Coren</dc:creator><pubDate>Mon, 22 Oct 2012 16:59:11 -0000</pubDate></item><item><title>Re: The T&amp;#038;T Plugin &amp;#8211; Integrate T&amp;#038;T with Google Analytics</title><link>http://brian.webanalyticsdemystified.com/2012/10/the-tt-plugin-integrate-tt-with-google-analytics.html#comment-689101608</link><description>&lt;p&gt;Great post! I wish other testing platforms had this level of flexibility built-in -- having been doing some work with Optimizely, the GA integration is much easier/faster (one drop-down to select a custom variable slot to use)...but we also quickly ran into limitations when running multiple tests. In Optimizely's case, the test data gets pushed into a visit-level custom variable, which, using the informatio here, would be easy to do with T&amp;amp;T, too.&lt;/p&gt;&lt;p&gt;FWIW, I'd suggest using a non-interaction event in the T&amp;amp;T example in this post. It just requires the addition of ",,true" or ",1,true" to the trackEvent call. That way, you won't inadvertently muck with bounce rate data for visitors who landed on the page where the test is running and then bounced. &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Tim Wilson</dc:creator><pubDate>Mon, 22 Oct 2012 07:47:16 -0000</pubDate></item><item><title>Re: The T&amp;#038;T Plugin &amp;#8211; Integrate T&amp;#038;T with Google Analytics</title><link>http://brian.webanalyticsdemystified.com/2012/10/the-tt-plugin-integrate-tt-with-google-analytics.html#comment-689093784</link><description>&lt;p&gt;very cool!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Just another web analyst</dc:creator><pubDate>Mon, 22 Oct 2012 07:31:18 -0000</pubDate></item><item><title>Re: Optimization Test Techniques &amp;#8211; Part I of II</title><link>http://brian.webanalyticsdemystified.com/2012/04/optimization-test-techniques-part-i-of-ii.html#comment-603309882</link><description>&lt;p&gt;I really enjoy the opportunity to read abot how you view 'optimization" and your opinion is greatly appreciated.&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Gregory Smith</dc:creator><pubDate>Mon, 30 Jul 2012 15:06:32 -0000</pubDate></item><item><title>Re: Brian Hawkins, Demystified</title><link>http://brian.webanalyticsdemystified.com/2012/02/brian-hawkins-demystified.html#comment-450315816</link><description>&lt;p&gt;Thanks so much Chris.  Same here!  See you next week.  &lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">bhawkins</dc:creator><pubDate>Mon, 27 Feb 2012 17:54:37 -0000</pubDate></item><item><title>Re: Brian Hawkins, Demystified</title><link>http://brian.webanalyticsdemystified.com/2012/02/brian-hawkins-demystified.html#comment-450252187</link><description>&lt;p&gt;Congratulations Brian.  We look forward to working with you!&lt;/p&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Chris Olenik</dc:creator><pubDate>Mon, 27 Feb 2012 16:39:18 -0000</pubDate></item></channel></rss>