Here’s the first of our articles to help you get your head around the building blocks required for Adobe Reports & Analytics (formerly SiteCatalyst).
There are a few ways to find out the order in which certain events happen when visitors come to your site, but the most effective is through implementing Success Event Pathing. We take you through the process of successful event pathing.
Well, it’s August and true to their word, Adobe upgraded us to SiteCatalyst v15 on the 1st, and so I thought I’d share a few of the golden nuggets within v15.
I was thinking about how to order them…do I go by not bad to flamin’ eck, that’s awesome? Or start with the big bang and then let it continue to smoulder throughout?
The problem is there are too many new and great features that you can’t really put them in any type of order. They appeal to you on different levels, from functionality, to UI, to analysis, to reporting, to combination segmentation and sub reporting.
So, following a recent “back to basics” post, a reader requested that I write something describing how custom traffic props are actually useful. How about customer segmentation achieved through traffic props?
Custom traffic props are used for counting traffic-based activity, to gain insights into user behaviour across our sites. By default, custom traffic props only come enabled with the metric Page Views, which, by itself is, admittedly, not a lot of good. But, with a couple of minor customisations, you can get valuable insights from the props very quickly.
This post is actually about customer segmentation – in our case measuring student activity versus staff activity versus “anonymous” activity. In your case, it’ll probably be customers vs. non-customers. But, you don’t have to stop at the customer vs. non-customer segments either. There’s plenty of other customer segments that you can apply throughout the brand funnel, as they move from being just a browser to a high value loyal customer.
Read on to find out more about enabling customer segmentation.
One of the fundamental things you need to understand about Omniture SiteCatalyst is the difference between an s.prop and an eVar, and just what events are and when to set them. They are at the heart of the product and provide the ability to customise it to suit your business needs.
If you don’t understand the difference, you’re going to be in a world of pain, and left dazed and confused.
This is, understandably, the most confusing thing to new SiteCatalyst users, and they take a bit of getting used to, especially when you start to combine them all together, but once you understand them, you’ll be on your way to generating custom ones that can really provide insight. Hopefully this post will help out in some small way.