Webtrends Analytics 9 Adminstration Guide, November 2012
Implement the powerful drilldown feature for campaign reporting.
To implement the powerful drilldown feature for campaign reporting, Webtrends Analytics 9 uses the campaigns.csv file. For software users, this file resides in the installation directory\storage\config\wtm_wtx\datfiles\datasources directory. The information in this translation file identifies the following information for each campaign:
For example, the following sample line from campaigns.csv provides Webtrends Analytics 9 with information about the Free DVD Banner campaign.
123461,Free DVD Banner,Banner Ad,100 x 160 Image,Advertising Partner,Electronics Store,Bizrate 2003,Free DVD,BizRate,Right Frame
For this campaign, Campaign ID=123461, Creative=Banner Ad, Creative Type=100 x 160 Image, Demand Channel=Advertising Partner, and so on.
By default, this file contains data customized for the Zedesco website samples provided with Webtrends. To create campaign drilldown reports customized for your website, edit this file to provide information about each of your own campaigns. When you provide this information for your campaigns, you provide the information Webtrends Analytics 9 uses to track these categories using Visitor History and to build tables with multiple levels. If you use Webtrends Analytics 9 software, you can simply edit the existing campaigns.csv file or replace it with your own customized version, using the same number of columns in the same order and substituting commas for columns for which you do not include data. If you use Webtrends Analytics 9, contact Webtrends Support to have your own file uploaded and implemented.
By default, all profiles use the same campaigns.csv file. You can also use multiple versions of this file for different profiles.
It is technically possible to create campaign reports based on a translation file that uses different dimension columns or a different order of dimensions than those used in the default campaigns.csv file. However, with this method, translation occurs once for each corresponding dimension in each report, rather than only once during Visitor History processing. The number of lookups required to create the drilldowns is thus much larger, and increases dramatically with any increase in the number of drilldown reports or in the size of the translation file. Because of the potential performance and scalability problems associated with these extra lookups, it is best to use only the methods described in this document to modify campaign translation files.