What you will learn
This tutorial will teach you how our SDK analytics library works, to enable you to retrieve and leverage all of the beacon-related interaction analytics with the AdTag platform.
The AdTag platform generates many types of analytics around beacon usage and interactions, based on the logs created by the mobile SDK.
For instance, the AdTag platform manages the following notification-related metrics:
- Number of notifications displayed per beacon
- Number & percentage of engagement on notifications
While the mobile SDK automatically generates some logs, others need to be manually configured in your application.
How does the SDK send logs to AdTag?
The SDK uses the AdtagLogsManager to send logs to the AdTag platform.
The AdtagLogsManager saves the logs in a specific database, and sends them in a dedicated thread when a maximum number of logs or 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 AdTag platform, each time a notification is displayed.
The Application Management section on AdTag allows you to manage:
- The network that your application can use to send the logs back to the AdTag platform: WIFI_ONLY or ALL (for all types of networks)
- The maximum number of logs mentioned above
- The maximum waiting time mentioned above
- Network type: ALL
- Maximum number of logs: 30
- Maximum waiting time: 25 seconds
Notification display logs
Each time a beacon notification is displayed, the SDK automatically creates a corresponding log.
Notification engagement logs
Each time a user engages with (= clicks on) a beacon notification, the SDK automatically creates a corresponding log, called a redirect log.
If you are working with custom-built notifications, make sure that you implement the configureNotificationIntent method from the BeaconIntent class, which then allows the SDK to generate the logs automatically:
Learn more about implementing a custom-built Notification Listener in the beacon notification tutorial