05-07-2014 06:39 AM - last edited on 09-29-2015 01:23 PM by Migrator
"Is there more information on what these data sources should contain and when/if they should contain data?"
If the Tealium Android Library is initialized with the Tealium.OPT_VOL_VERBOSE flag, you can see the populated data sources generated by the Library in LogCat with the tag "Tealium" at Verbose level. - carrier should be generated for every call as long as ((TelephonyManager) context.getSystemService(Context.TELEPHONY_SERVICE)).getNetworkOperatorName(); does not return null or an empty string. - exception_name - exception_reason - exception_totalcrashcount - exception_trace Are only generated when a crash occurs (if LifeCycle is not suppressed) or if an Exception was tracked using the Tealium.track(Object, Map, String) method (https://community-beta.tealiumiq.com/t5/Customer-Documentation/Mobile-Android-APIs-2-1-x/ta-p/5722 - lifecycle_firstlaunchdate_MMDDYYYY - lifecycle_launchcount - lifecycle_sleepcount - lifecycle_terminatecount - lifecycle_totallaunchcount - lifecycle_totalsleepcount - lifecycle_totalterminatecount These are definitely generated during LifeCycle events only, as long as LifeCycle events were not suppressed in library initialization. - view_height - view_size - view_type - view_width - webview_url Are all iOS specific, and not currently supported by Tealium Android Library 2.1.
"Is there a way for us to "see" that they are working? Meaning, is there somewhere in the Tealium Management console to see if these are firing?"
Possibly, I'll consult someone on this and get back to you, thank you for your questions.