By default, Telemetry gives you detailed information about App Version, Device Type, Platform, and Distribution Mechanism. But that's just the start: You decide the signal types and the metadata payload for each signal, so you can include exactly the information you need to improve your app!
Each time you want to send a signal to Telemetry, call one (non-blocking) function: App Start. User has switched the Settings to Pizza Mode. New Data Entered. And so on.
That's it! Lean back and see information fill your dashboard in Telemetry's very nice (if I may say so) iOS and macOS app.
With App Store analytics, the available information is kinda slim. Like, amount of downloads of your app, and how many people open them. Nothing after! And you'll only get this data about a day later.
With Telemetry, you get signals about one second after the app has sent them. And you can get way more information too, like: Which features are your users actually using?
While other analytic packages are eager to scrape as much data off your users as possible, Telemetry only communicates the data you need to find out how your users use your product.
User Identifiers are always hashed. This way you can recognize the same user when they reappear but never associate data with a specific person.
Or, if you have more questions, contact the Autor @breakthesystem aka Daniel on Twitter.