Comments on: On tag placement and related mechanisms… http://webanalytics.ox2.eu/2007/03/16/on-tag-placement-and-related-mechanisms/ A companion in your Web Analytics journey Sun, 31 Jan 2010 07:32:45 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: Julien Coquet http://webanalytics.ox2.eu/2007/03/16/on-tag-placement-and-related-mechanisms/comment-page-1/#comment-549 Julien Coquet Mon, 19 Mar 2007 17:43:05 +0000 http://webanalytics.ox2.eu/2007/03/16/on-tag-placement-and-related-mechanisms/#comment-549 Thanks Dennis, Michael, I think both your comments point to the limitations of tagging automation in an enterprise context. However, it is refreshing to see some CMS editors take that paradigm into account and modify their tools, products and services to accomodate for their Web analytics needs. Again, this brings more water to my closing statements: go through the reflection process, structure your site and your content based on your business needs and mirror your Web Analytics tags. Cheers, Julien Thanks Dennis, Michael,

I think both your comments point to the limitations of tagging automation in an enterprise context.

However, it is refreshing to see some CMS editors take that paradigm into account and modify their tools, products and services to accomodate for their Web analytics needs.

Again, this brings more water to my closing statements: go through the reflection process, structure your site and your content based on your business needs and mirror your Web Analytics tags.

Cheers,

Julien

]]> By: Michael Notte http://webanalytics.ox2.eu/2007/03/16/on-tag-placement-and-related-mechanisms/comment-page-1/#comment-548 Michael Notte Mon, 19 Mar 2007 11:00:26 +0000 http://webanalytics.ox2.eu/2007/03/16/on-tag-placement-and-related-mechanisms/#comment-548 Hi Julien. Interesting post. On our side, we've "integrated" WebTrends tagging in our CMS platform for more than two years now. Javascript code is automatically added whenever a page is published from the CMS. We use the "footer" solution - mainly for performance and prevent potential display problems. We also integrated "logic" rules for the META tags in order to reduce manual definition as much as possible while offering flexibility. For example META tags are based on the templates used, META data fields from the CMS content (page title, section title,...), inheritance mechanisms... Still it offers possibility to override default rules for special cases. Of course, it has its limitations: we limited the number of tag used in our pages and we can't no simply add any specific or new tags without extra development. But in our context, we opted for compromise. We also try to do constant improvements to our tagging mechanism - step by step. Regards, Michaël Hi Julien.

Interesting post. On our side, we’ve “integrated” WebTrends tagging in our CMS platform for more than two years now. Javascript code is automatically added whenever a page is published from the CMS. We use the “footer” solution – mainly for performance and prevent potential display problems.

We also integrated “logic” rules for the META tags in order to reduce manual definition as much as possible while offering flexibility. For example META tags are based on the templates used, META data fields from the CMS content (page title, section title,…), inheritance mechanisms… Still it offers possibility to override default rules for special cases.

Of course, it has its limitations: we limited the number of tag used in our pages and we can’t no simply add any specific or new tags without extra development. But in our context, we opted for compromise. We also try to do constant improvements to our tagging mechanism – step by step.

Regards,

Michaël

]]> By: Dennis R. Mortensen http://webanalytics.ox2.eu/2007/03/16/on-tag-placement-and-related-mechanisms/comment-page-1/#comment-550 Dennis R. Mortensen Sat, 17 Mar 2007 20:47:30 +0000 http://webanalytics.ox2.eu/2007/03/16/on-tag-placement-and-related-mechanisms/#comment-550 Hi Julien, :-) Super post. This is something we, as you, work with on a daily basis. However; I do agree from a technical point of view that several options are available, but I find it un-realistic on an enterprise level to deploy Web Analytics “automatically”. Most Enterprise systems today have in the range of 50 to 100 variables and most of these is debated and “set” through standard business requirements consulting. Half the variables need again to be either inflated on-the-fly or even amended based on users actions. I think the future (as you indicate yourself) is more in the line of REAL integration in between CMS and Analytics packages. – way beyond fiddling with templates though. Again; really good post Julien! Dennis R. Mortensen, COO at IndexTools My Analytics blog http://visualrevenue.com/blog Hi Julien, :-)

Super post. This is something we, as you, work with on a daily basis. However; I do agree from a technical point of view that several options are available, but I find it un-realistic on an enterprise level to deploy Web Analytics “automatically”. Most Enterprise systems today have in the range of 50 to 100 variables and most of these is debated and “set” through standard business requirements consulting. Half the variables need again to be either inflated on-the-fly or even amended based on users actions.

I think the future (as you indicate yourself) is more in the line of REAL integration in between CMS and Analytics packages. – way beyond fiddling with templates though.

Again; really good post Julien!

Dennis R. Mortensen, COO at IndexTools

My Analytics blog
http://visualrevenue.com/blog

]]>