mirror of
https://github.com/anyproto/docs.git
synced 2025-06-08 05:47:05 +09:00
GitBook: [#186] No subject
This commit is contained in:
parent
cbc8311f8e
commit
d5571dbd0e
3 changed files with 2 additions and 8 deletions
18
faqs/what-trackers-does-anytype-use.md
Normal file
18
faqs/what-trackers-does-anytype-use.md
Normal file
|
@ -0,0 +1,18 @@
|
|||
# What Trackers does Anytype Use?
|
||||
|
||||
While the product is in alpha, we use analytics services to help us understand performance of the app as a whole, adoption of certain features, and how the latter impacts retention.
|
||||
|
||||
**Amplitude** is the main service we use for tracking _events_ inside the app. It allows us to track metrics such as:
|
||||
|
||||
* How many users joined in the past month & how many dropped
|
||||
* How many Objects, Blocks, Sets, and Custom Types were created (and average that per number of active users)
|
||||
* How much time people spend in the app, on average
|
||||
* Which devices are used to login to the app
|
||||
|
||||
We use these to understand our main product metrics and whether overall, we’re moving in the correct direction. While we can track frequency and adoption of events, _we cannot in any way track the content you create._ I’d like to emphasise that this last point is foundational to us.
|
||||
|
||||
In practice, this means that we know for instance that custom Types are very popular, but we cannot see what these custom types are (nor which Objects you’ve created with those types).
|
||||
|
||||
Besides Amplitude, our iOS and Android teams use **Crashlytics** to understand the pervasiveness of crashes.
|
||||
|
||||
Once we open our beta we are eager to provide analytics opt-out.
|
Loading…
Add table
Add a link
Reference in a new issue