TelemetryDeck

Some of you might be seeing the mysterious “iPhone99,7” or “iPhone99,11” in your devices list. No one truly knows, but we think this might be Apple Private Cloud Compute devices as reported by the Apple Wiki. theapplewiki.com/wiki/IPhone99,…

What does iPhone99,7 mean? Wrong answers only 👀

When your app is used by thousands—including teenagers—you have to be especially careful with analytics. That's why FK Distribution chose TelemetryDeck: actionable product insights without building user profiles or collecting personal data. Case study: 
telemetrydeck.com/casestudies/en…

Tech update: We’re bringing back the detail panel in “Recent Events” because oh wow a lot of you missed that <3

Tech update: the namespace settings now live in Organization → Settings → Namespace Status

Tech update: When you are a very long-time TelemetryDeck user who has more included events in their free plan, we now store that number when you switch to a paid plan, in case you want to switch back to free.

Tech update: Our new billing model update is finally live. Not only does it allow us to offer more fine-grained packages and auto-sizing, but it also is way more configurable and allows us to set limits for overages and spike protection per customer.

Tech update: The “Recent Events” and “Parameters” views got a lot more interactive. Find out what parameters are mostly used and navigate backward in time with the recent events.

Tech update: Moved some servers around. We now have around 40 bare-metal machines and 20ish VMs.

Yes, TelemetryDeck is made and hosted in Europe. 🇪🇺 telemetrydeck.com/blog/europe-ba…

We’re gonna have to collect the user’s value of NSGlassTintAmount, won’t we? 👀

Tech update: We updated our permissions system to make accessing TelemetryDeck faster and more secure. (This led to some transient “user cannot access this namespace” errors, though; sorry about that.)

Now we're finally ready AND we took the opportunity to fix one of the biggest complaints: the gap between our smaller plans telemetrydeck.com/blog/pricing-u…

For almost 2 years we kept postponing a pricing update, because infrastructure, performance and becoming a fully European service came first.

Turns out, if you use Apple’s UIDevice.IdentifierForVendor and your customer just restarted their device and hasn’t unlocked it yet; that value might be nil. Just sayin’ (we’ll take that into account in future versions of the SDK).

@_BenjiM Sorry, this must have been a temporary glitch. Please try again.

@Telemetry_Deck site is down for me.

After 3+ years, we're updating TelemetryDeck's pricing. • More granular plans for indie developers • Automatic upgrades after sustained growth (not one-off spikes) • Existing paid customers keep their current pricing 🎉 More details on the blog: telemetrydeck.com/blog/pricing-u…

What would you like to track for upgrading to #iOS27 / #macOS27?

We've implemented a fix for our slow API issues. This should restore better service to all customers except those calling the deprecated api/v3/query/async API by hand. Please migrate to use the sync apis at v4/query/tql instead.

We are aware of our APIs being periodically slow and/or unavailable for individual requests. This seems to be because our number of users have increased considerably. We're investigating and working on various fixes. Thanks for your patience <3