Frequently asked questions

TelemetryDeck supports multi-platform integration! All TelemetryDeck Events are sent via HTTP POST request, so you can send them from a web page, or any other app for any platform. For websites we provide a single line of code so you can get started instantly, and our SDKs are super lightweight and help you send signals from the get-go.

We're providing SDKs for Swift, Kotlin, JavaScript, and more!

If you would like to see other client packages, open an issue or (if you want to be particularly awesome) maybe write one yourself and share it with us and the community? Here's a spec document to get you started.

The SDK code included in your app is licensed under a modified MIT License with a removed attribution clause. This means you can use it in any project without restriction, and you do not have to attribute it.

A TelemetryDeck Event is the most basic building block in the TelemetryDeck analytics ecosystem. Every time an event happens in your app, you can send an event using the TelemetryManager.send(...) function.

Events have a type which is the name of the signal such as TelemetryDeck.Navigation.pathChanged, a user which is a String representation of a hashed user identifier, plus a parameters which are various metadata, such as TelemetryDeck.Device.operatingSystem, TelemetryDeck.RunContext.language, or custom metadata you want to deliver with each event.

Events are the raw data that is being interpreted by your analytics.

You can upgrade your plan at any time, and we'll prorate the price difference. The system will also auto-upgrade you if you go over your included events too many times in a row.

Welcome to the analytics journey! Our recommendation is to start with the smallest paid plan and add only the most basic analytics. This will allow you to estimate your costs better.

If you use more data than is covered by the smallest plan, it will auto-upgrade after two months.

We'll warn you at 80% and 100% usage via email, but events are still ingested. We'll upgrade your plan to the next fitting plan if this happens for two months in a row.

We recommend one TelemetryDeck App per codebase. This makes it easy for you to separate different concerns and dashboards so you're just analyzing the code that you want at one time.

Additional apps don't incur any extra costs because they are grouped under your Organization, and the Usage dashboard will show you which apps use the most of your included evens.

Congrats, you're featured on the App Store! If your spike is temporary, you'll probably run into your plan limit, and if you are way over your limit, we may decide to pause processing your data for a bit.

However, one single spike won't increase your costs. To make sure we're growing organically with you, we'll only upgrade your plan if you're over the limit two months in a row.

Also, talk to us, we'll find something.

That depends a lot on the number of users you have, the type of your app (websites are way less chatty), and how much data you're collecting. When you send a TelemetryDeck event every other line in your code, your usage will be higher than if you only send one at app launch.

A good starting point is Number of Usersｘ30. You can also play around with our Pricing Calculator for a better estimation.

For sure! Contact us at info@telemetrydeck.com and we'll help you find the perfect solution for your needs!