Lots of devs have done it in Perl. I’ve done it in Perl and in JS. I’ve done lots of things that are easy to knock-out a decent prototype but cannot compare in the slightest to a professional package sustained by hundreds of thousands of users and teams of dedicated devs. For example, at work my old boss used to brag about how our site had 10 million page views a month via pure Perl tracking. I was very skeptical and insisted we try Analytics. When we finally started tracking it with a real tool it turned out that more than 9 million of the views were robots, spam bots, and spiders; and internally fired checks which were underestimated.
If you just want to track internal app usage and you are using code based on a framework with a central controller/dispatcher like Catalyst you can easily route internal nav information to a DB or flat file or whatever. Sessioning is not completely meaningful here as some clients don’t keep state/cookies. If your app is facing the Internet, the quality of your data will be low. If you’re doing internal/intranet and your site uses no rich content, you could be fine with this approach… depending on what you want to do with it.
So, what do you want to do with it? Where is it? What framework are you using?
In reply to Re^3: Tracking users clicks throughout an application
by Your Mother
in thread Tracking users clicks throughout an application
by Anonymous Monk
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |