Considering All Options
Once the business objectives are clear, you can take those objectives and map them to Omniture products, features, functions, variable, etc. Be sure to explore all the different options, understand the differences in those options, and choose the best solution for your site. There are often multiple ways to get the same kind of information, but there are sometimes subtle differences in the outcome.

Some example questions you can ask yourself in this regard include:

  • Is this Traffic-based objective?
  • Can we answer it using s.props?
  • If not, what else do we need? (VISTA, ASI, Discover, excel, etc).
  • Is this a Conversion-based objectives?
  • Can we answer it using eVars?
  • If not, what else do we need? (Classification & SAINT, Conversion breakdowns, etc).

The next step is to identify your variable use. By understanding what the Omniture variables do, you can more easily implement them. You should map out and DOCUMENT (ALWAYS DOCUMENT) your variable use.
  • = Parent content category (page groupings).
  • s.prop1 = Page subcategory.
  • s.prop2 = Internal search terms.
  • s.eVar1 = Merchandising category.
  • s.eVar2 = Internal search terms (mirror of s.prop2).
  • Even1 = New Subscription.
Another important question to ask when you are mapping the variables out is:
      Can these values be referenced when needed?
This could be broken down into specific questions, such as these examples:
  • At the page level do I know the content category and sub-category?
  • For any given visitor can I determine the segment such as register vs. non-register?
  • Based on your site architecture, how best can I put events onto the appropriate page?
For example, it doesn’t do any good to map a variable to the “Age” variable if you don’t ascertain the age of the site visitors. So make sure that you can ge the information that you are planning to put into the variable.

The next logical step is to figure out how you are going to get the values that you need into code on the page. Common solution include:
  • Server-side scripting (PHP, JSP, ASP).
  • Client side scripting (JS).
  • Hard code values.
Although the architecture of your site will dictate how you will likely code your Site Catalyst variables, it is also sometimes a variable-by-variable decision. For example, you might be able to pull a value from the URL for one variable, while you need to query a database for another variable’s value.

In any case, the onus is, of course, on you to provide quality values into the variables. You may contact Omniture Consulting for some suggestions and best practices in this regard.

Omniture provides several options for self-help. Those that can help you the most during your implementation process include:
  • Site Catalyst Implementation Manual.
  • On-demand Training Modules.
  • Online Knowledge base (White paper, Common questions).
In addition to the self-help options, you should have al least two users at your company that are set up as “supported users” and can call or email for help from Omniture Support. If you would like more help implementing Site Catalyst, you may also engage on Omniture Technical Consultant. Please contact your Account Manager for more information.