Capture Behavior Data
Post Data from an Authenticated Server-to-Server Connection
Post Data from an Unauthenticated Server-to-Server Connection
This page applies to both Version 2.x and Version 3.x of the Engagement Mobile SDK.
Note
The Data 360 Module for the Engagement Mobile SDK enables comprehensive collection of granular data about customer mobile app interactions through advanced event tracking capabilities.
Before behavior data can be sent to Data 360, ensure the following:
trackLifecycle to truetrackScreens to trueBehavioral lifecycle and screen events are disabled by default in the Data 360 Module for privacy compliance.
Each behavior generates an engagement event with eventType="appEvents" and relevant behavior-specific fields populated.
Lifecycle events are automatically triggered when your mobile app transitions between foreground and background states, or when the application is updated.
When the mobile application comes to the foreground, an event is generated:
1{
2 "behaviorType": "AppLaunch",
3 "appName": "MyAppName",
4 "appVersion": "1.0.0",
5 "eventType": "appEvents",
6 "category": "Engagement",
7 // + all automatically assigned fields like deviceId, sessionId, dateTime, etc.
8}On the first app launch, behaviorType is set to "AppFirstLaunch".
Note
When the mobile application moves to the background, an event is generated,
1{
2 "behaviorType": "AppBackgrounded",
3 "appName": "MyAppName",
4 "appVersion": "1.0.0",
5 "eventType": "appEvents",
6 "category": "Engagement",
7 // + all automatically assigned fields like deviceId, sessionId, dateTime, etc.
8}When the mobile application is updated, an event is generated.
1{
2 "behaviorType": "AppUpdate",
3 "previousAppVersion": "1.0.0",
4 "appName": "MyAppName",
5 "appVersion": "1.2.3",
6 "eventType": "appEvents",
7 "category": "Engagement",
8 // + all automatically assigned fields like deviceId, sessionId, dateTime, etc.
9}Screen events track customer navigation patterns as they move through different screens and views within your mobile application.
Screen view events are generated when customers navigate through different screens in your app:
Activity viewsUIViewControllers are added to the view hierarchy1{
2 "behaviorType": "ScreenView",
3 "screenName": "MyScreenName",
4 "appName": "MyAppName",
5 "appVersion": "1.0.0",
6 "eventType": "appEvents",
7 "category": "Engagement",
8 // + all automatically assigned fields like deviceId, sessionId, dateTime, etc.
9}After you’ve configured the Data 360 Module and enabled the desired behavioral events, the SDK automatically sends these events to Data 360 as they occur in your app. No manual intervention is required.