We actually don't collect that information for privacy reasons.
The only thing we *do* have is the number of channels that the widget is added to, as a natural side-effect of the way the system works, but that doesn't tell you if anyone's actually using those channels.
Because of the cache, we don't know how many times a widget is actually run, only how many times it's fetched from our servers, which would be probably be an order of magnitude too low if the cache is doing its job properly.
We don't currently collect *any* information about what users are clicking on, what music they're playing, or even what mode it's in - in general we resist collecting fine-grain user behavior from the device because, frankly, it's a bit creepy.
This might seem pretty strange - but we're interested mainly in overall, aggregate behaviors, keeping information about individual users as anonymous as possible. Information about individuals exists only the degree that it takes to operate the service, or diagnose problems. We may change this in the future, but for the time being, privacy trumps collection of personal use data. As a side-effect, this means we naturally comply with some of the more draconian data privacy rules in various countries.
What we encourage folks to do that care about this is to instrument their own widgets to collect the information they want and send it to their own servers. While not required, we'd also encourage disclosure of the information being collected so that users can make an informed choice.