Analytics app instrumentation data points
The following data elements can be used at specific points in your app business logic in order to collect analytics data. You must configure these parameters within the Call SubApp element that is added to a warehouse app.
| Data Element | Description |
|---|---|
| Base_App | Identifies the parent app from which Insights data is collected (25 characters maximum). |
| App_Subapp | Identifies the subapp within the parent app (150 characters maximum). |
| PathID | Identifies the business logic path used to process the transaction (25 characters maximum). |
| StepNo | The sequential step within app business logic in which an action took place (decimal(18,6)). |
| What | Identifies the activity being performed (25 characters maximum). |
| EventSubType | Identifies user actions, for example, start, cycle, retries, failed attempts, steps, stop, etc. |
| LocationName | The name/description of the warehouse location to identify the user location. This data point can include a descriptive name, physical addresses, etc (150 characters maximum). |
| Loc_Latitude | The latitudinal map coordinate identifying the geographic location of the mobile app user (25 characters maximum). |
| Loc_Longitude | The longitudinal map coordinate identifying the geographic location of the mobile app user (25 characters maximum). |
| ItemID | The unique item identifier (25 characters maximum). |
| ItemName | The name of the item (75 characters maximum). |
| ItemDesc | A brief description of the item (150 characters maximum). |
| Quantity | The true quantity of inventory you have in stock (decimal(18,6)). |
| FunctionCall | Identifies the function call for the task being performed (100 characters maximum). |
| FunctionCallID | The unique identifier for the corresponding function call (100 characters maximum). |
| ErrorMessage | Enables developers to capture device error messages. |
| Retry | Indicates whether a second transaction was attempted for the record. |
| CaptureUserComments | Indicates whether to capture user comments when processing a transaction. User comments are beneficial when troubleshooting. |
| UserComments | Enables developers to incorporate user comments into app business logic (300 characters maximum). |
| DeveloperNotes | Enables developers to incorporate app developer notes into app business logic (1000 characters maximum). |
| PromptQuestion | Enables developers to include questions within the app. This is useful for capturing error path details (300 characters maximum). Best practice is to use this data point sparingly. |
| SessionID | A system-generated unique identifier in all of your log events. |
| Custom1-10 | Ten customer-defined customs fields available to developers (50 characters maximum). |
Systematically captured data points
| Data Element | Description |
|---|---|
| UserID | The systematically captured user identifier (64 characters maximum). |
| DeviceID | The systematically captured device identifier (64 characters maximum). |
| DeviceType | The systematically captured handheld device in use (64 characters maximum). |
| ApplicationID | The systematically captured identifier for the app. |
| Duration_Min | The systematically calculated duration of an event in minutes. |
| DeviceUTC | The systematically captured coordinated universal date and time. |
| DeviceLocalTime | The systematically captured current time at the device location (14 characters maximum). |
| TransactionGUID | The systematically generated transaction identifier (100 characters maximum). |
| EnvironmentID | The systematically captured identifier indicating whether the data is from the development or production environment. |
Loading...
There was a problem loading this topic