What you will learn
This tutorial will teach you how to tag your application with our mobile SDK, in order to retrieve and leverage all the zone interaction analytics related to in-app actions from the Herow platform.
The Herow platform generates many types of analytics around zone usage and interactions, based on the logs created by the mobile SDK.
For instance, the Herow platform manages the following in-app action-related metrics:
- Number of in-app actions displayed for each zone
- Number & percentage of 'clicked-through' in-app actions
While the mobile SDK automatically generates some logs such as the In-AppActionDisplay Logs, others need to be tagged manually in the application by developers such as the Click-through Logs.
How does the SDK send logs to Herow?
The SDK uses the HerowLogsManager to send logs to the Herow platform.
The HerowLogsManager saves the logs in a specific database, and sends them in a dedicated thread when a maximum number of logs and a maximum waiting time is reached.
A pushLogsNow method also exists in the SDK, to immediately send the logs saved in the database to the Herow platform, each time a notification is displayed.
The Application Settings section on Herow allows you to manage:
- The network that your application can use to send the logs back to the Herow platform: WIFI_ONLY or ALL (for all types of networks)
- The maximum number of logs mentioned above
- The maximum waiting time mentioned above
Default settings are:
- Network type: ALL
- Maximum number of logs: 30
- Maximum waiting time: 25 seconds
These settings can be updated at any time on the App Settings section of the Herow Platform
Being GDPR compliant
Please refer to the dedicated GDPR tutorial to make the SDK compliant with the GDPR.
Starting from version 3.0.3 on Android, the SDK won't collect analytics without getting the appropriate opt-ins
Alert display logs
Each time an in-app action is displayed, an analytics log is automatically sent to the platform.
Each time an in-app action is clicked, the SDK automatically creates a corresponding log.
This is what Connecthings calls a redirect log.
These automatic logs are possible because the SDK sets up a convention for your zone notification intent. To help you, the SDK comes with the class InAppActionRedirectHelper which provides a static method to add the correct parameters to your zone intent.
When an in-app action is clicked, you must use the configureInAppActionIntent method from the InAppActionRedirectHelper to correctly configure your intent to generate a 'Click-through' log:
InAppActionRedirectHelper.configureInAppActionIntent(intent, placeInAppAction, redirectType, from);
The parameters of the methods are:
- intent: the intent needed to be configured
- placeInAppAction: the object for which the log is generated.
- HerowLogData.REDIRECT_TYPE: indicates the origin of the activity. In this case, as the activity was launched from an in-app action: HerowLogData.REDIRECT_TYPE.ALERT
- From: use it to provide additional contextual information regarding the in-app action, for example, the Activity that originally displayed the action. Be sure to use the same tag than the iOS team