I was meeting with a large marketing/development company the other morning to demo Loggr and get some feedback (that was you Josh and Joe, thanks!). Usually one of the first questions I get in a meeting like that is…
"How is Loggr different than Google Analytics?" It’s a fair question, and since I typically talk about GA in my introduction, I fully expect to get it.
Both Loggr and Google Analytics track things and provide analytics on the things they track. The difference is in the things we track. GA tracks web traffic while Loggr is used for tracking application events.
"What are application events?" is usually the next question, and not as easy to explain. I usually try to give an example. Picture an online book store. There are numerous, important events going on in an e-commerce website like that. Events that give a clear picture into how the website is being used — or not used. Here are some:
- new and deleted customer accounts
- adding and removing books in a shopping cart
- abandoned shopping carts
- customers leaving comments or reviews
- customers getting errors
These are events that are really important to track. Even more important is to track the particular user that is doing all these events, when they are doing them in what order. This is where Loggr excels and the effectiveness of Google Analytics is kinda useless.
I try to explain it this way… Google Analytics is one of the best tools prior to your website’s login page. After the login page you want to track events based on the user, which is what Loggr does. If your website doesn’t have a login page, which probably means it doesn’t specifically identify users, then Loggr is not as helpful.