Sep 18 2008
Your answer should be, “we don’t.”
Path analysis is bunk. Why do analytics vendors spend so much time on path analysis reports and tools? Taken in context, *some* of the pathing tools can be useful, but giving us a tree diagram of complete paths is completely useless, in my opinion. What does it tell you? Absolutely nothing.
What makes it even more frustrating is how *pretty* the darn tree diagram reports are. Never show this report to anyone! Otherwise you’ll be getting requests for path analysis reports and will end up wasting your valuable time when you could be analyzing your 404 or most popular page reports!
Do you have conversations with your colleagues that go something like this:
Them: “Can we see how people are navigating through the [enter degree name here] section of the website?”
You: “Uh … (knowing full well where this is going) … yes … can you give me more specifics?”
Them: “Like the paths they are taking.”
You: “What exactly do you want to know?”
Them : “If they’re actually reading our application instructions before filling out the application.”
You: “Sure, we can do that.”
And then you say to yourself, “there are other ways to look at that, not path analysis.” Good, good. Go with that!
The trick to using alternative reports to get at your “path analysis” questions is to focus on *exactly* what you want to know. In this case, if the user is reading the application instructions before filling out the application. We’ll get into specifics later, but for now …
Let’s talk path analysis. So what the heck is “path analysis” anyway? It’s basically analyzing the paths your users take throughout your website. The ridiculousness of path analysis might seem obvious to those of us who have been deep into web analytics for a while. For those people just starting out with analytics (or not involved in using them at all), path analysis might still seem like a great idea … at first.
Think of pathing this way, though. How do you make your way through a website? How many times do you use the back button? How many times do you search for a page instead of using link navigation? How many times do you go back and forth between 2 pages?
Now, make believe you are tracking 20 people, just like yourself, through your site. What insights can you possibly get from their exact paths? Not much. Will any of those paths be exactly the same? Probably not. Why? There are simply too many variations. Too many options:
- User A Path: Landing Page (from search engine) –> Page 1 –> Home –> Page 2 –> Page 3 –> Exit
- User B Path: Home –> Page 1 –> Page 3 –> Home –> Exit
… and those are the most simplistic I could think of right now.
Another layer. Keep in mind that (depending upon your site, of course) more than half of your visitors land on your site at a page *other* than your home page. This adds another layer of complexity.
What questions might we feel compelled to answer by the path analysis report:
- We want to find out if people are taking a particular path through the site.
- We want to know what “related degrees or certificates” users are looking at. For instance, are users that are visiting our MBA pages also visiting our Masters in Project Management pages?
There are many ways we can gain insights into two situations without using path analysis. Let’s get specific.
Finding out if people are taking a particular path through the site. Ask yourself this, “what particular path do you want to analyze?” Focus your question to one path. We can do that … and it’s relevant and actionable! It’s called a conversion funnel, goal, or similar depending upon what analytics tool you are using.
For Google Analytics users, here is a tutorial on setting up goals. For Omniture users, use the PathFinder report. For a funnel with more than 3 pages, use the Fallout Report Builder. Remember the example I gave in the beginning of this post? Use the goal/funnel report to see if users are reading your application instructions before starting the application.
Finding out if the users who are visiting our [enter degree name here] pages are also visiting our [enter other degree name here]. Many analytics vendors allow you to set up “sections” of the website. So, logically, you can set up a “section” for all MBA pages and then a “section” for all Masters of Project Management pages. This is fantastic for segmentation purposes. But, don’t get sucked into creating pathing reports for sections. Just like page pathing reports, there are too many options so I can’t see this report having any sort of actionable data to offer.
Instead, how about this … do you have a “request more information” form? Is there a place to select *multiple* programs of interest? How about analyzing that to see the possible “related” programs? Wouldn’t that give you much better data and more actionable data than would trying to figure out pathing options between sections of your website?
Remember that the when you’re feeling compelled to use path analysis and you’re asking yourself questions like, “what paths do users take through my website,” force yourself to give a *specific* example – ” Do users take the specific path from page 1 –> page 5 –> page 6?” You’ll get so much more actionable data out of answering that specific question than wasting your time on a vague, non-actionable question like, “what paths do users take through my website.”
Focus. Don’t waste your time on reports (even if they’re pretty!) that tell you nothing.
Footnote. I must thank Kyle James for (unknowingly) giving me the idea for this post. While reading his great post about why pageviews is not a quality metric (which I totally agree with), it got me thinking about other metrics and reports that are pretty much worthless.
3 Responses to “Why Do We Care About Path Analysis?”