Yes. An extra Perl file (normally called rs000001.pl – depending on your script ID) is available in the installer and is automatically uploaded to your web site. It is a way of tracking which sites customers have come through in order to reach your site. It works by creating a text string as a cookie in the customer's browser if they click on a specific type of hyperlink. If the customer places an order, the text string is then included with the order.
The main uses of this are as follows:
* If you have several links on different websites that point to the same store, you can see how much business comes from each of those links by assigning a different text string to each link.
* If you have several links pointing to your catalogue from different parts of your website, you can see which part of your website is the most popular route for people to go down before arriving at your store by assigning a different text string to each link.
Once an order is downloaded the text string from the cookie appears in a field called sUserDefinedGeneral in the 'Order' table in 'ActinicCatalog.mdb'. By changing the User Definable 3 prompt in 'Design | Text | Web Site (cont) | General Information', to 'Referrer' (but NOT showing it), you can make the text string generated by referrer.pl appear on the Transaction Logs (in the format 'Referrer: <Text String>').
Correct Format for the Call to The Referrer Script
Presuming the following settings:
The call to referrer.pl would be as follows:
There are four values you pass to the referrer script:
* SOURCE=The text string to indicate where people have come from.
* DESTINATION=The page in your 'acatalog' folder you want people to land on
* PATH=The path from your cgi-bin folder to your 'acatalog' folder
* BASEURL=The URL of your acatalog directory
The values can be anything as long as they follow the x-www-form-urlencoded standard (%XX where XX is the hex code for the special character like spaces, & , ?, etc.). The text string is limited to 255 characters.
For example, http://www.myserver.com/acatalog/ will appear as: http%3a%2f%2fwww%2emyserver%2ecom%2facatalog%2f
/ becomes %2f
. becomes %2e
_ becomes %5f
: becomes %3a
The main uses of this are as follows:
* If you have several links on different websites that point to the same store, you can see how much business comes from each of those links by assigning a different text string to each link.
* If you have several links pointing to your catalogue from different parts of your website, you can see which part of your website is the most popular route for people to go down before arriving at your store by assigning a different text string to each link.
Once an order is downloaded the text string from the cookie appears in a field called sUserDefinedGeneral in the 'Order' table in 'ActinicCatalog.mdb'. By changing the User Definable 3 prompt in 'Design | Text | Web Site (cont) | General Information', to 'Referrer' (but NOT showing it), you can make the text string generated by referrer.pl appear on the Transaction Logs (in the format 'Referrer: <Text String>').
Correct Format for the Call to The Referrer Script
Presuming the following settings:
The call to referrer.pl would be as follows:
HTML Code:
http://www.myserver.com/cgi-bin/rs000001.pl?SOURCE=123&DESTINATION=Section%5fPage%2ehtml&PATH=%2e%2e%2fhtdocs%2facatalog&BASEURL=http%3a%2f%2fwww%2emyserver%2ecom%2facatalog%2f
* SOURCE=The text string to indicate where people have come from.
* DESTINATION=The page in your 'acatalog' folder you want people to land on
* PATH=The path from your cgi-bin folder to your 'acatalog' folder
* BASEURL=The URL of your acatalog directory
The values can be anything as long as they follow the x-www-form-urlencoded standard (%XX where XX is the hex code for the special character like spaces, & , ?, etc.). The text string is limited to 255 characters.
For example, http://www.myserver.com/acatalog/ will appear as: http%3a%2f%2fwww%2emyserver%2ecom%2facatalog%2f
/ becomes %2f
. becomes %2e
_ becomes %5f
: becomes %3a