Tealium.Config config = Tealium.Config.create(application,"YOUR_ACCOUNT","YOUR_PROFILE","ENVIRONMENT");boolean isAutoTracking =true;// Additional instance for Lifecycle
trackingLifeCycle.setupInstance("INSTANCE_NAME", config, isAutoTracking);// Standard Tealium instance
Generated on the first onActivityResumed to occur. If onActivityPaused is called before onActivityResumed (when the library is initialized in the middle of the Activity lifecycle), then the module creation time is used to generate a launch event.
Generated during onActivityResumed when more than 5 seconds has elapsed since the last onActivityPaused. This indicates that onActivityResumed is called because the app is foregrounding and not because of a view change.
Available for specific lifecycle paradigms and unconventional lifecycle tracking. This approach is not recommended for most implementations. To allow manual lifecycle tracking update your lifecycle initiation code to set isAutoTracking to false.
To manually track a launch event, call trackLaunchEvent:
Tealium and the attached LifeCycle multitons are remote-killable by pubish settings in Tealium iQ. Null checks should be performed when getting the instances to call their methods.
When a launch event follows a wake event or vice-versa, this indicates a crash has occurred since the app did not successfully sleep. If the aforementioned sequence occurs because of a Tealium library shutdown, this is not considered to be a crash event.
When a crash event is detected, the launch or wake event data will have the lifecycle_diddetectcrash variable will be added.