In this session, Bocek discussed how to quickly diagnose and resolve Webtrends Analytics issues. Some of the best practices he suggested looking in the following locations for troubleshooting tips and general information:

o Customer Center within your Webtrends application
o Webtrends forums – http://forums.webtrends.com
o Webtrends Outsider – http://www.webtrendsoutsider.com (customer created and driven)

Webtrends On-Demand. If using On-Demand, inquire with your account manager about getting a software install for testing purposes only. It can allow you to test current setups before implementation in the OD environment. Log file delivery from WebTrends On-Demand may be needed.

There are also many ways you can use Webtrends to troubleshoot Webtrends. For example:

Use the URL viewed in Visit filter to include activity from all visitors who hit a URL or multiple URLs. This can be used to determine how a visitor hit a particular point on a web site, when in theory it is not supposed to be possible with the report originally created.

For example, “Same Visit Campaign” shows a campaign may not expect in the report. To determine how this is possible, create a filter with 1 “Visit Filter” and the option of “Filer must match ALL criteria”. The “Match Criteria” will have two separate matches. One will be the campaign you’re expecting to see and the other will be the campaign you do not want to see. The filter when completed is saying “only include activity if a visit hits both campaign A and campaign B in the same visit”.

Create a custom report with “Visitor” as the dimension and “hits” as the measure (to keep it simple). Add the filter to the custom report. Once it’s run, the only data in the report will be the visitors that hit both campaigns during the course of a visit. You can then use this information to pull out the entire visit from the logs and determine what’s happening to cause the report oddity.

To leave comments, please login or sign up to the Engage Network at the top of this page.