How to insert the Webtrends tag into Drupal sites

Following a Twitter conversation on how to implement the Webtrends tag into Drupal sites, I contacted their HelpLine and received the following (thanks Jon Bijak!), which I thought worth sharing as I could find nothing in their knowledge base when searching for Drupal: Products Webtrends On Demand Webtrends Analytics 9.2 Webtrends Analytics 8.7 Webtrends Analytics 8.5 Webtrends Analytics 8.1 Webtrends Analytics 8.0 Drupal is a widely used theme-based content management system. While Drupal has the capability of putting footer code on every page, blocks are filtered out of the footer. While Drupal has contributed modules that may provide the ability to do this, Webtrends does not manage or support them, and therefore the Webtrends tag should be added to the theme itself (the HTML section of a PHP file). Since it is possible to apply a separate theme to the Administration section, this gives the customer the added bonus of not having to track the administrator. Keep in mind that if you use multiple themes, you will need to apply this to each. Since it is possible to apply a separate theme to the Administration section, this gives the customer the added bonus of not having to track the administrator. 1. Go to to build the tag using V9. After selecting “Build Tag,” in the “Javascript Folder Name:” field enter the path “/sites/all/libraries/webtrends/”. 3. Save the tag, then extract its contents. 4. Copy the webtrends.js file to the “/sites/all/libraries/webtrends/” of your site, creating it if it doesn’t already exist. 5. Use a text editor to open the main template file for each theme (“page.tpl.php” by default) and webtrends.html (extracted from the Tag Builder archive). 6. Copy the contents of webtrends.html and paste it above the tag in the theme’s template file. 7. Save the template and close both files. 8. Repeat steps 6 and 7 for each theme. The theme should now be functioning and you’ll want to test it as you would any other site. More Information  There is currently a Drupal module for Webtrends. Using this module hasn’t been researched and this module is not supported or affiliated with Webtrends. Unfortunately, there does not appear to be anything that will handle commerce tagging. Any exploration into configuring Drupal, or any other CMS (beyond basic tagging) is strictly a Professional Services engagement.  N.B.  There is an error in the renumbering, but I don’t think it is important… Please let us know how you get on!

Webtrends IP-less Cookie

Data Concerns

With electronic surveillance projects like PRISM catapulting data intrusion and collection issues into the headlines, privacy is becoming more and more high profile in today’s Big Data era. It’™s a concern for consumers and providers of digital media alike. Consumers don’™t like the idea of their browsing history being available to Big Brother, yet this same information is key for website-owning organisations to monitor and improve their performance. Organisations need to balance the need for data with the need to have the trust of their customers.

Recent EU legislation attempted to resolve this issue by forcing websites to obtain consent from visitors before serving cookies, but studies have shown that only a tiny minority of people (less than 2%) actually block cookies. So what’s going on? Are people really concerned by cookies? I think the answer is a qualified yes, despite the lack of action actually taken by the consumer. A survey by eConsultancy showed that 89% of those surveyed thought the EU cookie legislation was a positive step and that only 23% of people would be happy to accept cookies. So, people are clearly concerned about cookies and a potential invasion of privacy but have little understanding of what a cookie is and how it is used. Cookies essentially have an image problem!

Cookie Make Over

It is left to the analytics providers to take a lead in addressing public concerns in order to protect their customers’™ (and their own) business interest. A cookie make-over is needed to increase trust and preserve loyalty in the face of fast changing public opinion. And that’s just what Webtrends has done by introducing their new IP-less cookie.

A step in the right direction

Traditionally Webtrends cookies have been constructed using the visitors IP address to generate a random value. In order to remove the IP address, Webtrends is phasing in the new cookie over the coming months. New visitors will receive the new IP-less cookie, while returning visitors will have the expiry date of their cookie (containing their IP address) set to 1st January 2014. Webtrends estimates that, as many visitors clear their cookies every month, by this date only 5% of visitors will have the old style cookie left on their machine. You don’™t need to do anything to make this happen, the process will be automatic.

However, an option is provided to remove the final 5% for organisations that want to totally eliminate IP storing cookies. This requires adding a JavaScript plugin to the new v10.4 tag which forces the overwriting of the old cookie value with the new. However, this is a value judgement each organisations has to weigh up independently. None-the-less this is a step in the right direction towards reassuring web visitors that analytics need not be overly intrusive and that, hopefully, will preserve the ability for organisations to collect and analyse the data they need to make essential business decisions.

For more information read Webtrends Knowledge Base Article: Improved Data Collection