Comments on: Web Analytics Technical Implementation Best Practices. (JavaScript Tags) http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html Pluralitas non est ponenda sine neccesitate. Fri, 05 Dec 2008 17:54:22 +0000 http://wordpress.org/?v=2.6.5 By: Trending Upward | Analytics is attitude - we need an adjustment http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-477409 Trending Upward | Analytics is attitude - we need an adjustment Fri, 05 Dec 2008 04:28:31 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-477409 [...] First, take a look at this quick list of implementation tips from our good friend Avinash. That post is almost 2 years old, but I think it still holds true today. If you’re implementing a proprietary tool like Omniture or WebTrends, make sure to talk to your vendor about your business and web site goals before implementation. [...] [...] First, take a look at this quick list of implementation tips from our good friend Avinash. That post is almost 2 years old, but I think it still holds true today. If you’re implementing a proprietary tool like Omniture or WebTrends, make sure to talk to your vendor about your business and web site goals before implementation. [...]

]]> By: Phil http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-407785 Phil Tue, 29 Jan 2008 12:08:39 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-407785 Hello Avinash, I've just read this section in your book and came on your blog to see if you had anything more about the issue of redirects. As you know a large percentage of the traffic that arrives on your website comes with the referrer camp blank. I know that there are many reasons behind this, bookmarks, server issues, etc, but one of them is faulty redirects. Are there any ways at dealing with these to glean any useful information, to help segment the data better? The book is great btw! Hello Avinash,

I’ve just read this section in your book and came on your blog to see if you had anything more about the issue of redirects. As you know a large percentage of the traffic that arrives on your website comes with the referrer camp blank. I know that there are many reasons behind this, bookmarks, server issues, etc, but one of them is faulty redirects.

Are there any ways at dealing with these to glean any useful information, to help segment the data better?

The book is great btw!

]]> By: Zack http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-406670 Zack Fri, 25 Jan 2008 22:10:58 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-406670 Have you heard of anyone using the SiteCatalyst debugger like a sitemap to check an entire site instead of just one page at a time? In theory the dugger tool could be used in this fashion. I was also trying to customize a Visio web sitemap to capture page tag info but it will only return the meta tag titles and URLs. Have you heard of anyone using the SiteCatalyst debugger like a sitemap to check an entire site instead of just one page at a time? In theory the dugger tool could be used in this fashion.
I was also trying to customize a Visio web sitemap to capture page tag info but it will only return the meta tag titles and URLs.

]]> By: Zack http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-406560 Zack Fri, 25 Jan 2008 17:06:35 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-406560 When you refer to the nifty tool that Omniture has to validate tags are you referring to the Debugger? - - - - - - Avinash: Yes Zack. Please check with Omniture's Tech Support. When you refer to the nifty tool that Omniture has to validate tags are you referring to the Debugger?

- - - - - -

Avinash: Yes Zack. Please check with Omniture’s Tech Support.

]]> By: links for 2007-09-21 « Simply… A User http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-242737 links for 2007-09-21 « Simply… A User Fri, 21 Sep 2007 00:43:47 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-242737 [...] Web Analytics Technical Implementation Best Practices. (JavaScript Tags) » Occam’s Razor by Avinash Kaushik (tags: analytics webanalytics web article blog dev internet **) [...] [...] Web Analytics Technical Implementation Best Practices. (JavaScript Tags) » Occam’s Razor by Avinash Kaushik (tags: analytics webanalytics web article blog dev internet **) [...]

]]> By: Justin Cutroni http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-42617 Justin Cutroni Wed, 14 Feb 2007 02:42:32 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-42617 Hi Avinash, Regarding Item # 5: <blockquote> Use cookies intelligently (they are delicious) ...... One last thing on cookies, please be aware that IE 6 limits the number of cookies to 20 per domain. </blockquote> I believe this is a browser issue, not just an IE issue. So the 20 cookie limit also applies to FireFox and, I would assume, Safari. Justin Hi Avinash,

Regarding Item # 5:

Use cookies intelligently (they are delicious)

……

One last thing on cookies, please be aware that IE 6 limits the number of cookies to 20 per domain.

I believe this is a browser issue, not just an IE issue. So the 20 cookie limit also applies to FireFox and, I would assume, Safari.

Justin

]]> By: Sushant Ajmani http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-29186 Sushant Ajmani Fri, 19 Jan 2007 22:57:10 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-29186 Here are some points to consider: - 1. Use the TRACKING CODES appropriately in your Marketing Data Feeds.**VERY VERY IMP (Keep in mind the % of MARKETING BUDGET as a part of SALES) 2. Send Regular Data Feeds from your CRM system to your Analytical system so that; you could view the TRAFFIC data for multiple Customer Segments. This strategy works for B2B sites. 3. Send regular DATA FEEDS from your Order Management system to your Analytical Solution so that; you could club your OFFLINE sales with your ONLINE COMMERCE data and enjoy the consolidated view of your business. 4. If your company sells products on EBAY or OVERSTOCK then schedule a daily feed for your ANALYTICAL solution 5. PAGE NAMEs are the most important piece of information on the site and most of the companye don't use them consistently so; be cautious in this regards. 6. Keep special eye on FALLOUT REPORT and SINGLE PAGE VISIT report because; solution for most of the analytical problems lies in them. I can write 100 more points but; above mentioned are some of the important ones. Here are some points to consider: -

1. Use the TRACKING CODES appropriately in your Marketing Data Feeds.**VERY VERY IMP (Keep in mind the % of MARKETING BUDGET as a part of SALES)

2. Send Regular Data Feeds from your CRM system to your Analytical system so that; you could view the TRAFFIC data for multiple Customer Segments. This strategy works for B2B sites.

3. Send regular DATA FEEDS from your Order Management system to your Analytical Solution so that; you could club your OFFLINE sales with your ONLINE COMMERCE data and enjoy the consolidated view of your business.

4. If your company sells products on EBAY or OVERSTOCK then schedule a daily feed for your ANALYTICAL solution

5. PAGE NAMEs are the most important piece of information on the site and most of the companye don’t use them consistently so; be cautious in this regards.

6. Keep special eye on FALLOUT REPORT and SINGLE PAGE VISIT report because; solution for most of the analytical problems lies in them.

I can write 100 more points but; above mentioned are some of the important ones.

]]> By: Lies, Damned Lies... http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-27504 Lies, Damned Lies... Mon, 15 Jan 2007 01:57:58 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-27504 <strong>JavaScript advice...</strong> There's a good post over on Avinash's blog with 9 tips for getting JavaScript tagging right on your website. There's not much for me to add except to say that you should click the link above and read his advice;... JavaScript advice…

There’s a good post over on Avinash’s blog with 9 tips for getting JavaScript tagging right on your website. There’s not much for me to add except to say that you should click the link above and read his advice;…

]]> By: Jeff Lawrence http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-26801 Jeff Lawrence Fri, 12 Jan 2007 21:37:51 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-26801 Excellent post. I find that proper implementation is critical with web analytics. All too often we have users who have botched the installation process in one way or another (usually involving PHP or other sites) instead of taking it as a step by step approach. Excellent post. I find that proper implementation is critical with web analytics. All too often we have users who have botched the installation process in one way or another (usually involving PHP or other sites) instead of taking it as a step by step approach.

]]> By: Julien Coquet http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-26441 Julien Coquet Thu, 11 Jan 2007 15:32:58 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-26441 Robbin in this case, you need to include JS code earlier in the page because variables initialized in the JS include are then modified by subsequent calls to <i>_utmFunctionNameHere</i> functions in this case only does your tracking code need to be placed higher up in the code, most preferrably within the HEAD tag IMHO. Robbin in this case, you need to include JS code earlier in the page because variables initialized in the JS include are then modified by subsequent calls to _utmFunctionNameHere functions
in this case only does your tracking code need to be placed higher up in the code, most preferrably within the HEAD tag IMHO.

]]> By: Robbin Steif http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-26397 Robbin Steif Thu, 11 Jan 2007 12:59:56 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-26397 <b>I don't think so</b> but I know you guys at OX2 are incredibly sophisticated so I won't pretend to know something that you don't. (And like I said, I'm just technical enough to be dangerous.) I mostly can pull up the Google Analytics guide and quote it at you: <i>Important: if your pages include a call to urchinTracker(), utmLinker(), utmSetTrans(), or utmLinkPost(), your Analytics tracking code must be placed in your HTML code above any of these calls. In these cases the tracking code can be placed anywhere between the opening body tag and the JavaScript call.</i> I went through your example to see if I could find a special way that you got around the problem, but didn't see it. Tell me I'm wrong - Robbin I don’t think so but I know you guys at OX2 are incredibly sophisticated so I won’t pretend to know something that you don’t. (And like I said, I’m just technical enough to be dangerous.) I mostly can pull up the Google Analytics guide and quote it at you:

Important: if your pages include a call to urchinTracker(), utmLinker(), utmSetTrans(), or utmLinkPost(), your Analytics tracking code must be placed in your HTML code above any of these calls. In these cases the tracking code can be placed anywhere between the opening body tag and the JavaScript call.

I went through your example to see if I could find a special way that you got around the problem, but didn’t see it. Tell me I’m wrong -

Robbin

]]> By: Julien Coquet http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-26370 Julien Coquet Thu, 11 Jan 2007 11:13:46 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-26370 Bleh, indents got block-quoted :P Oh well. I rest my case ;-) Bleh, indents got block-quoted :P

Oh well. I rest my case ;-)

]]> By: Julien Coquet http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-26369 Julien Coquet Thu, 11 Jan 2007 11:10:31 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-26369 Robbin, that's a non-issue. Look at the example code below: (hope this comes out right) <html> <blockquote> <head> <blockquote> <!-- header stuff goes here: META tags, title, JS, CSS, RSS calls, you name it--> </blockquote> </head> <body> <blockquote> <a href="javascript:;" onClick="foo('stuff');">Clicky</a> <!-- Your content here --> <script type="text/Javascript"> <blockquote> function foo(bar){ <blockquote> alert ('omg the code for this behavior is declared in the footer\n\rand yet it works upper in the page!'); </blockquote> } </blockquote> </script> </blockquote> </body> </blockquote> </html> Robbin, that’s a non-issue. Look at the example code below:
(hope this comes out right)

<html>

<head>

<!– header stuff goes here: META tags, title, JS, CSS, RSS calls, you name it–>

</head>
<body>

<a href="javascript:;" onClick="foo(’stuff’);">Clicky</a>
<!–
Your content here –>
<script type="text/Javascript">

function foo(bar){

alert (’omg the code for this behavior is declared in the footer\n\rand yet it works upper in the page!’);

}

</script>

</body>

</html>

]]> By: Robbin Steif http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-26244 Robbin Steif Thu, 11 Jan 2007 03:58:40 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-26244 Sorry, I forgot that your blog would execute the html. Anyway, the urchintracker code probably needs to be right after the open body tag. Sorry, I forgot that your blog would execute the html. Anyway, the urchintracker code probably needs to be right after the open body tag.

]]> By: Robbin Steif http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-26243 Robbin Steif Thu, 11 Jan 2007 03:57:11 +0000 http://www.kaushik.net/avinash/2007/01/web-analytics-technical-implementation-best-practices-javascript-tags.html#comment-26243 Hi Avinash. I am probably the demographic this post is written for -- a marketing person who knows just enough about the technology to be dangerous. (So thank you, and with your help, I will be less dangerous, and certainly my own blog works better because of you.) Anyway, what do you and Julien think of the onclick problem that Google Analytics poses? In order to tag onclick events or much of the stuff you note in #9, the main part of the analytics has to be called first. So if the click happens high on the page, the urchintracker code probably needs to be right after the tag. Robbin Hi Avinash. I am probably the demographic this post is written for — a marketing person who knows just enough about the technology to be dangerous. (So thank you, and with your help, I will be less dangerous, and certainly my own blog works better because of you.)

Anyway, what do you and Julien think of the onclick problem that Google Analytics poses? In order to tag onclick events or much of the stuff you note in #9, the main part of the analytics has to be called first. So if the click happens high on the page, the urchintracker code probably needs to be right after the tag.

Robbin

]]>