LinkPulse implementation
Implementing LinkPulse consist of two processes:
- Installing the logging software
- Implementing tags in the user interface templates
Installing the logger
The recommended method for logging is setting up the web-server to do the job for you. As an alternative you can use a dedicated server for the job, see PDF below. The procedure includes setting up jobs for transferring the logs to the reporting server.
There are several ways to install the actual logging procedure, depending on OS and platform. The best, most thoroughly tested method is based on the Mod_rewrite module of the Apache web-server. This method easily handles several million lines a day without taking a toll on the server. You could run that on a old PC. For other platforms, please contact us, as not all alternatives support LinkPulse 3.
High traffic implementation.pdf describes alternative setups for Apache based logging, including one for windows environments
User interface implementation
A prerequisite for information on user behaviour is that the clicks can be positioned in the user interface. As a coordinate systems approach is both useless for dynamic sites and really don't give you any useful meta information, LinkPulse is based on categorising the user interface.
Categories in this context are made up of links that belong to each other in the interface. Left_menu, feature_lead and bottom_listbox are all typical categories.
Read more about Categorisation here
To implement the categories in the templates:
After defining your categories, either by yourself or in collaboration Onsite, you have one manual and two automated methods
to chose from . See Manual or automated implementation of LinkPulse tags