Online Marketing Trends

I just got this reply on my case at WebTrends Support; “Currently IE7 is not supported by the WebTrends 8.0a product and unfortunately WebTrends does not have information when they will be completely compatible with IE7.”

It’s sad actually that they are waiting too long with supporting new versions; Office 2007 is’t’ supported either.

The release of Microsoft Office 2007 is on it’s way.

I noticed that WebTrends Report Exporter doesn’t work in combination with Word 2007. It looks like WebTrends is not seeing the future challenge yet. This is their anwer:

There is no official word on which version of WebTrends will be supported with MS Word 2007.

Are you getting these certificate errors when logging in to WebTrends?

Just click “Always trust content from this publisher” as this will take away the warning message.

The “More information” dialog will show this:

Then be rest assured that WebTrends will solve this problem in a feature release. WebTrends’ response is;

“This is a known issue and will be resolved in a future release of WebTrends. To prevent the message from coming back check the “Always trust content from this publisher” box.:”

WebTrends told me that this problem should be solved in next release, 8.0b.>

The new WebTrends version 8 is part of the WebTrends Marketing Lab, a new name for the products WebTrends Analytics and WebTrends Marketing Warehouse.

With this new suite WebTrends focusses not only on web analytics but also on Marketing Performance Measurement.

Now I already posted some screenshots from WebTrends Analytics 8, here is a screenshot of WebTrends Marketing Warehouse:

In one sentences WebTrends describes WebTrends Marketing Warehouse as;

WebTrends Marketing Warehouse makes it easy to understand precisely which products, services and information your customers want, so you can increase the impact of relationship marketing programs such as email marketing.

WebTrends Marketing Warehouse.pdf (251.15 KB)

Did you ever get the error from WebTrends that it couldn’t extract logfiles because there was insufficient disk space while there were hundreds of gigabytes available ?

I often get these warnings with logfiles that are several hundred MB’s of size:

Unable to extract Logfiles/W3SVC57/ex051229.log, a member of archive G:\manual\ex051229.zip, because of insufficient disk space (149MB available, 263MB required)

Solution; extract the logfiles yourself and let WebTrends use the extracted logfiles. It looks like WebTrends reports about the available RAM memory as being disk space. Apparently it tries to load the extracted logfile in memory while analyzing it.

With MCMS2002 you have Channels and Postings; a Channell contains one or more Postings. A Channel has a default Posting which is being displayed when you request the Channelname in the browser.

Example; Channel /ETV/Utrecht/ (http://www.etv.nl/ETV/Utrecht) is the homepage for the Utrecht “Venster” of ETV. It will display the Posting /ETV/Utrecht/Utrecht.htm as this is set as default Posting.

Now, both http://www.etv.nl/ETV/Utrecht and http://www.etv.nl/ETV/Utrecht/Utrecht.htm will show exactly the same content. When analyzing the Pages report in WebTrends, both URL’s will occur:

Now this is not an ideal situation because you just want totals without having to pick your calculator. These were two options I figured out;

1. Use WebTrends’ URL Search/Replace
For every Channel you have to make a definition that adds the name of the Posting to the Channel URL. So it rebuilds the records in the logfile from http://www.etv.nl/ETV/Utrecht/ to http://www.etv.nl/ETV/Utrecht/Utrecht.htm. The disadvantage is that we have a lot of Channels in this site. Every time a Channel has been made or has been changed, you will have to add a new URL Search/Replace definition or change it.

2. Use Script URL in Microsoft Content Management Server 2002
Redirect all traffic initially destined for a Channel to the Posting-url. You can do this with the “Script URL” property of a Channel. In this field you specify the URL of a redirectpage, the redirectpage handles the request and forwards it to the Posting-URL.

The disadvantage is that you are introducing a redirect in your site and redirects are a no-no for search engines. To decrease most of the negative points, we use a 301 Moved Permanently redirect instead of the 302 you’d use when you do a Response.Redirect;

        private void Page_Load(object sender, System.EventArgs e)
        {
            Channel currentChannel = CmsHttpContext.Current.Channel;
            string defaultPosting = currentChannel.DefaultPostingName;
            if (defaultPosting != “”)
            {
                if (currentChannel.Postings[defaultPosting] != null)
                {
                    Response.Status = “301 Moved Permanently”;
                    Response.AddHeader(“Location”,currentChannel.Postings[defaultPosting].Url);
                }
            }
        }