Like any software product you use, there are a few key elements that you need to understand to be successful.  In working with clients I have found that many do not have a good understanding of the three fundamental building blocks of SiteCatalyst: sProps, eVars and Success Events.  When I was an Omniture client, I will admit that I had much more important things to do with my time than to learn about Omniture’s variable types and their capabilities.  However, over time, I came to understand that these variables are the foundation of all SiteCatalyst reporting, so if I wanted to use Omniture reports to measure my website success and/or justify my re-design theories, I had better suck it up and learn about these three variable types.  I hope you will do the same.  In this post I will review sProps and will cover the other two types in my next posts.

Traffic Variables
Traffic variables (known to old-timers as sProps) help to track page-by-page site traffic activity.  Site Traffic is normally measured via Page Views, Visits or Unique Visitors.  The primary purpose of sProps is to allow you to breakdown Page Views, Visits and Unique Visitors into meaningful buckets.  While SiteCatalyst provides reports to see total Page Views, Visits and Unique Visitors for your site, most web analysis needs to take place at a much more granular level.  Without sProps, you would not be able to see such things as which pages are the most popular or what percentage of pages were viewed in the USA vs. Canada, etc….  The following is an example of the most commonly used sProp report, the Most Popular Pages report:

Not Persistent
An important thing to know about sProps is that they are not persistent.  This means that they do not retain their value from one page to the next, a concept that often confuses Omniture customers.  I find that the easiest way to understand sProps is to think of the most commonly used sProp: Page Name.  Let’s assume a visitor to your site starts their visit on the Home Page and the value “Home Page” is passed into the Page Name sProp.  From the Home Page, the visitor clicks on a link and is taken to the “Contact Us” page.  You would certainly not want the value of “Home Page” to persist and be passed into the Page Name sProp on this next page or it would look like the Home Page had two Page Views instead of each page having one Page View.

Pathing
Another important thing to know about sProps is that they are used for Pathing. Pathing is the ability to view the order in which values are passed to a particular SiteCatalyst sProp for a specific Visit.  For example, let’s say that each page on your site has a pagename and the values passed to the Pagename sProp are Page A, Page B, and Page C respectively.  If Pathing is enabled for that sProp, SiteCatalyst would record the order in which the values were passed and allow you to view reports that show the percentage for which all site users went from Page A to Page B, etc…  I will definitely be talking more about Pathing in a future post.

Did You Know?
The following additional items related to sProps are worth noting:

  1. Visits, Daily Unique Visitors, Weekly Unique Visitors, Monthly Unique Visitors and Quarterly Unique Visitors can be enabled for any sProp (for an additional fee)
  2. SiteCatalyst provides several “out-of-the-box” pre-defined sProps including: Pagename, Site Section, Server, Browser, Country, etc…  These are similar to all other (custom) sProps with the exception being the Pagename sProp which is somewhat special in that it captures the page URL if no value is passed to it.
  3. Any two sProps can be “correlated” or broken down by each other
  4. Pathing can be enabled for any sProp
  5. Any sProp can be “classified” using SAINT

Real-World Example
In every post I will attempt to provide a real-world example of the topic at hand.  Let’s say that we are working for Greco Inc., an Omniture SiteCatalyst customer that owns several different types of web properties.  One of Greco Inc.’s web properties has a translation utility which allows each page of the site to be viewed in either English or Spanish.  The CMO is working on a marketing campaign targeting Hispanic customers and, as such, would like to get a feel for the percentage of all site Page Views viewed in Spanish.  To accomplish this, the client would pass the language that the current page is being viewed in to a custom sProp.  For best results, this sProp should be populated on every page so that the total Page Views in this report matches (or is close to) the overall number of Page Views for the same timeframe.  Doing this might produce a report that looks like this:

Thus, by using a custom sProp, Greco Inc. now has a new way to breakdown Page Views and can answer the specific business question at hand.

Have a question about anything related to SiteCatalyst?  Is there something on your website that you would like to report on, but don’t know how?  Do you have any tips or best practices you want to share?  If so, please send me an e-mail at insidesitecatalyst@omniture.com and I will do my best to answer it right here on the blog so everyone can learn! (Don’t worry – I won’t use your name or company name!)

13 comments
srilakshmi
srilakshmi

Hi, recently we did page views, event tracking and getqueryparam on url params( s.eVar). but is there any way that I can see url params and visits and page view on a single report?

Gautam Choudhary
Gautam Choudhary

Hi Adam, Wonderful post.You have done this in such a simple manner that i am now quite clear in the variable use.Thanks So much.Keep posting. Cheers!

Sreeja
Sreeja

Wonderful post.....lots of my questions were answered. Looking forward to more such posts.....

Devender
Devender

Hi Adam, Thanks for sharing your awesome insights. I have what may sound like a dumb question -- how do the s.props get populated? I'm hoping like the SAINT file, there's another file that the beacon pulls all the prop info from? Many thanks for you answer in advance! -Devender

Ben Gaines
Ben Gaines

Mayank: Unique Visitor metrics for Custom Traffic variables work because SiteCatalyst is able to tie together the various page views and link clicks that occur for each visitor using a single persistent cookie. The Custom Traffic values themselves are not stored in a cookie, but the visitor will pass the s_vi cookie on every page view, and the value contained there functions as a key which allows SiteCatalyst to recognize when disparate page views and link clicks belong to a single visitor. Thus, the tool can identify when a single visitor has "seen" a certain Custom Traffic value, and assign it a Daily Unique Visitor, Weekly Unique Visitor, etc. in the Custom Traffic report. Thanks! Ben Gaines

Mayank
Mayank

Adam If s.prop use non persistent cookies, how will it track unique visitors. Suppose, a visitor is coming after two days, with non persistent cookies omniture will take as a new visitor.

Ben Gaines
Ben Gaines

Hi Brett. There is definitely a way to do this. You would want to use the getQueryParam plug-in to capture the value of the query parameter (MkCpgn=) and pull it into a SiteCatalyst variable. You would then probably want to write the value to a cookie which could be read on subsequent page views in the visit and would then expire. You can get the getQueryParam plug-in from within SiteCatalyst by going to Help > Help Home, then Supporting Docs > Plug-ins.

Mac
Mac

Great post. I liked ur example which help me to understand about the functionality. Looking forward for some more post.

ccardillo
ccardillo

Great information, as well as the Conversion vars posts. Very helpful for me and my team. Keep these coming!!

anil
anil

Adam! Great to see you blogging here! I had great learning experience in your sessions at omniture summit. I look forward for more posts from you! Cheers

Mike
Mike

Great stuff and focusing your attention on teaching some advanced techniques is a great idea. I look forward to reading many more post.