Tips, tricks, and pokes, just WebTrends Analytics
Random header image... Refresh for more!

Cool custom report: Drill down through your directory structure

Applies to:  SDC data collection

Wouldn’t it be cool to have a drilldown report based on your directory structure?

FYI, WebTrends has two different drilldown-building methods. The complicated one involves specifying each level of the drilldown, where each level is based on a different parameter. The easy way involves specifying just one parameter — but that one parameter needs to contain all the levels of your drilldown.

Both methods are based on parameters. And your directory structure is in the URL, not in a parameter, so you can’t base a drilldown on it.

(dramatic pause)

Or can you?

WELL, ahem, SDC just happens to automatically collect a special parameter that contains the directory structure for every hit. It’s called WT.es. No, we don’t know what “es” is supposed to stand for.  (later comment:  we are informed that “es” stands for “event source” meaning it is the source page for which an event occurred, for the event tracking part of the tag.  We’re taking advantage of the fact that this parameter appears on all hits, not just event hits.)

An example of this parameter is: 
WT.es=http://www.yoursitename.com/directory1/directory2/ directory3/filename.aspx

A custom report based on this WT.es parameter gives you a slick view of traffic at every level of your directory structure. Here’s how to set up the dimension.

(First, check to be sure your version of the SDC tag generates WT.es.  It’s somewhat recent.  The TagBuilder tag definitely collects it, and I think one or two earlier versions do also.  Go to this post for info on how to view your tag’s output.)

Report Configuration >> Custom Reports >> Dimensions >> New Dimension

Give it a name, like “Drilldown on Directory Structure (WT.es)” and the column name can be “Path” or whatever you want to call it.

Base it on “Query Parameter” and enter “WT.es” for the parameter name.

Click on the Advanced button and an additional set of choices will appear. All you care about in this extra stuff is the box for “Parameter Contains Drilldown Data.” Check the box and enter “/” for the delimiter. Continue on, taking the defaults from this point, and save the new dimension.  Ta-dah.

Build a custom report with this as the dimension and things like Visits and Views for measures.

Enjoy! When looking at the report, keep in mind that

  • this is NOT a path analysis. Just because somebody got to /directory1/directory2/pageABC.html doesn’t mean they went through /directory1/ to get there. Each row of the drilldown report is its own entity, reporting traffic on that particular combination of directories and files.
  • blank lines mean “there was nothing at this level”.   Interpret a blank line to be a terminating slash in the URL, with nothing after it.  (Redundancy is good!)
  • Filenames will appear in this report as well as directories.  You can detect them by the fact that they have a file extension, like .jsp (assuming your filenames have extensions).  And that there’s nothing under them in the hierarchy.
Share:
  • Digg
  • Sphinn
  • del.icio.us
  • Facebook
  • Mixx
  • Google

Tags

, , ,

Somewhat Related Posts

  • Making your first Custom Reports!
  • ...
  • Suspending a Custom Report
  • ...
  • The WebTrends *.wlp file — knowing enough to be dangerous
  • ...

    7 comments

    1 Eric { 09.23.08 at 3:42 pm }

    That is a cool idea for a report. It actually be a useable replacement for the standard Pages report. Unfortunately I have an older version of WebTrends and don’t have the WT.es parameter. Do you think it would work with the query parameter dcsuri from the SDC?

    2 willig { 09.23.08 at 5:26 pm }

    WT.es stands for event source, meaning the source page for which an event occurred.

    3 rocky { 09.23.08 at 8:21 pm }

    Eric – Regarding dcs.dcsuri – no, it won’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’t end up that way in the SDC logs.

    Regarding the vintage of your WebTrends program — it’s actually the vintage of the SDC tag that’s the issue. I’ll be sure that’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.

    4 rocky { 09.23.08 at 8:22 pm }

    Willie – thanks!

    5 ashley { 01.12.09 at 3:41 pm }

    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.

    6 rocky { 01.12.09 at 8:29 pm }

    Ashley – absolutely.

    Do you by any chance want to write something on pre-analysis batch scripts? A lot of people would benefit!

    7 Guillermo Fuente { 03.11.10 at 4:12 am }

    This is one of the BEST custom reports i´ve ever seen. Thank you very much!

    Leave a Comment