KISSmetrics
Largest users
There are a countless number of analytics and metrics solutions on the Internet. We believe KISSmetrics is different than any other analytics system due to a combination of three key features. KISSmetrics: 1. Allows highly-flexible custom data with an extremely simple API 2. Focuses on people and has a memory 3. Makes funnels and conversions, one of most important pieces of information for a product, easy to track and interpret
Reviews for KISSmetrics
This review is devoted to the KissMetrics,but including some comparisons with Google Analytics and Mixpanel.
One of the key-questions what KissMetrics is able to answer you is where in your sign-up process people are ditching your site, due to excellent funnels.
KissMetrics Pros & Cons:
KissMetrics leads at funnels. If you need to know how many visitors go from your landing page to pricing to sign up and how many drop out at each stage, it’s easy. You would first set up a few URL rules on the KISSmetrics site:
or via an event API very similar to Mixpanel's:
***_kmq.push(['record', "Viewed main timeline"]);***
and then chain them together into a nice visual report:
Most importantly, the KISSmetrics funnels are very accurate. They consistently matched the traffic I measured with Google Analytics and matched up with the numbers in my database.
While their funnels are great, you can encounter problems finding KISSmetrics useful for anything else. Even though their JavaScript API is almost identical to the Mixpanel one, there is no reporting interface that supports measuring retention. And while you can track properties for events, again like Mixpanel, you can find those much less useful in the funnels.
KISSmetrics makes it easier to get set up with a really helpful debugger that loads an arbitrary URL on your site and shows you all the data KISSmetrics is collecting. This is much easier than the hoops I had to jump through with testing my Mixpanel setup.
Both Mixpanel and KISSmetrics allow you identify a user with something unique like an email address, username, or id before recording other data. This helps with accuracy so that the same visitor isn’t counted multiple times in a funnel or for an event (unless they actually went through the funnel or triggered the event multiple times). While this makes for better reporting, neither Mixpanel nor KISSmetrics let you see all the events any given user triggered or all the funnels he or she went through. You can approximate that functionality by setting an identifier property with each event. So instead of just reporting that the currently logged in user viewed the main timeline, you can specify who it was with a property and be able to filter the reports by that property. This can be a bit cumbersome but per-user data is very useful because instead of retention in the abstract, you get to see exactly who is coming back.
