Comments on: Additional Methods To Measure Interaction Using The Get Time To Complete Plug-In http://webanalyticsland.com/sitecatalyst-implementation/additional-methods-to-measure-interaction-using-the-get-time-to-complete-plug-in/ Omniture SiteCatalyst Implementation Optimization. Fri, 20 Aug 2010 16:55:53 +0000 hourly 1 http://wordpress.org/?v=3.0.1 By: Loryn-Aimee http://webanalyticsland.com/sitecatalyst-implementation/additional-methods-to-measure-interaction-using-the-get-time-to-complete-plug-in/comment-page-1/#comment-156 Loryn-Aimee Sat, 15 May 2010 10:50:04 +0000 http://webanalyticsland.com/?p=284#comment-156 Thank you digdeep. I agree it's a great plugin, and would recommend adding a classification for time groupings to it to make for easier analysis where necessary. I've implemented this on an eCom site, measuring the difference between Cart Open and Checkout and again between Checkout and Purchase using different props and cookie names. if (s.events) { // Time to Build Cart if (s.events.match(/scOpen/i)) s.prop9='start'; if (s.events.match(/scCheckout/i)) s.prop9='stop'; s.prop9=s.getTimeToComplete(s.prop9,'ttbc',0); // Time to Check Out if (s.events.match(/scCheckout/i)) s.prop10='start'; if (s.events.match(/purchase/i)) s.prop10='stop'; s.prop10=s.getTimeToComplete(s.prop10,'ttco',0); } prop9 works, prop10 does not - only one value of "start" shows up. Does anything stand out to you? The only thing I can think of changing is the expiration (currently set to 0 as in your example) which leads me to the second point: I actually do want the number of days lapsed between the two events to show in cases where visitors took a number of days to build their cart including if their activity happened in different visits. Do you know which other values for expiration can be inserted in that 3rd parameter? Any light on this would help loads!! Thank you digdeep. I agree it’s a great plugin, and would recommend adding a classification for time groupings to it to make for easier analysis where necessary.

I’ve implemented this on an eCom site, measuring the difference between Cart Open and Checkout and again between Checkout and Purchase using different props and cookie names.

if (s.events) {
// Time to Build Cart
if (s.events.match(/scOpen/i)) s.prop9=’start’;
if (s.events.match(/scCheckout/i)) s.prop9=’stop’;
s.prop9=s.getTimeToComplete(s.prop9,’ttbc’,0);

// Time to Check Out
if (s.events.match(/scCheckout/i)) s.prop10=’start’;
if (s.events.match(/purchase/i)) s.prop10=’stop’;
s.prop10=s.getTimeToComplete(s.prop10,’ttco’,0);
}

prop9 works, prop10 does not – only one value of “start” shows up.
Does anything stand out to you?
The only thing I can think of changing is the expiration (currently set to 0 as in your example) which leads me to the second point:
I actually do want the number of days lapsed between the two events to show in cases where visitors took a number of days to build their cart including if their activity happened in different visits. Do you know which other values for expiration can be inserted in that 3rd parameter?

Any light on this would help loads!!

]]> By: VaBeachKevin http://webanalyticsland.com/sitecatalyst-implementation/additional-methods-to-measure-interaction-using-the-get-time-to-complete-plug-in/comment-page-1/#comment-122 VaBeachKevin Mon, 14 Dec 2009 05:01:34 +0000 http://webanalyticsland.com/?p=284#comment-122 The Counter eVar are designed for when you are trying to count the number actions a user takes before an event. For example, you may use an eVar to capture the number of internal searches before purchase. Each time a visitor searches, the eVar should contain a value of +1. If a visitor searches four times before a purchase, you will see an instance for each total count: 1.00, 2.00, 3.00 and 4.00. The Time To Complete plug-in however will return a time it took to get from one action to another. Using this plug-in if you check the debugger you will see something like: <img src="http://webanalyticsland.com/images/ttc.jpg" alt="Time To Complete Plugin Debugger" /> Check out Answer ID 1443 in the Omniture knowledge base for more information about using a Counter eVar. The Counter eVar are designed for when you are trying to count the number actions a user takes before an event. For example, you may use an eVar to capture the number of internal searches before purchase. Each time a visitor searches, the eVar should contain a value of +1. If a visitor searches four times before a purchase, you will see an instance for each total count: 1.00, 2.00, 3.00 and 4.00.

The Time To Complete plug-in however will return a time it took to get from one action to another. Using this plug-in if you check the debugger you will see something like:
Time To Complete Plugin Debugger

Check out Answer ID 1443 in the Omniture knowledge base for more information about using a Counter eVar.

]]> By: digdeep http://webanalyticsland.com/sitecatalyst-implementation/additional-methods-to-measure-interaction-using-the-get-time-to-complete-plug-in/comment-page-1/#comment-121 digdeep Mon, 14 Dec 2009 00:29:00 +0000 http://webanalyticsland.com/?p=284#comment-121 Sweet post, Waiting on my Omniture account manager to discuss something similar so perfect timing :) I thought counter evars served this purpose? what is the difference between the plug in vs counter evars? tks..n Sweet post,

Waiting on my Omniture account manager to discuss something similar so perfect timing :)

I thought counter evars served this purpose? what is the difference between the plug in vs counter evars?

tks..n

]]>