The page is the most important unit of measurement on the Web site. Several metrics are based on page data (for example, pathing metrics). Additionally, many reports display data from the page name. Therefore, deploying a page naming strategy that is helpful to the Site Catalyst user most often requires forethought and planning. A good page name strategy will enable your users to maximize their use of Site Catalyst reports.

Here are some of the common business questions and objectives that can be answer thought proper use of the page Naming variables.

  • Obtain accurate page view data for baseline metrics.
  • Understand granular page flow to minimize fall-out rate.
  • Increase understanding of visitor behavior throughout Web site.
  • Acquire detailed traffic statistics on Web site.
Without questions, your page naming convention is the most important element you can define in your implementation because so many metrics and reports in Site Catalyst are derived from page name. The important aspect of page naming is determining at what level you need to understand exactly what your visitors are doing and how they are interacting with your site.

The time and effort you initially spend in developing a page name strategy is a worthwhile investment. Page names impact many other forms of analysis, such as pathing and data correlations. Well-planned page name ensure clear, more accurate data as well as enhanced and accelerated user-adoption of SIte Catalyst throughout your organization.

Site Catalyst tracks page name through the pageName variable, which is part of the standard Site Catalyst code on each Web page.
For example home page has a pageName variable set to “Omniture:Homepage”;

s.pageName = “page name”;
s.pageName = “Omniture: homepage”;

Remember the following when working with the pageName variables.
  • The pageName variable is case-sensitive, for example: “Home page” and “home page” are seen as two different pages.
  • Page names are limited to 100 characters.
  • If a page name changes, historical data cannot be easily re-assigned to the new page name. In order to facilitate the measurement of page-related trends over time, it is important to maintain consistent page names.
Note: Only first 20 characters of page name are displayed in most Site Catalyst graphs or chats.

The following section contain the various Site Catalyst page naming options.

Recommended Options: - Server-Side
Use server-side logic to populate page name for each Web page.
  • Server-side logic can be used to set the s.PageName variable.
  • Enables you to automate the page naming process and control the schema for friendly page names.
The following limitations may exist when using server-side logic to populate the page name:
  • Only applies to dynamic pages, not static HTML pages.
  • Flexibility in page naming will depend on your platform.
  • Requites some ongoing diligence to ensure that the page naming logic doesn’t break based on changes to the URL structure or new content.
Hard-coded - Manually set page name on each Web page.
  • Page names can be manually hard-coded into each Web page in the pageName variable.
  • Allows you to create a friendly page name, which isn’t restricted to what’s found in the URL or title tag.
The following limitations may exist when hard-coding the page naming:
  • Labor-intensive for IT team to implement and maintain if there is a significant number of static HTML pages.
  • Dynamic pages (ASP, JSP, CFM, PHP and etc.) cannot be hard-coded.
  • Development team must be careful if using existing pages as boilerplates; otherwise multiple pages can inadvertently share the same page name.