> We actually don't care who each user is, we just want the aggregate data.
> It's very important for us to know which of those functions are being tried, used, and reused (or not)
Aren't these 2 at odds with each other, or else how can you tell when the same person re-uses a feature? Surely you need some kind of user identifier for that?
Yes, good point, I should have been more clear. You're right that we track unique users, but we do so in abstract. I suppose with some work we could pull together enough data from different sources to determine who a particular user was in a particular session. I just meant that we don't do that and it's not easy for us to do that because we don't care about that type of data. We only care about what each abstract user does in the sense that we want to know the aggregate of how many users did that thing.
Additionally, unlike google analytics, we do support the browser's "do not track" flag. So if a user doesn't want to be tracked at all, we completely respect that.
> It's very important for us to know which of those functions are being tried, used, and reused (or not)
Aren't these 2 at odds with each other, or else how can you tell when the same person re-uses a feature? Surely you need some kind of user identifier for that?