We built UserSignals because we needed a way to see exactly how each individual using one of our web applications was using the website and see which features/sections they have used and which they haven't.
This is hugely important because it gives us the data we need to make informed decisions and helps us personalize our outreach to individual members to encourage them to get the most out of an app and discover crucial features or guide them through new features if they've haven't tried them yet.
Google Analytics is the go-to solution for website analytics but we found that it just didn't provide the user level insights and capabilities we were looking for. The data from GA was too high level, showing "this happened on your site" but not "these specific users did this and these ones have never visited this particular section."
Further, we found huge discrepancies in the numbers reported by GA versus UserSignals. Because UserSignals tracks using a unique user ID for each registered member, we can accurately determine how many users did something, regardless of how many devices or sessions were involved. In Google Analytics, "unique users" doesn't necessarily mean "unique individuals".
Additionally, the standard edition of GA doesn't provide the capability to extract raw data so you can't perform independent audits or join in additional or sensitive user data to perform deeper analytics and queries. A premium version is available that supports this but it is priced for enterprise users rather than startups and small businesses; and it still isn't specifically designed to track events and activity associated with specific, indentifiable users. We needed to be able to export the raw data at any time and ideally be able to schedule automatic delivery of batch exports for integration with other systems (we're still working on scheduled exports, but they're coming soon.)
When research other analytics platforms we found their pricing left a lot to be desired, tending to be convoluted and confusing or simply too expensive. Typically pricing was metered based on number of events tracked or number of sessions, making it tremendously difficult to anticipate or forecast what your actual cost would be. For UserSignals we decided it was much simpler to charge by the total number of users tracked and the data retention period.
And because nobody seemed to have built quite what we were looking for, here we are!