Application lifecycle



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.



Here’s an example of JSON added in the stc variable of your hits:

	"lifecycle": {
		"fs": 0,
		"fsau": 0,
		"scsu": 2,
		"fsdau": 20160120,
		"dsu": 0,
		"sc": 5,
		"fsd": 20160120,
		"dsls": 0,
		"dsfs": 0,
		"sessionId": "e1e04f45-8d54-4e24-81cf-75314a5bcead"


Name Description
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 application’s installation
scsu Number of sessions made since the last application update
fsd Date of the application’s 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 phone’s settings. As such, if the user has changed the phone’s date, the variable may be a negative number.

Was this post helpful?

Last update: 21/03/2016