Comments on: A New User Experience, Part 1 (of 5): Introduction to Tag Builder 3.0 http://blogs.webtrends.com/blog/2009/03/31/a-new-user-experience-part-1-of-5-introduction-to-tag-builder-30/ We strongly considered calling it The Weblog Thu, 19 Nov 2009 20:07:52 -0800 http://wordpress.org/?v=2.8.4 hourly 1 By: Bryan Cristina http://blogs.webtrends.com/blog/2009/03/31/a-new-user-experience-part-1-of-5-introduction-to-tag-builder-30/comment-page-1/#comment-213 Bryan Cristina Fri, 03 Apr 2009 19:06:08 +0000 http://blog.webtrends.com/?p=1516#comment-213 Thanks for the clarification, Eric. Maybe it would be a good idea to show an example string of what a CORRECT implementation of WebTrends code should be sending back to the WebTrends server with the GET .gif command. I see what's in there (the dcsuri, dcssip, tz, vtid, etc) but I'm not sure everything that should be in there is either there or in the correct format. Thanks for the clarification, Eric.

Maybe it would be a good idea to show an example string of what a CORRECT implementation of WebTrends code should be sending back to the WebTrends server with the GET .gif command. I see what’s in there (the dcsuri, dcssip, tz, vtid, etc) but I’m not sure everything that should be in there is either there or in the correct format.

]]> By: Eric Rickson http://blogs.webtrends.com/blog/2009/03/31/a-new-user-experience-part-1-of-5-introduction-to-tag-builder-30/comment-page-1/#comment-215 Eric Rickson Thu, 02 Apr 2009 21:15:59 +0000 http://blog.webtrends.com/?p=1516#comment-215 Thanks Bryan. To clarify for customers who haven't seen these parameters before, they are used only for WebTrends Marketing Warehouse and Visitor Intelligence WT.vt_sid Our data collection server now constructs the vt_sid from the first party cookie and session start time. This approach allows us to track across domains much like in Analytics, as long as the same dcsid is used on both domains. New optional parameters for Warehouse Visitor ID The current tag builder tag ( v2.1 and up) populates two new parameters: vtvs (session start time stamp) and vtid (visitor id). By default the tag will populate vtid with the co_f value. However, there is an override option in tag builder to set vtid based on a parameter or cookie. This is very useful if you want to use a different method for visitor identification in Marketing Warehouse than in Analytics while sharing the same dcsid. By default these parameters aren’t used for anything, but we have added new options for visitor identification for our Marketing Warehouse that lets you choose from the default vt_sid, the new vtid, or a user defined parameter. Pretty flexible stuff. Thanks Bryan.

To clarify for customers who haven’t seen these parameters before, they are used only for WebTrends Marketing Warehouse and Visitor Intelligence

WT.vt_sid
Our data collection server now constructs the vt_sid from the first party cookie and session start time. This approach allows us to track across domains much like in Analytics, as long as the same dcsid is used on both domains.

New optional parameters for Warehouse Visitor ID
The current tag builder tag ( v2.1 and up) populates two new parameters: vtvs (session start time stamp) and vtid (visitor id). By default the tag will populate vtid with the co_f value. However, there is an override option in tag builder to set vtid based on a parameter or cookie. This is very useful if you want to use a different method for visitor identification in Marketing Warehouse than in Analytics while sharing the same dcsid. By default these parameters aren’t used for anything, but we have added new options for visitor identification for our Marketing Warehouse that lets you choose from the default vt_sid, the new vtid, or a user defined parameter. Pretty flexible stuff.

]]> By: Bryan Cristina http://blogs.webtrends.com/blog/2009/03/31/a-new-user-experience-part-1-of-5-introduction-to-tag-builder-30/comment-page-1/#comment-217 Bryan Cristina Thu, 02 Apr 2009 20:14:23 +0000 http://blog.webtrends.com/?p=1516#comment-217 Hey guys, Just wondering what's up with the tagbuilder app. No matter if you check or uncheck the option to use vt_sid vs vtid, it will ALWAYS use vtid. Is that some sort of bug or the way it's supposed to be? Using the new .js, I'm not getting any first party cookie/sid information set. Hey guys,

Just wondering what’s up with the tagbuilder app. No matter if you check or uncheck the option to use vt_sid vs vtid, it will ALWAYS use vtid. Is that some sort of bug or the way it’s supposed to be?

Using the new .js, I’m not getting any first party cookie/sid information set.

]]> By: c prendergast http://blogs.webtrends.com/blog/2009/03/31/a-new-user-experience-part-1-of-5-introduction-to-tag-builder-30/comment-page-1/#comment-214 c prendergast Wed, 01 Apr 2009 18:20:35 +0000 http://blog.webtrends.com/?p=1516#comment-214 I just completed my first interaction with the new tagbuilder site. I thought it was much easier to use than the previous version. I was able to build my tag in just a few minutes without handholding by our WT account guys Tom S. and Dave J. (I'm sure they are happy the site is so easy to use too). Thank you for providing such great tools! I just completed my first interaction with the new tagbuilder site. I thought it was much easier to use than the previous version. I was able to build my tag in just a few minutes without handholding by our WT account guys Tom S. and Dave J. (I’m sure they are happy the site is so easy to use too). Thank you for providing such great tools!

]]> By: Michael Notté http://blogs.webtrends.com/blog/2009/03/31/a-new-user-experience-part-1-of-5-introduction-to-tag-builder-30/comment-page-1/#comment-216 Michael Notté Wed, 01 Apr 2009 08:50:29 +0000 http://blog.webtrends.com/?p=1516#comment-216 Well done guys! The interface is a good example of "form" best practices: clear interface, contextual help, selected fields being highlighted, clear error messages,... Much better than the previous one - make the process much clearer. Will probably plan upgrade of our tags from v8.0.3 to latest one - too many cool features Cheers, Michaël http://www.kaizen-analytics.com Well done guys!

The interface is a good example of “form” best practices: clear interface, contextual help, selected fields being highlighted, clear error messages,…

Much better than the previous one – make the process much clearer.

Will probably plan upgrade of our tags from v8.0.3 to latest one – too many cool features

Cheers,

Michaël
http://www.kaizen-analytics.com

]]>