Campaign Analyzer
Overview
Features
Version Log
Demo
Order
Download
Setup Guide
FAQ
|
Setup Guide
1. Unzip ca.zip. You should get the following files:
report.cgi - Main script
hit.cgi - Hit logging script
lead.cgi - Lead logging script
sale.cgi - Sale logging script
*.pm - common libraries
styles.css - CSS styles
*.gif - image files
*.dat - data files
2. Edit *.cgi files if needed: the very first line contains full pathname to Perl. Default settings should
be OK for most systems, but you should check with your administrator if not sure.
3. Create Scripts Directory (if does not exist) on your web server. Make sure web server can execute
scripts from this directory. Set mode to 755.
4. Upload all *.cgi and *.pm files to the scripts directory on your
web server in ASCII mode. Please note, you should use ASCII mode when uploading scripts to your
web server.
5. Set 0755 mode for all *.cgi and *.pm files you have uploaded as per step 4
6. Upload all *.css, *.gif, *.dat files to the same directory in BINARY mode.
7. Enter URL of reprot.cgi script into your browser address string and hit Enter key. You should see
System Setup Wizard screen. If you see something
else, please refer to Setup Troubleshooting section for more info.
8. Complete setup using Setup Wizard
9. Add tracking code to your web pages and/or modify cgi scripts to generate tracking code. To
obtain code please use Campaign Analyzer Code menu.
3. Setup troubleshooting
You have entered URL of report.cgi into browser address string and...
3.1. Saw Page Not Found 404 Error
That means you either made a mistake typing the url or the scripts directory must be accessed
via another URL - please refer to your web server documentation to find out how URLs map to file system
directories on your server.
3.2. Browser began download source code of the register.cgi script
That means your server does not recognize register.cgi as executable script. Please refer to your web server
documentation
to find out how to configure web server to recognize *.cgi file extension as executable script.
3.3. Saw Internal Server Error page
There could be multiple reasons for this error including but not limited by using binary mode to upload file,
wrong path to Perl (the very first line of any script), failure to make executable either script file or
script directory. Please refer to contents of your server error log file for error description. Please note,
that one error usually generates 2 or more lines in error log file and the last one, which reads "Premature end
of script headers" does not contain useful info. Before contacting us please obtain at least 10 last lines
from your server error log.
|
