Beacon tracking allows you to measure and target micro locations by using iBeacon and Bluetooth Low Energy.
The following beacon data is sent to Analytics and Target when trackBeacon is called:
- a.beacon.uuid - ProximityUUID of the beacon
- a.beacon.major - Major number of the beacon (such as store number)
- a.beacon.minor - Minor number of the beacon (such as a unique number within a store)
- a.beacon.prox - Values of 0-3 represent how close the user is to the beacon.
Here is what these values mean:
- 0 = unknown
- 1 = immediate
- 2 = near
- 3 = far
This beacon data is captured in mobile solution variables.
- Add the library to your project and implement lifecycle.For more information, see Add the SDK and Config File to your IntelliJ IDEA or Eclipse Project in Core implementation and lifecycle .
- Import the library:
- Gather beacon location.Multiple third-party libraries are available to scan Bluetooth LE beacons, depending on the manufacturer of the beacon.
- After the beacon information has been obtained, use the following call to track the location:
// assumed that the following variables will have been retrieved by the 3rd party beacon library String beaconUUID; String major; String minor; Analytics.BEACON_PROXIMITY proximity; // BEACON_PROXIMITY is an enum available in the SDK. Number 0-3 representing how close the // user is to the beacon. 0 unknown, 1 immediate, 2 near, 3 far. Analytics.trackBeacon(beaconUUID, major, minor, proximity, null);
- When the user leaves the beacon's proximity, clear the current beacon:
Send additional data
In addition to the beacon data, you can send additional context data with each trackBeacon call:
HashMap cdata = new HashMap<String, Object>(); cdata.put("myapp.ImageLiked", imageName); Analytics.trackBeacon(beaconUUID, major, minor, proximity, cdata);
Context data values must be mapped to custom variables in the Adobe Mobile services: