Jason Egan

Site Optimization, Web Analytics & Social Media

Web Analytics

Programming and Web Analysts

Now that Omniture has APIs and WebTrends is doing more sophisticated things with their tools that have ODBC connections, I was thinking, should we Web analysts consider adding to our skill set? Primarily, should we begin to add programming abilities to our skill set? Things like APIs are great, but only if you have the ability to create applications that access these APIs. Should we Web analysts start learning languages like PHP, SOAP and XML so that we can create our own applications?

Also, most popular Web analytics technologies are based upon JavaScript (from the implementation side anyway). So, a better understanding of JavaScript would most likely benefit us all. A better understanding of JavaScript alone could open some doors for better Web analytics opportunities for those not already proficient with JavaScript.

I think that we Web analysts should be immersing ourselves in programming so that we become more than just analysts and the users of tools like Omniture, GA, WebTrends, etc. I for one will be trying to pick up the following skills in 2009:

• PHP/SOAP - for the purpose of programming with Web APIs and creating new applications for analytics and online marketing
• JavaScript - I’m already decent with JS, but would like to be able to do some more advanced things for analytics
• SQL/MySQL - for the purpose of querying Oracle, SQL and MySQL databases

Are their any other skills that you think would benefit Web analysts? What additional skills are you trying to pick up on your own this next year?

---

Omniture Dashboard Speed & Dates

This post is just to note a couple of things that I have discovered recently about Omniture dashboards. I hope that this might be of help to some of you that use Omniture.

Faster Omniture Dashboards

File this one under what is most likely common sense. But, I have seen many Omniture SiteCatalyst dashboards take forever and a day to run, or you will see the “unable to retrieve data” message. I at first thought that this might be due to the fact that I had seen this most often on dashboards for Omniture variables that were using 20 - 30 classifications. Maybe using that many classifications slowed everything down? But no, it was really just because of the number of metrics that we had for each reportlet. I tried recreating dashboards with only revenue, and voila, the dashboards ran in no time. The down side here, is that a dashboard is only so useful if it has a single metric. If you are experiencing problems with slow dashboards, you might want to try and reduce the number of metrics in your reportlets (maybe to just two or three) until it runs in a reasonable amount of time. The addition of calculated metrics is also a significant factor in slowing down or killing Omniture dashboards. Of course if the dashboard is automated via email, you can add everything you like, and the whole thing will get emailed perfectly fine.

Omniture Dashboard Dates

Just another Omniture dashboard experience that I thought I’d share. We have several dashboards that are setup so that each reprotlet might be reporting on ranked data for the last 30 days. Last 30 days was chosen since a current month would not be all that useful on the first of the month. One of the great advantages to dashboard in SiteCatalyst 14 (as opposed to earlier versions), is that you can change the date for all reportlets in a dashboard at the same time. This makes the dashboards much more useful. So, someone requested the executive dashboard for a custom date range. Knowing that you can do this in SiteCatalyst 14, I changed date range to the custom one requested. Everything ran great, so I sent the dashboard to the person via the email function within SiteCatalyst 14. However, the dashboard that the person received was stuck to the default of last 30 days in which the dashboard was originally created. So, just be aware that while you can change Omniture dashboard dates to custom ranges, the email results will be the default of the dashboard in the way that it was created. I confirmed this with Omniture, and it is not a bug, but just the way it was designed.

---

New Google Analytics Features - First Impressions

So I have access to the new updates to Google Analytics now. My first impressions of the updates are very positive. The two big additions (aside from the API) are the custom reports and segmentation.

The custom reporting actually went a little beyond my expectations. The big thing here that Google has done is that you can create reports that are very deep (4 levels or so) and that you can correlate across different report dimensions easily. Now Google just needs to implement more variables and events to take this to the next level.

The segmentation works well too, but it’s a little clunky in it’s setup. Here, I like the buckets that you start with in Omniture’s Discover. The creation of a segment seems a little more intuitive when starting from the idea of a visitor, visit or page view.

I do think that with the additions of the custom reporting and segmentation that Google has become more of a serious option for larger businesses. 

---

Omniture Launches Developer Connection & Discover API

Okay, I’m not trying to make this an Omniture blog, but they keep releasing products/services and acquiring companies at startling rate the last few weeks. That being said, I received an e-mail from them this morning about launching a beta of something called the “Omniture Developer Connection.” At first glance, this appears to be just a repository for documentation on Omniture’s Web services. One BIG thing that I did notice, is that:

There is now a Discover API and accompanying documentation!

This is great to see, and I hope that Omniture gives some more attention to this new API. I would like to automate some Discover reporting, and an automated CSV file isn’t the most elegant way to accomplish it.

This site (that requires Omniture login credentials) also contains forums for developers as well as a library of code examples that can be contributed to by developers. Right now though, there are no posts in the forum (aside from the admin) and there’s only one code example.

Here’s the announcement e-mail from Omniture:

Announcing Omniture Developer Connection (BETA) 

The Omniture Developer Connection is here—a community Web site designed to help our customers build applications  that use their Omniture data. Found at http://developer.omniture.com, the Developer Connection allows our customers to:

• Use Omniture SiteCatalyst data across third-party applications, such as an intranet or a company-branded application
• Access SiteCatalyst reporting data to create calculated metrics, or format the data to meet specific internal needs
• Use the data collection API to facilitate the integration of SiteCatalyst with applications that cannot be easily tagged with JavaScript

In addition, Omniture Developer Connection contains:

• Documentation of Omniture’s application programming interfaces (APIs)
• Sample code showing reference  implementations to give developers a head-start in developing their own applications
• Discussion boards and blogs to provide peer-to-peer support among those building Omniture-driven applications

Please pass this along to the appropriate development team within your organization. For additional detail on the Developer Connection, a list of Frequently Asked Questions is provided below: 

1. When is the Developer Connection available?
Omniture will be releasing the Developer Connection in beta on October 17, 2008.

2. Who can access the Developer Connection?
The Developer Connection and Omniture APIs are accessible to Omniture customers with a SiteCatalyst login.

3. What are the Omniture APIs?
The Omniture Web Services API provides programmatic access to Omniture SiteCatalyst administration, data insertion, Omniture Data Warehouse and reporting functionality. The Web Services API is built using SOAP, which allows developers to use any SOAP development toolkit to start developing applications. The data insertion API is built on an XML-based schema, allowing developers to easily and quickly send data and begin testing integrations with the system.

4. How do I access the Developer Connection?
Customers can use their SiteCatalyst login information to access the Developer Connection at http://developer.omniture.com.
 
5. What is the best way to start using Developer Connection?
A Getting Started guide (for users with a SiteCatalyst login) is available to assist new users through the process of learning the prerequisites, enabling the Web services APIs, and testing and authenticating newly developed applications. The guide is available under the ‘Getting Started’ tab in the portal.

6. Does Developer Connection include API documentation for all products in the Omniture Online Business Optimization suite?
Currently, API documentation is available for SiteCatalyst, DataWarehouse, Discover reporting, and SearchCenter. Additional API’s will be added in the future. 

7. How should Beta participants provide feedback regarding the Developer Connection portal? 
We will be monitoring the community blogs and message boards and encourage customers to provide us feedback there. 

Sincerely,

Your Omniture Team

---

Omniture Acquires Mercado

I received an e-mail this morning that Omniture has acquired Mercado, one of the largest players in on-site search. The funny thing here is that Omniture has only recently started selling the rebranded VisualScience product (which was formerly a WebSideStory product) for site search. I am guessing that Omniture will take the same direction here as they have with their Discover product, making the VisualScience product a “lite” version compared to their newly acquired product from Mercado. Here’s the e-mail Omniture sent this morning making the announcement:

Update:

I’m hearing on Twitter that this was a bit of a fire sale (http://twitter.com/jbillingsley/statuses/959067564). It also looks like Mercado wasn’t doing so well and that the software-as-a-service business model wasn’t helping the issue (http://www.startupisrael.com/mercado-shutting-down). I know that Omniture uses the same basic business model, but they also have the advantage of a huge customer base.

---

Creating an Action-Oriented Culture

Most experts in Web analytics dream of working for a business that makes data-driven decisions. Look at it as justification for our career choice. However, I think that this needs to be taken a step further:

We should be concerned with creating an action-oriented culture, not just a data-driven one.

Having access to advanced Web analytics tools, we can churn out meaningful analyses that management will most certainly use in making decisions. So, that means that we work for a data-driven company, which is a great thing indeed. The missing thing there is that the information isn’t nearly as useful if no action is ever taken. This can also be very defeating for people in Web analytics. No one wants to feel as though their hard work is never put to real, visible use.

So what can we do to help create an action-oriented culture when we don’t have direct control over resources and priorities?

Start A/B Testing

This is a slam-dunk, since action is one of the first steps here, and the payoff is pretty quick to see. Once you can get your company to buy into A/B testing (don’t worry about multivariate yet), more tests will follow as the return on investment becomes evident. Start easy with only A/B tests, where “B” is very different from A (to ensure meaningful results) and try out a tool like Google Website Optimizer (free) to help make ROI justification easier.

Focus on Change

Everyone delivers dashboards and standards reports. As I’m fond of pointing out, these eventually get ignored with all of the other noise that exists in inboxes. If you want people to stand up and take notice, and eventually act, then you’re going to need to get a little more manual and really dig into the “why” of your data and information. Like it or not, we Web analysts don’t know everything that marketing, Web design and the other teams on our site are doing. So, instead of just delivering dashboards on a regular basis, we need to start tracking significant changes in metrics, investigating with the necessary people, and finally delivering an intelligent analysis on the “why.” In addition, we need to make efforts to be more in the loop with all of our online efforts to understand and provide analysis on the efforts that are not making any significant changes on our site(s). After all, why waste effort on something that doesn’t even move the sales needle?

Understand Your Customer/Visitor

I just mentioned how important it is to understand the “why” in why things are changing or happening on your site. While traditional quantitative analytics is great, we must supplement our data with qualitative data. We must also do this at the visit level so that we can correlate the “why” to what visitors actually did (or did not do) on our site. If you can start to get survey input from your site visitors, then you can put some real, hard evidence that action needs to be taken and put it in front of the right people. These people might find it a little harder to not act on information from a person that has a proven purchase or visit history with your Web site. While there are a lot of survey solutions out there, you should at least start with something free like 4Q, which was created by Avinash Kaushik and iPerceptions. You may not be able to get the answers to the 4Q survey related to your transactional data (hey, it’s free!), but it’s a starting point in gaining qualitative knowledge about your visitors/customers.

Do you have any other ideas as to how data and information can spur action?

---

Why You Should Be Using Omniture Discover

This of course only really applies to current Omniture customers or those thinking about moving to Omniture as a new customer. I’ll also preface this further by saying that I am on Omniture’s Customer Advisory Board (CAB) for Discover (On-demand).

Anyway, there are several reasons that you should be using Discover and several reasons why you need it in addition to the normal SiteCatalyst offering.

Reasons why Discover is a good supplement to SiteCatalyst Include:

• SiteCatalyst’s power is in providing reports and delivereing those reports and dashboards on a regular basis. The power of Discover on the other hand is to enable you to perform true exploratory analyses.
• SiteCatalyst has limits in terms of how far you can drill down into data, and also limts in what you can drill down to. In Discover, you can drill down to anything, as deep as you like.
• Drilling down in SiteCatalyst only works from the moment it’s enabled, and is not retroactive. In Discover, everything can be drilled down to, and everything is retroactive. So if you think of something that you’d like to look at a few months ago, you can. Everything is retroactive from the moment you enable Discover though, not before.
• In SiteCatalyst, you can segment anything by using what are called ASI segments. However, ASI segments aren’t flexible enough that you can easily change the segments definitions themselves in the middle of an analysis. In Discover, you can change segments on the fly with a simple drag-and-drop.
• Omniture Data Warehouse can deliver segmented data to you, but can take 1 – 3 days to do so. In Omniture Discover, you will get your data in just a few seconds. This allows you to see the results of segmentation quickly so that you can know how to best craft a Data Warehouse request for large dumps of data.
• There is no additional implemenation for Discover. Once it is enabeled, all of your reports are ready to go.

So these are some of the reasons that Discover can supplement your use of SiteCatalyst.

So what are the things that you can do in Discover specifically that make it a great tool for deep analysis?

• Dashboards and regular reports are often and eventually ignored. Deep analyses of segmented data allows you to create presentations of informaiton that most others will not have access to.
• Quick creation of segments . Why look at just every visit on your site, when you can look at:
  • First time visits
  • Return visits
  • Visits that include certain pages on your site
  • Visits where your help content is viewed
  • Visits where no purchases are made
  • Visits where people fallout of your purchase funnel
  • Visits where people used internal site search
  • And many more…
• Omniture Discover is fast. When starting Discover (a Java application), it imports a data set. Once that’s imported, you need only wait a couple of seconds for anything to run. When using a Web-based application (as are most Web analytics solutions), you have to make a request of a server, the server gets the data that you need and then you are delivered the information in your browser. This can leave you waiting for a report until you are frustrated.
• If you are running A/B and multivariate tests, Discover will let you analyze test results in a deeper way that can make determining the winner more clear-cut.
• After SiteCatalyst has all of your reporting and dashboards built out, Discover is the tool where true Web analysts will work on a regular basis.

If you have any specific questions about Discover, let me know. Also, if you are already using Discover, do you have any particular segments or analyses that you like to look at on a regular basis? Any tips or tricks of your own you’d like to share? Leave a comment and share anything that you have!

---

The Economy and Web Analytics Jobs

A lot of people have lost their jobs over the last few months, and a lot more probably will. Most people in analytics know that there is more demand for skilled Web analysts than there is supply. So, would you say that experts in analytics have recession-proof jobs by default?

I keep seeing a lot of articles and content poping up on the Web about recession-proofing your job. Most of them say that you need to appear indespisible (perception is reality, right?) as well as be more of a jack-of-all-trades. Here’s a podcast from Harvard Business Review on this:

Harvard Business IdeaCast 110: How to Protect Your Job in a Recession

What can Web analytics people do to recession-proof themselves?

As I see it we can do several things at least:

1. Constantly (and I mean almost daily!) turn out ideas to improve your company’s online presence
2. Present to management often (to increase your visibility and the perception of being indespensible)
3. Speak at conferences (analytics or otherwise) and become better know in your company’s own industry (unless the bad economy has resulted in your travel budget being shot!)

One other thing that you can do to recession-proof your job is to keep some information close to the vest. That is, don’t run out and tell everyone in your company how to do everything that you do. If you document exactly how to do all of the technical aspects of your job, this might also hurt you in recession-proofing your job. I can’t say that I really agree with everything here about not sharing things about your job skills, but I’m just throwing it out there as something that we all know is done in reality.

Do you have any further ideas as to how people in Web analytics can help themselves in recession-proofing their jobs in this economy?

---

More on Pages Not Being Worth Anything

Followup to “Pages Aren’t Worth Anything” from Jason Egan on Vimeo.

This is my first attempt at a video post here, so this might be a little rough. They should get better though!

Summary:

• Pages aren’t worth anything, but what you’re selling is.
• Testing and optimization should replace analytics in determining how effective a page is at conversion.
• You should me optimizing and measuring the worth of your marketing accumen as opposed to some HTML. Look at a page or site this way. It is a marketing and sales tool. How good is it at marketing and selling? How good are you and making the site better at marketing and selling.

---

Your Pages Aren’t Worth Anything

I’m sure that some of you will disagree with the title of this post as soon as you see it, but hear me out (read me out?). Wether you are in publishing/content or straight up e-commerce, your pages are not making money inherently. Many executives and busines owners always have one of the two following question:

1. “How much revenue has this page made?”
2. “How well is this page converting?”

To preface the rest of this post and explain the title of this post, I am going to say that pages do not make money, and they do not convert. Crazy, I know. But, what does make you money and convert are the changes that you make to your pages.

Answering, “How much revenue has this page made?“

 

I do not want to turn this into a debate about revenue attribution at the page view level, so I will leave that issue for another time. So let’s just assume that you have some kind of repor that has page names and dollar amounts next to those pages. The answer to the above question is:

“Does it matter what that revenue number is if you aren’t changing anything?”

So you can trend a page’s revenue over time. So what? Let’s say that you sell hair dryers (why was that the first thing that popped into my mind?). Your sales of hair dryers are what make you money, not the view of some page on your site. Afterall, you are selling hair dryers, not page views.

I also want to take this opportunity to address the publisher/content sites out there. News flash, you are selling something! Your selling ad views, and video ad plays, not page views or time spent (or “engagement” of all silly things).

You should not be asking how much a page makes for you. You need to be coming up with ideas that you think can make a page better, and testing those ideas to see if you can create lift! A page that just sits there and is never, or blindely changed isn’t doing you any good. Does it really matter how much you think a page makes over time if you’re not trying to make it better to begin with?

You changes, improvements and efforts make money and create lift. A page sitting there isn’t doing you any good.

Answering, “How well is this page converting?“

 

Again, I would say that a page just sitting there is never converting any different that it ever has, so tracking the conversion rate of a page is pointless. You should be tracking how good YOU are at making changes that improve conversion.

Lift is as Important as Revenue and Conversion

 

Just like I feel that “engagement” is an excuse on the part of publisher/content sites, I feel that tracking how much a page makes or how well it converts is an excuse for not testing your pages and working on creating lift. If you really care how much a page is making or how well it’s converting, then you should have a hypothesis as to how you can make it better, and you should test that hypothesis to create lift.

---

Powered by Wordpress | WP Premium theme by WP Remix
Copyright 2007. Jason Egan. All rights reserved

• Home
• About Jason
• Google Analytics Resources
• Resume