Insert
the following code to the end of the <BODY> section of each
page of interest, right before the body close tag, </BODY>.
After the setup has been completed, data collection takes place in
each tagged page by virtue of the call to st_init() that is made in
the JavaScript.
01 <script language="javascript" type="text
/javascript" src="http://ccs.domain.com/sastag/SASTag.js"></script>
02 <script language="javascript" type="text/javascript" src="http:
//ccs.domain.com/sastag/SASSiteConfig.js"></script>
03 <script language="javascript" type="text/javascript">
04 function st_pageCfg {
05 // Place configuration values here
06 }
07 function st_pageDats {
08 // Place data values here
09 }
10 </script>
11 <script language="javascript" type="text/javascript" src="http:
//ccs.domain.com/sastag/SASTagDebug.js"></script>
12 <script language="javascript" type="text/javascript">
st_init();</script>
13 <noscript><img src="http://ccs.domain.com/sastag
/SASTag.gif?JS=0$URI=/TagsDisabled" border="0"></noscript>
Before
you insert the code into your pages, you must ensure that the protocol
and domain
http://ccs.domain.com
match the domain name
of the clickstream collection server that contains the tag code. If
you are collecting data over Secure Socket Layer (SSL), then the https
prefix should be used instead of http.
The following
table provides a line-by-line explanation of the full page tag.
Line-By-Line Explanation of the Full SAS Page Tag
|
|
|
Includes the SAS Tag
code. This code includes and defines the st_init() function, as well
as all of the data elements and default configuration settings for
the tagging solution. After this line has been executed in the browser,
st_init() is available to be called (line 12). Then the default tagging
information is sent to the clickstream collection server.
|
|
Includes the default
shared site configuration settings. This file is normally copied,
renamed, and edited to set common site-specific configuration settings
for data collection that applies across all pages into which it is
included. The link in Line 2 then normally points to this copy.
|
|
Enable page-specific
configuration and data values to be set. Settings made here can override
the product defaults and the site-wide settings and data values included
in Line 2.
|
|
Useful to include when
initially tagging pages to aid in testing. Inclusion of this line
results in a pop-up debug window appearing as the data is being gathered.
This feature provides more information about what is being collected.
Note that you should be careful not to include this line in your production
configuration or your users will also get this pop-up window. Also
note that you must disable pop-up blocking software that prohibits
this window from being displayed.
|
|
Initializes the tagging
code for the page. This line results in instrumentation of elements
on the page and collection of data about the page load event.
|
|
Used when JavaScript
is not enabled in the user’s browser and the tag code cannot
run. This line minimally makes an indication of this by requesting
the tag image with a static set of information to indicate that JavaScript
was not enabled. The page is tagged, but the information is not as
rich as if JavaScript were enabled. This line is necessary only if
you want to gather information about hits from users that have JavaScript
disabled.
|