LinkTrakker can be called via an SSI tag that you place in the HTML of the webpage to track. Before version 3.5, this was the only deployment method for LinkTrakker -- since then, JavaScript deployment provides a more compatible solution.
However, you could still use this method for collection (but to do so LinkTrakker must be installed on the same machine as the webpages to be tracked.) You must also make sure that permission to utilize server-side includes has been granted to the directory containing the page you want to track.
Windows NT users must make sure that the directories containing tracked webpages have permission to execute server-side included scripts (using #exec cgi mode). With a Microsoft IIS webserver, this is as easy as setting script execute permissions for the directory within the server manager console.
An example of the needed SSI tag:
<!--#exec cgi="/your_cgi_alias/trakker_ssi.cgi"-->
for UNIX
<!--#exec cgi="/Scripts/Trakker/trakker_ssi.pl"-->
Windows NT
In each of the above examples, the cgi= segment of the tag should be pointing to the trakker_ssi script in the LinkTrakker directory.
You'll need to add this tag to each page of your website you want to track. The tag can go anywhere on the page and will not interfere with the way the page is displayed.
If you are using SSI deployment, you must also make sure that the relative path variable is set for each entry in your Admin panel. This should contain the actual location of the HTML page, relative to the Web server's document root (always beginning with /).
In most cases, this should be the equivalent of removing the domain name portion of the URL for the page (for example, if the URL of the page is http://yourdomain.com/mypage.html, the relative pathname would be /mypage.html.)
In some cases, it is a bit more complex. Most Web servers look for a default document to display when a browser points to just a directory. For example, when you go to http://www.radiation.com/products/ (notice, no something.html), you are actually getting the index.html in the /products directory (so the relative pathname in this case would be /products/index.html.)
If your server behaves differently (for example, defaulting to default.htm), you will need to define relative urls accordingly.
