Editing the article for the hundredth time, Bill hunted for the word count button. Why couldn't they see that he used that all the time?
When most people think of maintaining event logs, they think of it in terms of tracking access to sensitive information inside the application. Whilst tracking activity is a very useful facility of the logs; they can be used for so much more.
If you know what your customers or clients are doing inside the application, you know what features they use more than others. You know where you could place sales prompts, which sales prompts are working. You know if the client actually read that document, even if they didn’t respond to your email asking them to read it.
“What scares me about this is that you know more about my customers after three months than I know after 30 years." - Lord MacLaurin, Tesco Chairman after the introduction of the Clubcard.
We are firm believers in the philosophy that you can never have too much data to analyse. In business terms, think how valuable it would be to a high street store to be able to track how many times a particular item of clothing was taken off the rail, or how many times someone picked up the packaging and read it, before putting it back on the shelf.
Technically speaking, to log users is not particularly complex. Once you have the framework in place to log one action, to log other extra actions should be simple enough to slot in. You are the person who knows your business best...but it is a rare business that wouldn’t benefit from knowing more about customers or clients.
If you are already logging the data, why not consider a tool to help you analyse it?
