Lifecycle variables allow you to know how users are using your application. With lifecycle variables, you can calculate, for example, user retention and the use rate of your application.
Lifecycle variables are automatically calculated and added in stc variable of your hits.
Heres an example of JSON added in the stc variable of your hits:
Since 2.11.1 version, it’s now possible to get metrics computed by SDK to do an other processing. To do this, just call tracker method :
Metrics are rendered in the same way as in the stc, so get it from the same key (sample with “sc” : session count):
|sessionId||The session begins when an application is launched or brought into the foreground, and ends when the application is sent to the background during more than 60 seconds (by default), or when the application is closed.|
|fs||Allows you to know if the application was launched for the first time|
|fsau||Allows you to know if the application has been launched for the first time since an update|
|sc||Number of sessions made from the applications installation|
|scsu||Number of sessions made since the last application update|
|fsd||Date of the applications very first session|
|dsfs||Number of days since the very first session|
|fsdau||Date of first session since the last update|
|dsu||Number of days since the last update|
|dsls||This variable indicates the number of days that have passed since the last session. The calculation is made using the phones settings. As such, if the user has changed the phones date, the variable may be a negative number.|
Was this post helpful?