Webtrends Implementation Streamlining

The Client

The client is a US based company, which is a pioneer in the field of online content syndication.

The Need

The client already had a vendor to manage their Webtrends setup. However, the vendor was unable to implement the software properly and there were problems with the setup. Because of this data management was a difficulty. There were no provisions for automated downloading of log files and even basic modifications in the profile setup were difficult to make.

The client was using Webtrends Ver 8.7 to track the following:

• Websites of over 30 syndicate partners
• Their content which was being shared by their partners
• Their pages displayed on other websites via iFrames
• Sponsored and Unsponsored traffic coming to the website
• Their Branded (carrying the client's logo) and Unbranded content being consumed
• Number of Sponsored (3rd party) links being clicked. This was not easy as there is no ownership of these websites and we can't insert tags and codes into them

The Solution

Nabler was roped in by the client for Webtrends Data Administration. Nabler had access to the databases of both the client and the client's Webtrends vendor.

Nabler's approach:

• Began by analyzing the entire Webtrends setup. Checking how it is currently configured.
• To fix the problem of log files not being updated on time, they began by streamlining the whole process so as to get timely data.
• Looked at the frequency of log files and monitored how profiles were being currently processed.
• Proper scheduling was done based on the frequency of log files. As they were monitoring multiple websites, their log file delivery had to be planned in such a way that there was no clash.
• Depending on what time each profile's log got downloaded, data was arranged in queues on priority basis. The scheduling mechanism manages back to back delivery of various files for on time delivery of required metrics.
• Nabler simplified the process of incorporating new profiles in a way that did not disrupt the current flow of data.
• Various filters and missing IPs were included in the log setup.
• One of the interesting initiatives of Nabler was the introduction of 'Restore Points' in the profile setup. This enabled the user to roll back to certain profile mid-points in case of any error in data, instead of rolling back to the very beginning. Earlier if a problem in data was detected, then the user had to begin setting the profile from the very start. For example, if any internal testing was done and those IPs were not excluded from the data to be analyzed, then the whole profile would need to be reset in order to get the correct data set.
• They also helped the client track the 3^rd party/sponsored links. This was a critical task as it is not possible to insert tracking codes into these websites. Nabler was able to give the client these figures which helped them monitor the 3rd party traffic.

The Benefits

• Timely delivery of data
• Helped keep a track of how their content was being used and in turn track their revenue streams
• Measure the performance of the competitors by tracking their content's performance
• Saving data and time while rectifying the problem with the help of 'Restore points'
• Easily update the account to add new profiles and edit existing ones
• Setting up the 'automated downloading' function to simplify the reporting process
• Scheduling of log files to effectively manage multiple data points