Bleesk is the only proximity platform that supports 4 different trigger types that deliver proximity campaigns to your customers' phone: Beacons, WiFi, Geofence and QR codes.
Please make sure that your beacons are properly configured before starting a proximity campaign. The default settings that are set by beacon manufacturers' do not meet requirements for a successfull proximity campaign. Please make sure that:
- Broadcasting Power (Transmission power) is set to + 4 dBm - the more power, the longer the range. Increasing the power makes the signal more stable. If you want the beacon to trigger only when a phone is touching it (or nearly touching it) you should test setting brodcasting power for -40 dBm though.
- Advertising Interval is set to 200 ms. The shorter the interval, the more stable the signal.
- Smart Battery Saving is set as OFF
- Security UUID is set as OFF
- Use only one bluetooth protocol per beacon (iBeacon or Eddystone UID) - enabling beacon to send bluetooth signals in both protocols significantly decreases the campaign delivery rate.
Adding WiFi spots is as simple as adding beacons:
Campaigns that are triggered by WiFi spots work on both iOS and Android. The only difference between two systems is that on Android all you need to do is turn on WiFi on your device, whereas on iOS you need to be logged in to a designated WiFi network.
You can import your entire beacon fleet from Estimote or Kontakt.io to Bleesk platform in just a matter of seconds:
You can synchronise your entire beacon fleet with Estimote or Kontakt.io cloud if you used Import Beacons feature.
Synchronising beacons saves a lot of time if you use Eddystone-URL campaigns - it allows you to export Eddystone-URL campaigns from Bleesk into your beacon cloud without the need to enter all URLs manually one by one. To synchronise your beacon fleet with Estimote or Kontakt.io cloud:
Please note that when sync with cloud is completed, it is not automatically synchronized with the beacon device until smartphone running the Kontakt.io or Estimote mobile app comes into range of the beacon.
Beacons in range of a Cloud Beacon will be updated when the Cloud Beacon connects to the cloud.
Geofence is less precise than beacons or wifi spots therefore we recommend at least 200 meters as a minimal radius. If you are not able to receive Geofence campaign try increasing radius to 500 meters or moving the pin on a map slightly (geofencing uses operating system location services and sometimes they are not able to assign your position to a specific address).
If you place two Geofence spots in close proximity to each other, users of your app may receive two campaigns at the same time and spot analytics can be doubled.
QR codes are just another type of spot. QR codes have the same ability to initialize a proximity campaign on a user's mobile phone. You can assign any type of campaign to a QR code, just as you would assign it to a beacon. The only difference between QRodes and other spots is that user needs to manually scan the printed QR code with a phone's camera to initialize the campaign on the phone. QRodes are great if you want to grant somebody a coupon, point or stamp for the purchase made - they guarantee that you as a seller have control over who receives it and who doesn't.
Visit our Eddystone & Physical Web guide for more info.
Universal links enable you to send a link to your customers, so after they click on it, it will show them a particular campaign you created:
NFC tags can be used as an alternative way to deliver proximity campaign even if your customer doesn't have a dedicated mobile app installed on the phone!
For example an NFC Tag could be attached to a For Sale sign. Once a customer taps the Tag with his phone, his phone can call the real estate agent or will open a dedicated page (campaign) created in Bleesk with more details about this house. It is up to you and your specific business case to create meaningful connection - the possiblities are limitless.
How to create NFC Tag Campaign:
Bleesk is fully compatible with Eddystone™ protocol and receives campaigns assigned to Eddystone beacons. Eddystone is an open bluetooth protocol, that currently consists of three packets: Eddystone-URL for broadcasting URL addresses, Eddystone-UID for broadcasting beacon’s ID, and Eddystone-TLM for beacon telemetry.
Google stops serving Nearby Notifications on December 6th, 2018.
Make sure you have Physical Web properly set on your device: Setting up Physical Web in Chrome on your Android or iOS device.
Please note that if you want to change or update content, it takes minimum 10 minutes for the changes to be seen live on devices that receive Eddystone URL campaign.
Please note that using Sync Beacons feature only syncs with your beacon cloud - it does not mean that Eddystone-URL will automatically be synchronised with your physical beacons. In most cases you still need to use phone with Estimote or Kontakt.io app that is in proximity of physical beacons in order to synchronise data from the beacon cloud with them.
Each Eddystone-URL created in Bleesk is measured to reflect how many times it was viewed. The data collected by our platform is displayed in the Analytics dashboard