Friday, June 12, 2009

Tracking Referrals from Microsoft Bing

On June 1st, Microsoft released Bing, the company’s next generation search engine and aspiring Google killer. Bing has gotten a lot of publicity lately and chances are, it may have referred a good piece of your website visitors already.

As a web analyst, you may be wondering what your Analytics vendor is doing to accommodate Bing and what steps you may need to take to update your search engine-related reports. I will try to answer those questions below.

If you are using a software-as-a-service (SaaS) solution, your vendor may have already updated (or will soon be updating) their solution to accommodate this new search engine into their reports. If not, you will most likely need to perform an update to your software.

  • WebTrends On Demand customers have begun to see the changes on the date of the launch itself. If you are however using WebTrends Analytics on-premise software, you will need to run a browser and keywords updater, downloadable via the WebTrends Support site.

  • Omniture updated its collection of tools (SiteCatalyst, SearchCenter, Discover OnPremise) on June 3rd. You can check out Omniture's press release for more information.

  • Google is actively working on an update to recognize Bing in Google Analytics. In the meantime, you can customize your Google Analytics tracking code by adding the following line:

    pageTracker._addOrganic("bing", "q");

Nestor Archival Jr.
Senior Analyst, Consulting Services
Stratigent, LLC

Thursday, June 11, 2009

Educational Resources - As Promised

I hope that you’ve been able to make it out to an OMS near you. I’ve had the pleasure of presenting in MN and ATL, and the crowds have been awesome! As part of my presentation, “Inside the Mind of an Analyst,” I promised to deliver a list of resources that you could use to educate yourself on Web Analytics. So, as promised, here is a list. I’d love for you to comment and add in other resources that I don’t have listed, and please contact me directly if you have any questions at all (bill@stratigent.com).

Books:


Web Analytics Demystified (http://bit.ly/11yceN) by Eric Peterson

The Big Book of KPIs (http://bit.ly/11yceN) by Eric Peterson

Web Analytics: An Hour A Day (http://bit.ly/G7G4m) by Avinash Kaushik

Yahoo! Web Analytics (http://bit.ly/9TIc2) by Dennis Mortensen

Advanced Web Metrics with Google Analytics (http://bit.ly/ah3ax) by Brian Clifton

Always Be Testing (http://bit.ly/33VUb) by Bryan Eisenberg

Call to Action (http://bit.ly/shNnt) by Bryan Eisenberg


Blogs:


http://analyticsinsightblog.stratigent.com/

http://blog.onlinemarketingconnect.com/

http://www.kaushik.net/avinash/

http://webanalyticsdemystified.com/wad-weblogs.asp

http://sethgodin.typepad.com/

http://rich-page.com/

http://blog.webtrends.com/

http://www.omniture.com/en/resources/blogs

http://blog.coremetrics.com/

http://analytics.blogspot.com/

http://www.grokdotcom.com/


Help Forums/Developer Portals:


http://www.google.com/analytics/support_overview.html

http://developer.omniture.com/

http://developer.webtrends.com/community/developer/

http://groups.yahoo.com/phrase/webanalytics

http://help.yahoo.com/l/us/yahoo/ywa/

http://www.twitter.com/ (Hashtags: #wa, #ga,#ya, #omniture, #webtrends, etc.)


Bill Bruno

VP, Business Development & Technology



Thursday, May 21, 2009

Google Outage Proves the Importance of Page Tag Location

Last Thursday's Google outage had a dramatic impact on more than just Google users. It was widely reported that the outage killed 5% of Internet traffic and prevented users from accessing popular services such as Gmail and YouTube. The less-reported aspect of the story is that the outage also impacted some websites using Google Analytics. During the outage, the visitors to those sites noticed distinctly slower-than-normal loading times.

The slow-loading websites problem was caused by the way that the Google Analytics tracking code was added to the site pages. The Google Analytics page tags are hosted on Google's servers, so if the tracking code was placed at the top of the HTML page, visitors experienced delays while the content below that code loaded.

There are risks and benefits with placing web analytics page tags near the top of the HTML code or near the bottom. Last week's outage highlighted the risk of placing the tag at the top. Because of this potential issue, Stratigent has generally recommended that the Google tracking code be placed at the bottom of the page, immediately before the tag. This ensures that visitors see your site content before the Google page tag is requested.

Although there are some exceptions, this best practice also applies to other page tag-based tools. There are rare cases when the data-collection servers for any web analytics tool are either down or slow. Putting the page tag code near the bottom of the page will prevent this from adversely affecting the visitor experience.

Nestor Archival Jr.
Senior Analyst, Consulting Services
Stratigent, LLC

Friday, May 15, 2009

Tracking 301 Redirects in WebTrends

One way to track referrals from a 301 redirect is to append a URL parameter. However, if you use a question mark (?) to do so, you will create duplicate content issues that impact your search engine rankings. To solve this issue, use a hash (#) tag instead.

In WebTrends, tracking hash tags as part of the query string requires custom changes to the page tag.

CAUTION: Don't change your WebTrends page tags unless you are familiar with JavaScript and the WebTrends tracking code. Always perform testing of code changes before moving changes to production.

Old Tag Versions

For older tag versions (1.x.x), the following changes need to be performed on the wtinit.js and wtbase.js files.

(1) In the wtbase.js file, add and run a dcsHash() function that will parse “hash” parameter-value pairs. For each page tag call, dcsHash() is called if and only if the custom trackhashes variable is set to true (set in step 2).



(2) Add a line of code to the wtinit.js file that enables a flag needed in the tracking of “hash” parameters.



To turn off the tracking of hash parameters, you can set this.trackhashes to false.

New Tag Versions

Due to code structure changes in the most recent tag versions (8.x.x) created from WebTrends Tag Builder, there are slight differences to the way you should modify the new tags compared to the old ones. The following changes need to be performed on the inline code and webtrends.js file.

(1) In the WebTrends() function of the webtrends.js file, assign a default value of false to a custom trackhashes variable.



Note: Always set the trackhashes variable to false since this acts as a default value. If you want to enable the tracking of “hash” parameters and set this variable to true, do so in step 3 below.

(2) In the webtrends.js file, add and run a dcsHash() function that will parse the “hash” parameter-value pairs. For each page tag call, dcsHash() is called if and only if the custom trackhashes variable is set to true (set in step 3).



(3) In the inline code right before the _tag.dcsCollect(); line, set the trackhashes value to true to enable the “hash” tracking functionality.



To turn off tracking of “hash” parameters, you can set _tag.trackhashes to false.

When this has been completed, the WebTrends tag will treat the “hash” parameters as if they are regular query string parameters. You will then be able to use and report on the “hash” parameters as dimensions in custom reports.

Nestor Archival Jr.
Senior Analyst, Consulting Services
Stratigent, LLC

Monday, April 20, 2009

How to Use Fiddler with Firefox


Ever wanted to do QA and use Fiddler for Firefox? Are you frustrated with having Firebug restrict viewing downloaded objects on a page-by-page basis? Do you want to see all the downloaded objects for an entire session in a single list in Fiddler?

If you happen to answer ‘yes’ to any question above, then do this:

1. Open Fiddler.

2. Open Firefox.
  • In Firefox, go to Tools > Options > Advanced.
  • Go to the Network tab, and click “Settings…”.
  • Change the Connection Settings and use the ones below:



Firefox traffic should then go through the Fiddler proxy, allowing the tool to capture your data. Once you are done, don’t forget to reset the proxy back to normal settings.

As an additional tip, you can download the Firefox “SwitchProxy” which allows you to configure different proxy setting profiles for easy proxy switching:


Nestor Archival Jr.
Senior Analyst, Consulting Services
Stratigent, LLC

Wednesday, April 15, 2009

WebTrends Releases Tag Builder v3.0 with a Slew of Improvements

WebTrends Tag Builder 3.0 went live toward the end of March and presented the renewed panache and enthusiasm that has been building up in the WebTrends organization recently. On the v3.0 release, WebTrends Technical Support Manager Wayne Denman said, “This is the first time the general public gets to sample the flavor of our customer centric approach to building products and marks an especially important milestone for WebTrends.”

There have been several iterations of the tool from its May 2008 initial release, which I discussed in my previous Tag Builder post. Since this initial release, a lot of incremental improvements have been introduced. The said improvements have carried over to this newest release along with several new enhancements. Here are some of the most essential changes I have seen:

1. The TB interface underwent a facelift, now offering to “support a more usable, task-based workflow.” A simple yet elegant interface greets you when you visit the TB site. The tool cuts to the chase as Required Settings, the minimum configurations you need to supply to build a tag, have been emphasized while not undercutting the ability to supply Additional Options when needed. Additionally, highlighted contextual help appears when you hover over each of the settings.

2. TB implemented an improved and dynamic field validation system. Error messages are clear and provide valuable context. It notifies you when you forget to enter a value on a required field or when you enter an invalid value. It even requires you to enter the correct DCSID format (dcsxxxxxxxxxxxxxxxxxxxxxx_xxxx).

3. TB provided support for other existing tagging technologies, namely WebTrends Ad Director and Quantcast. To enable the tag integrations, you will need to enter your customer IDs for the said technologies.

4. TB incorporated a more comprehensive Help section that caters to each and every configuration setting available in the tool. As a plus, Help shows up as a convenient AJAX popup that can easily be closed by hitting the “Esc” key on your keyboard or clicking on “close.”

5. TB resolved several minor quirks, including but not limited to removing case-sensitivity requirements for file download extensions (i.e. exe, pdf, doc, etc) and META tag name prefixes (i.e. WT, DCS, and DCSext), and correctly tracking Silverlight 2.0.

Note: For a complete list of changes, refer to the Tag Builder Release Notes. Additionally, refer to the WebTrends Blog for an introduction to the new Tag Builder design.

Needless to say, I am very excited for how the newest version of the ever-evolving Tag Builder turned out. I am also very thrilled for our WebTrends clients who are now able to utilize the newest Tag Builder in their tagging implementation efforts, basic or advanced. As someone who has performed several tagging implementations in the past, I highly recommend Tag Builder v3.0 for its great usability, outstanding flexibility, and its up-to-date improvements to a robust tagging code structure.

Nestor Archival Jr.
Senior Analyst, Consulting Services
Stratigent, LLC

Tuesday, April 14, 2009

Google Analytics and Stratigent Co-host Web Analytics Wednesday

Web Analytics Wednesday is the world's largest social network for web analytics professionals. Join Stratigent and Google for an evening of networking, and a presentation on best practices and real world examples for efficiently gaining actionable insights from your web analytics data. When you arrive, please tell the person at the security desk that you are here for Web Analytics Wednesday, and they will let you up to the 17th floor.


Host: Kristen Nomura (Email)

Date: Wednesday, May 20, 2009 at 6:00 PM

Venue:Google Chicago

Address: 20 W. Kinzie Street, 17th Floor, Chicago IL (Venue | Map | Group)

Sponsor: Event sponsored by Stratigent and Google


To Register Please visit: http://www.webanalyticsdemystified.com/wednesday/index.asp?event_id=2782