This repository was archived by the owner on May 5, 2026. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Application lifecycle 6f1d08
Benjamin Diolez edited this page May 5, 2026
·
1 revision
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": {
"sessionId": "e1e04f45-8d54-4e24-81cf-75314a5bcead",
"fs": 0,
"fsau": 0,
"sc": 5,
"scsu": 2,
"fsd": 20160120,
"dsfs": 0,
"fsdau": 20160120,
"dsu": 0,
"dsls": 0
}
}Since 2.10.1 version, it’s now possible to get metrics computed by SDK to do an other processing. To do this, just call tracker method :
Map<String,Object metrics = tracker.getLifecycleMetrics();Metrics are rendered in the same way as in the stc, so get it from the same key (sample with “sc” : session count):
Map<String,Object metrics = tracker.getLifecycleMetrics();
metrics.get("sc"); // get the session count| 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. |
Last update: 26/10/2018
-
Data API
- Data flow
- Advice optimizations data flow
- Error codes data flow
- Faq data flow
- General information data flow
- Technical information data flow
- Reporting API v3
- Getting started
- Methods
- Parameters
- Technical information
- REST API
- Campaigns
- Custom variables
- Getting started rest
- Methods rest
- Response structure parameters rest
- Fixed periods
- Parameters compatibility
- Relative periods
- Structure of the response
- “code” parameter
- “columns” parameter
- “evo” parameter
- “filter” parameter
- “include” parameter
- “lng” parameter
- “max-results” parameter
- “page-num” parameter
- “period” parameter
- “period” parameter: “H” v. “He” & “MN” v. “MNe”
- “retention” parameter
- “segmentdesc” parameter
- “segment” parameter
- “sep” parameter
- “sort” parameter
- “space” parameter
- Technical specifications rest
- Data flow
-
Data collection
- Android
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Users
- Apple
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Users
- General
- Cddc renew staging process
- Changelog
- Craft your hit
- Encoded parameters
- Server side cookie management
- Supported taggings
- Tagging deletion
- Utilisation of dispatch sdks
- JavaScript
- Advanced features
- Campaigns
- Changelog
- Content
- Ecommerce
- Getting started
- Partners javascript
- Users
- Piano Analytics
- Event tagging piano analytics
- Getting started piano analytics
- Piano analytics tagging
- Feeding piano analytics with as2 tagging
- Tagging custom properties sdk
- Android