We've been discussing adding some analytics to our B2B products, in order to get a better idea of usage of our quite numerous modules and so on. We're a small but growing team with around a thousand customers between our products.
The two products are quite different, one a web-based and more of an aid, where retention and such metrics make sense. Here we've experienced companies replacing the sole person using our application, the new hire doesn't get taught about our tool or forgets, and suddenly they're wondering about these bills they're getting. We've got multiple companies where we've successfully sold our product to several times.
The other is a more traditional CRUD application, which users have to use to get their job done. As such retention and similar isn't a very relevant metric. However it has a large number of modules, and a lot of new functionality in each release, so feature tracking is more interesting. Perhaps failure/error tracking too, like how many manage to trigger certain errors and warnings, indicating a potential weak UI.
I mean the main screenshot shows a "Features" panel, but we have several hundred features we'd like to track, maybe thousands depending on how we can filter on event properties. We have quite a lot of core modules, almost all of which are per-country, so we need to be able to look at module usage per country for example. In addition a large portion of our customers have one or more custom integrations (some have over a dozen, again per-country in relevant countries). I wasn't able to see if we'd get the insight we need for this use-case.
In either case we're quite worried about PII, and while it's nice you got GDPR covered, I think we don't want any PII connected to our users. It's interesting to know how many users use a feature at a given company, but we don't really want to know who that is. From what I can gather that should be OK, just use some UUID for each user and leave it at that?
Perhaps these are dumb questions, product analytics isn't my forte and as mentioned we're just exploring the options at the moment, so don't have any direct experience yet.
That said, June does look really interesting. Especially since we don't have anyone who can dedicate a lot of time to this task.
Hey there - I missed this comment somehow as it was at the bottom of the thread.
You can use June without sending us PII some of our users do it. That being said most of our customers send PII to June as it really helps in the day to day to be able to look up a customer and get a quick glance of their usage
For features you can indeed create hundreds of them - we have pretty good filtering for the features, so you'd be able to rank them by usage, retention or even launch date.
Let me know if you do sign up, I'd love to make sure you get the most out of our product
The two products are quite different, one a web-based and more of an aid, where retention and such metrics make sense. Here we've experienced companies replacing the sole person using our application, the new hire doesn't get taught about our tool or forgets, and suddenly they're wondering about these bills they're getting. We've got multiple companies where we've successfully sold our product to several times.
The other is a more traditional CRUD application, which users have to use to get their job done. As such retention and similar isn't a very relevant metric. However it has a large number of modules, and a lot of new functionality in each release, so feature tracking is more interesting. Perhaps failure/error tracking too, like how many manage to trigger certain errors and warnings, indicating a potential weak UI.
I mean the main screenshot shows a "Features" panel, but we have several hundred features we'd like to track, maybe thousands depending on how we can filter on event properties. We have quite a lot of core modules, almost all of which are per-country, so we need to be able to look at module usage per country for example. In addition a large portion of our customers have one or more custom integrations (some have over a dozen, again per-country in relevant countries). I wasn't able to see if we'd get the insight we need for this use-case.
In either case we're quite worried about PII, and while it's nice you got GDPR covered, I think we don't want any PII connected to our users. It's interesting to know how many users use a feature at a given company, but we don't really want to know who that is. From what I can gather that should be OK, just use some UUID for each user and leave it at that?
Perhaps these are dumb questions, product analytics isn't my forte and as mentioned we're just exploring the options at the moment, so don't have any direct experience yet.
That said, June does look really interesting. Especially since we don't have anyone who can dedicate a lot of time to this task.