The configuration variables that are typically set in the main JavaScript file are as follows:

  • s_account.
  • currencyCode.
  • charSet.
  • trackDownloadLinks.
  • trackExternalLinks.
  • trackInlineStats.
  • linkDownloadFilters.
  • linkInternalFilters.
  • linkLeaveQueryString.
  • linkTrackVars.
  • linkTrackEvents.
These variables could be set on each page, but are normally included with the JS file. Some of the goals and objectives of using these configuration variable are:
  • Track multiple sites / domains.
  • Use any currency on purchases.
  • Capture data in different languages.
  • Link Tracking.
  • Track the number of downloaded files.
  • Track links to external sites.
  • Track custom links for uniques purpose.
Each of these variables is described in the following section.

Omniture Support creates report suite names and IDs. The report suite ID is the value added to the s_account variable. When data is sent to the collection servers, the report suite ID are used to determine where to populate the data in the collection tables. The report suite name is basically the user-friendly name that displays in the Site Catalyst interface.

The account (report suite) can be specified be server code on page, but usually is contained is the .JS file. The following sample code gives a good example of how the s_account variable is used.

     var s_account=”omnituretraininglive”

In this case, the report suite ID is omnituretraininglive”. These IDs are created by Omniture, but then applied to the JS file by the client.

You can also set the s_account variable dynamically by using the following steps and configuration variables:

1. Turn on the functionality:

2. What part of the URL should make the decision?
Match on domain, path, query string, or combination: (domain by default)

3. Map the [domain] value to the report suite ID.
If none match, default to s_account:

More information about using these variables is available in the Site Catalyst Implementation Manual.