What you will learn
This tutorial will teach you how to tag your mobile application with our mobile SDK, in order to retrieve and leverage all the beacon interaction analytics related to notifications from 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 for each beacon
- Number & percentage of 'clicked-through' notifications
While the mobile SDK automatically generates some logs, others need to be tagged manually in the application by developers.
How does the SDK send logs to the Adtag platform?
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.
It exists as well a method called pushLogsNow that permits to send the logs save in database immediatly to the Adtag platform. This method is called each time a notification is displayed.
The AdtagLogsManager allows you to configure:
- the maximum number of logs mentionned above
- the maximum waiting time mentionned above
- the network that your application can use to send the logs to the Adtag platform: it can be WIFI_ONLY or ALL (for all types of networks)
Default settings are:
- Maximum number of logs: 5
- Maximum waiting time: 20 seconds
- Network type: ALL
Beacon display logs
Each time a beacon notification is displayed, the SDK automatically creates a corresponding log.
Each time a beacon notication is clicked, the SDK automatically creates a corresponding log.
This is what Connecthings calls a redirect log.
These automaticac logs are possible because the SDK sets up a convention for your beacon notification intent. To help you, the SDK comes with the BeaconIntent class which provides several static methods to add the correct parameters to your beacon intent.
In the case of a notification, when implementing your own BeaconNotificationListener, calls the configureNotificationIntent method from the BeaconIntent class:
You can learn more about configuring your own BeaconNotificationListener reading the creating beacon notification tutorial