Configuration

There are several settings you can configure to capture data from your applications. You can configure most of the basic global settings in the TealeafBasicConfig file. Some settings configuration in the EOCoreBasicConfig file and TealeafLayoutConfig.json file.

Application key

The application key identifies and sessionizes mobile applications with Tealeaf services.

Use a unique Application Key for each mobile application. You may also capture the same data from more than one application. In such cases, you can use the same application key for all the applications. You can then group the data captured from the various application as a single entity.

Contact your administrator for the value of the application key for the SaaS service. The on-premises service may use cookies for sessionization. If cookies are used, then use TLTSID as the cookie name.

Kill switch

A kill switch is a mechanism that lets you disable the Connect library remotely on end users' devices. When you enable the kill switch setting, you must provide the URL for the application. The kill switch settings verify if the URL is reachable or not.

Cookie settings

#Call killswitch for a new session id
SessionTimeoutKillSwitch=false

# Device id header and cookie
disableTLTDID=true

#Image settings
# You can have PNG or JPG
ScreenshotFormat=JPG 

Session timeout

Screenshot

The screenshot setting controls how screenshots are captured. You can store screenshots in memory instead of in the local memory on the device. To store in memory, set PersistLocalCache to no in the local cache file settings.

Capture native layout

Configure the following settings to capture the screen layout.

Gesture enabled

Configure the following settings to capture gestures.

Auto-geolocation

Configure the following settings to capture location.

#Auto Geolocation logging enabled or not
LogLocationEnabled = true
LogLocationTries = 3
LogLocationTimeout = 30

Auto-instrumentation

Post settings

The post settings help manage the data posted from the framework to the server. You can configure the post settings in the EOCoreBasicConfig and the TealeafBasicConfig files.

Configure the following in the TealeafBasicConfig file.

You can also configure the following settings in the EOCoreBasicConfig file.

Local cache

Use the Local cache file settings to manage the local cache in the device used to log data. The local cache file settings are configured in the EOCoreBasicConfig file.

Log level settings

You can use the Log level settings to manage the data that is logged during a session. The log level settings are configured in the EOCoreBasicConfig file.

Auto layout

AutoLayout logs type 10 screen layouts for screen views of native mobile application sessions. It also enables the application to continue logging type 10 screen layouts when it resumes to the foreground.

You can configure the auto layout setting in the TealeafLayoutConfig.json file. Each AutoLayout entry has the following sub-entries.

Assign an identifier to a target item

To assign an identifier to a target item, add the AppendMapIds key to the TealeafLayoutConfig.json file. You can assign a readable identifier to the mid that maps to the target item. You can then configure events to fire when the identifier is encountered. You can use the same identifier for Android devices as well as iOS devices. When you assign the same identifier to your Android and iOS devices, you can create a single event in Event Manager that fires on the identifier. The event fires for both Android and iOS devices.
For example:

"AppendMapIds": { 
  "[PWDV,0][ABOL,0][FL,0][TH,0][LL,0][TW,0][LL,1][LL,0]": {
    "mid": "LoginButton"
  }, 
    "ibm.com.demoapp.main_activity_login:id\/send": {
      "mid": "LoginButton"
    }
}

Uses the mid setting to assign an identifier to two targets. The first target is for an iOS device, and the second target is for an Android device. The target for both devices is identified as LoginButton. You can create a single event that fires when LoginButton is encountered in either application.

The following snippet is an example of a TealeafLayoutConfig.json file:

{
  "AutoLayout": {
      "GlobalScreenSettings":{
          "ScreenChange": true,
          "DisplayName": "",
          "CaptureLayoutDelay": 500,
          "ScreenShot": false,
          "NumberOfWebViews": 0,
          "CaptureUserEvents": true,
          "CaptureScreenVisits": true,
          "CaptureLayoutOn": 2,
          "CaptureScreenshotOn": 0
      },
      "PaymentActivity":{
          "ScreenChange": false,
          "DisplayName": "The Payment Screen",
          "CaptureLayoutDelay": 500,
          "ScreenShot": false,
          "NumberOfWebViews": 0,
          "CaptureUserEvents": false,
          "CaptureScreenVisits": true,
          "CaptureLayoutOn": 0,
          "CaptureScreenshotOn": 0
      }
  },
  "AppendMapIds": {
      "[w,9290],[v,0]": {
          "mid": "ASimpleUIView"
      },
      "tag2999999": {
          "mid": "giveAdditionalId1"
      },
      "idxPathValue": {
          "mid": "giveAdditionalId2"
      }
  }
}