Introduction to Eddystone & Physical Web

appSAVE® 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 stopped serving Nearby Notifications on December 6th, 2018 but appSAVE® can serve these Nearby Notifications via. the Eddystone URL.  Note the comments below this graphic.

The Eddystone platform was developed to allow developers the ability to deliver messages without the end user needing to install an app.  

But since Google discontinued Nearby Notifications on December 16, 2018, the ability to deliver a message to phones without an app was also discontinued. 

This section is to allow developers who have the Eddystone beacons the ability to still use them because appSAVE® is compatible with Beacons with Eddystone-URL. appSAVE® broadcasts URLs with campaigns directly to any iOS or Android device and displays it in the notification area.

Adding Eddystone-URL Beacon

  • Go to Beacons & Other Spots list and click Add Spot.
  • Pick a name for your Eddystone-URL spot.
  • Choose Beacon as a Spot Type.
  • Choose Eddystone-URL as a desired Protocol.
  • Click Save Beacon and that's it.

Create Eddystone-URL Campaign

  • Add Eddystone-URL Beacon (see above.)
  • Create Content. See Create Content.
    Please note that if you want to change or update content, it takes a minimum of 10 minutes for the changes to be seen live on devices that receive Eddystone URL campaign.
  • Create a campaign with the content you created above as Default Content and Eddystone-URL beacon as Trigger.
  • Go to your Beacons & Other Spots list on appsave Fleet.
  • Export Eddystone-URL created in appSAVE® to your beacon.
  • There are two ways to do this:

The First Way is to copy the URL next to the Eddystone-URL beacon to which you have assigned your proximity campaign (highlighted in yellow): and paste the copied URL in the Eddystone-URL field of your physical beacon. This can be done either in the beacon provider's admin panel (for example Estimote Cloud) or beacon provider's mobile app (for example Estimote App). Here are more detailed articles how to do it for Estimote and since Google made their change above, there is now no longer any way to do this for beacons.

The second Way is if you have previously Imported Beacons from Estimote or cloud into appSAVE® you can now export Eddystone-URL created in appSAVE® to your external beacon cloud automatically by using Sync Beacons button. This needs to be done only once for a beacon and after that every time you update your campaign in appSAVE® the change will be automatically reflected in your Eddystone-URL beacons as well.

Please note that using Sync Beacons feature only syncs with your beacon cloud - it does not mean that Eddystone-URL will automatically be synchronized with your physical beacons. In most cases you still need to use a phone with Estimote or app (appSAVE®) that is in proximity of physical beacons in order to synchronize data from the beacon cloud with them.

Eddystone Analytics

Each Eddystone-URL created in appSAVE® is measured to reflect how many times it was viewed. The data collected by our platform is displayed in the Analytics dashboard. 

Eddystone-URL Tips & Troubleshooting

  • If you can't receive campaigns broadcasted by your Eddystone beacons please make sure your device is configured properly by following instructions available on the Physical Web project page.
  • Please be aware that Google caches and filters URLs that are being detected by your phone. Before anything is displayed on your phone, Eddystone-URL packets are sent to Google and it's ultimately Google that decides what and when is being shown to an end-user.
  • Sometimes however, especially with Android devices, the problem might lay in a Bluetooth hardware on your phone. Different manufacturers use different Bluetooth chipsets, antennas, drivers, OS versions, etc. Those combinations can result in a varying quality of Bluetooth scans. We've already received a number of reports from customers saying that the same beacon, in the same app is detected easily on one phone, but not the other. Unfortunately, that's beyond our control.
  • Note that appSAVE® also supports Eddystone-UID campaigns.
Because of these issues we strongly recommend you become familiar with the new Google AMP format for your URL links. Google likes the AMP protocal, that's why they developed it.
See (The evolution of Apps.)