For business units that have several Web entities, a “global” report suite can be used to get total numbers. This can be done in two ways:

1. A “Rollup” report suite would be created by the Site Catalyst Admin at your site in the Site Catalyst Admin console. This adds up numbers from various report suites to give totals. There is no coding needed for this.

2. Multi-suite Tagging for sites that need pathing and true uniques between added report suites, you may choose to incorporate “Multi-suite Tagging” This will be decided by the business users, but you will need to do the coding. This simply entails sending the data to two report suite IDs at the same time.

  • s_account=”SiteA_ID, GlobalID”.
  • s_account=”SiteB_ID, GlobalID”.
  • s_account=”SiteC_ID, GlobalID”.
Site Catalyst support multiple currencies, so you can provide multi-currency functionality to your end user and know that it will report correctly in the reports. There are three times that you need to consider when working with currency in Site Catalyst:
  • Passing currency in (set in page or JS file).
  • Storing currency (report suite level).
  • Viewing currency (in reports).
Passing Currency
In the JS file, you can set the s.currencyCode variable to denote the currency that you provide on your site, telling Site Catalyst how to understand the revenue that enters through the product string. Example code:

      s.currencyCode = “EUR”

If you allow people to purchase items on your site in different currencies, you will want to set this variable dynamically, usually at the page level.

Storing Currency
When you set up a report suite, you have to choose a currency in which all numbers will be stored. You can, however, still allow people to purchase items in several currencies on your site. This is by Omniture on the back end. If the currency being passed in does not match the stored currency type, a currency exchange will take place as it flows into the database. This exchange rate is updated daily.

Viewing Currency
Users in Site Catalyst can choose the desired currency for revenue-based reports. If the chosen currency does not match the type being stored in the database, a currency exchange will occur at the report run time. Because currency exchange rates fluctuate, the most accurate data will available if all three currency types are the same.

Currency Format
Currencies that do not use a period (.) as the separator will have to be modified to use the period instead of any other separator. Example, the Swedish Krona, which uses a comma, will have to be modified to use a period instead of the comma. Site Catalyst uses the comma to separate different products in the product string, and if there is a comma inside of the product string’s revenue filed, it will think that a new product is being sent, and the data will not be passed in correctly. The period will correctly pass the value to SIte Catalyst.

Character Sets
Character sets determine how data is displayed in the interface. Omniture supports two different character set types including ISO-8859-1 and UFT-8. Languages with similar characters such as English, Spanish, and French use ISO-8859-1. Languages that use other characters use UTF-8. Any languages that are not in ISO-8859-1 or UTF-8 are contained in the Shift-JS format, but since Omniture does not support Shift-JS, Site Catalyst uses the charSet variable to convert any characters in Shift-JS format to UTF-8. The following sample code shows an example of how the charSet variable is populated.


If the charSet variable contains an incorrect value, the data in all other variables will be translated incorrectly. If JavaScript variable on your pages (e.g. pageName, sprop1, channel) contain only ASCII characters, charSet does not need to be defined. However, if the variable on your pages contain non-ASCII characters, the charSet variable must be populated.

NOTE: Standard report suites use ISO-8859-1, while multi-byte report suite use UTF-8. Multi-byte support is enable by Omniture Live Support.