Omniture offers some best practices defined here as a tool to help you successfully implement Site Catalyst as quickly and effectively as possible. The following topic will be discussed:

  • Understanding terminology.
  • Dos and don’ts.
  • Asking the right questions.
  • Considering all options.
  • Identifying variable use.
  • Populating variable values.
  • Where to get help.
  • Design Solution Project.
To this point, we have described the Site Catalyst implementation and other useful tools. Omniture offers the following recommendations as best practices to follow during th e implementation process.

The Glossary in the Site Catalyst User Guide and the offer terms that are commonly used both in Site Catalyst and in Web analysis in general. Both the technical and business teams at your organization should become well-versed in the lingo used by Omniture and in the Web analytics industry so that they can communicate effectively not only with each other, but also with Omniture.

The terminology could be grouped into three areas:
  • Roles This one is probably pretty easy, because it mirrors what you already have in place, but some of the roles involved with Site Catalyst could be Executive Sponsor, Project Manager, Business Lead, Technical Lead, and Analyst.
  • Metrics and Reports You should also be familiar with the names of the metrics and reports used in Site Catalyst and in the industry, and know how they are best used. These include Visit, Unique Visitor, Page View, Exits (Exit Pages), Time Spent per Visit, etc.
  • Features and Functions It is helpful to be familiar with the different features and functions that are available in the Site Catalyst and other Omniture products. These include pathing, Data Warehouse, Omniture Search Center, etc.
Here are some helpful hints as you implement Site Catalyst:

Do ...
  • Make sure your page names are well planned and discussed.
  • Call things in the right order-especially with H code.
  • Verify the outcome with the Debugger tool.
  • Establish global standards for incorporations across the enterprise.
  • Perform a troubleshooting investigation prior to calling Omniture; describing what you have tried expedites solutions.
Don't ...
  • Deploy Site Catalyst code without talking to the report consumers. In order to get ANY value from the Site Catalyst implementation.
  • Values in reports must be understandable to those running reports.
  • Business issues must be solved by collecting the right data.
It is very important that you understand the business objectives before attempting to map them to variable. Make sure that you clarify any business needs. This is the old “measure twice , cut once” rule. It is much better to veri fy multiple times what the business user needs before coding the page. This will help avoid a “useless” report later that doesn’t contain the requested information.

For example, if a business requirement came through simply to “track content channels,” you would need to verify exactly what the users need to know. Some clarifying questions might include:
  • Do you need page view, visits or visitors for those content channel?
  • Do you need to know how people path between those content channels?
  • Can you give me example on our site of the content channels you are thinking of?
  • How granular are these content channels? Do they follow our site navigation?
In addition, make sure that you align your terminology with the person who request the information. For example, make sure that “visitor” means the same thing to you as it does him or her. Don’t ever assume that you know what they mean. Ask questions!