<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: Cool custom report:  Drill down through your directory structure</title>
	<atom:link href="http://www.webtrendsoutsider.com/2008/cool-custom-report-drill-down-through-your-directory-structure/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.webtrendsoutsider.com/2008/cool-custom-report-drill-down-through-your-directory-structure/</link>
	<description>Tips, tricks, and pokes, just WebTrends Analytics</description>
	<lastBuildDate>Fri, 13 Aug 2010 14:44:12 -0600</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Guillermo Fuente</title>
		<link>http://www.webtrendsoutsider.com/2008/cool-custom-report-drill-down-through-your-directory-structure/comment-page-1/#comment-1865</link>
		<dc:creator>Guillermo Fuente</dc:creator>
		<pubDate>Thu, 11 Mar 2010 10:12:35 +0000</pubDate>
		<guid isPermaLink="false">http://www.webtrendsoutsider.com/?p=86#comment-1865</guid>
		<description>This is one of the BEST custom reports i´ve ever seen. Thank you very much!</description>
		<content:encoded><![CDATA[<p>This is one of the BEST custom reports i´ve ever seen. Thank you very much!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rocky</title>
		<link>http://www.webtrendsoutsider.com/2008/cool-custom-report-drill-down-through-your-directory-structure/comment-page-1/#comment-1200</link>
		<dc:creator>rocky</dc:creator>
		<pubDate>Tue, 13 Jan 2009 02:29:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.webtrendsoutsider.com/?p=86#comment-1200</guid>
		<description>Ashley - absolutely.

Do you by any chance want to write something on pre-analysis batch scripts?  A lot of people would benefit!</description>
		<content:encoded><![CDATA[<p>Ashley &#8211; absolutely.</p>
<p>Do you by any chance want to write something on pre-analysis batch scripts?  A lot of people would benefit!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ashley</title>
		<link>http://www.webtrendsoutsider.com/2008/cool-custom-report-drill-down-through-your-directory-structure/comment-page-1/#comment-1198</link>
		<dc:creator>ashley</dc:creator>
		<pubDate>Mon, 12 Jan 2009 21:41:56 +0000</pubDate>
		<guid isPermaLink="false">http://www.webtrendsoutsider.com/?p=86#comment-1198</guid>
		<description>One thing to consider, if you have an older version of WebTrends (pre WT.es) and really want this parameter, you can always use a pre-analysis batch script to parse the SDC log and create a custom parameter with this information. While i have not done this for the directory info, I have successfully done this for many other things that we needed, but were not able to get tagged on the page. Also, if you have a content management system, you can frequently configure them to place the published URL in a custom Meta tag parameter.</description>
		<content:encoded><![CDATA[<p>One thing to consider, if you have an older version of WebTrends (pre WT.es) and really want this parameter, you can always use a pre-analysis batch script to parse the SDC log and create a custom parameter with this information. While i have not done this for the directory info, I have successfully done this for many other things that we needed, but were not able to get tagged on the page. Also, if you have a content management system, you can frequently configure them to place the published URL in a custom Meta tag parameter.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rocky</title>
		<link>http://www.webtrendsoutsider.com/2008/cool-custom-report-drill-down-through-your-directory-structure/comment-page-1/#comment-1046</link>
		<dc:creator>rocky</dc:creator>
		<pubDate>Wed, 24 Sep 2008 02:22:44 +0000</pubDate>
		<guid isPermaLink="false">http://www.webtrendsoutsider.com/?p=86#comment-1046</guid>
		<description>Willie - thanks!</description>
		<content:encoded><![CDATA[<p>Willie &#8211; thanks!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: rocky</title>
		<link>http://www.webtrendsoutsider.com/2008/cool-custom-report-drill-down-through-your-directory-structure/comment-page-1/#comment-1045</link>
		<dc:creator>rocky</dc:creator>
		<pubDate>Wed, 24 Sep 2008 02:21:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.webtrendsoutsider.com/?p=86#comment-1045</guid>
		<description>Eric - Regarding dcs.dcsuri - no, it won&#039;t work.  The dcs.* parameters get transformed by the SDC server back into whatever they should be in logs.  DCS.dcsuri gets turned back into the URI field  for example.  DCS.dcssta gets turned back into the status code field.  When you peek at what SDC is sending, those are parameters, yes.  But they don&#039;t end up that way in the SDC logs.

Regarding the vintage of your WebTrends program --- it&#039;s actually the vintage of the SDC tag that&#039;s the issue.  I&#039;ll be sure that&#039;s more clear in the posting.  The Tagbuilder tag definitely creates WT.es, and I think one or two of the previous versions (pre-tagbuilder).  I believe version 1.07 was the first one that did so.  Not all tags have a version number in them.</description>
		<content:encoded><![CDATA[<p>Eric &#8211; Regarding dcs.dcsuri &#8211; no, it won&#8217;t work.  The dcs.* parameters get transformed by the SDC server back into whatever they should be in logs.  DCS.dcsuri gets turned back into the URI field  for example.  DCS.dcssta gets turned back into the status code field.  When you peek at what SDC is sending, those are parameters, yes.  But they don&#8217;t end up that way in the SDC logs.</p>
<p>Regarding the vintage of your WebTrends program &#8212; it&#8217;s actually the vintage of the SDC tag that&#8217;s the issue.  I&#8217;ll be sure that&#8217;s more clear in the posting.  The Tagbuilder tag definitely creates WT.es, and I think one or two of the previous versions (pre-tagbuilder).  I believe version 1.07 was the first one that did so.  Not all tags have a version number in them.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
