Lookup Tables for Custom Reports

When you assign a standard lookup table in a custom report, you can specify a key column and a value column. The key column contains the data shown in the web activity data file. The value column contains the data you want to display in the report.

Because you can specify key and value columns, you can use a lookup table with any number of columns, and you can use the same lookup table for different reports by identifying different columns as keys and values.

Custom reports support commas, spaces, and tabs as column delimiters in lookup tables. If a value in your custom report lookup table contains an internal delimiter, you can enclose the entire column value in quotes. However, you should not use quotes within a translation value.

A forward slash inside a translation value causes translation to fail. To use values that include forward slashes, such as dates in the form dd/mm/yyyy, enclose the entire value in quotes.

For example, the following table shows how Webtrends parses a lookup table where a value contains an internal delimiter. This example assumes that the file uses commas as the delimiter.

Lookup Table Key Column

Lookup Table Value Column

Translated Value







If you are using commas as a delimiter and a value column contains the value news,foreign, Webtrends processes the content after the comma as an additional column and interprets the value as news. To return the correct value of news,foreign, make sure the value in the lookup table is "news,foreign".

URL query parameters are translated after any hex encoded strings have been decoded. For example, the encoded value “xxx%20yyy” is decoded to “xxx yyy” before the translation lookup occurs.

You can assign a lookup table to a custom report in either of the following locations: