The ultimate Nearby Notification troubleshooting guide

Notification not showing up? Here’s a step-by-step guide explaining what to do!
The support team at Beeem – after a few hundred customer support cases – has compiled the ultimate guide to troubleshoot your Nearby Notifications. As Google keeps the filtering algorithms a secret, the novice beacon user- especially the proximity marketing professional just starting out – may come across a myriad of issues during initial setup from hardware, to the 
phone settings, to content issues. Let’s do this!

I. Phone settings
The biggest chunk of the issues stems from simple things that anyone can check on their phones. Most of our support experience tells us, this is the place to start!
1. Does the phone have access to the Internet?
Please check if the phone has mobile data ON or is connected to a Wi-Fi Network. If you have a poor data connection (Edge or 2G) it might not enable Google Nearby to receive the data back from Google servers in time so notifications may not always appear.
2. Does the phone have Bluetooth on?
Most people have Bluetooth turned on most or all of the time and Bluetooth penetration is continually growing like Wi-Fi did 5-6 years ago. Please re-check your phone settings. Note: There is nothing else required in Bluetooth realm to get Notifications: there is no pairing or anything similar!
3. Does the phone have Location (sometimes called GPS) on?
As Google deems Nearby Notifications to be using location information of the device, so a setting called Location (called GPS on some Android ROMs) has to be on even though Notifications don’t use the phone’s GPS directly.
4. Has the beacon been in the range of the phone for enough time?
In some cases, we experience that the phone has to be in the range of the beacon for quite some time before a notification shows. The most we’ve experienced is about 1 hour, but an 5-8 minute wait is the norm. Also please note that you can trigger a manual scan for beacons by turning the phone screen off and then back on! Please note that beacon scanning can take a few seconds as well so please wait a few seconds on the notification list too.
5. Have you tapped on a notification, exited Nearby and don’t get it anyomre?
Google Nearby deems a notification “used” if you tapped on it and the page is still running inside the Nearby App. If you want the notification to appear again, close the Nearby App, turn your phone screen off and back on to trigger beacon scanning and get to your notification list!

II. Beacon settings


Time and time again we see the most trivial solutions to a beacon “not working”. Let’s go through them all!
1. Is it turned On? Is the Battery on?
If your beacon has an indicator light make sure it’s on. If you have no such options, make sure the beacon is on by checking the battery or going directly into the beacon’s own configuration app. If you don’t know what app to look for you can use the NRF connect app for iOS and Android to do a hardware-level scan for your beacons.
2. Is the beacon configured to be broadcasting an Eddystone URL?
In some cases, the beacons are left in iBeacon mode and are not broadcasting the URL but iBeacon IDs. You can check this by going directly into the beacon’s own configuration app. If you don’t know what app to look for you can use the NRF connect app for iOS and Android to do a hardware-level scan for your beacons!

III. Beacon page content issues
This is the most overlooked part of Nearby Notifications. Everyone expects to blast a badly written website running on a poorly performing server and is let down by the results. But if you look at it from the perspective of Google: do I really want to flood the notification list with items that provide a poor UX to my phone users? The answer is clearly no and you can’t blame them for doing it. So if you’re looking to blast irrelevant messages at crowded locations you’re most likely to see poor results especially compared to your expectations. Here’s all you need to know
1. Is the URL valid (Skip if you use Beeem!)
There is only one resource that the Physical Web team at Google provides to check your beacon URLs. The Physical Web validator will test your URL shorteners and destination URLs for technical issues that prevents Google servers from successfully crawling your URLs and displaying Nearby Notifications. NOTE: this test is only for the URL itself and not the content on the URL!!
2. Is the end URL exclusively HTTPS(Skip if you use Beeem!)?
This part is covered in the last test but there is so much confusion out there that I’d like to clarify this. The technical specification for Nearby Notifications requires exclusively HTTPS content on the final URL (including any image on the page for example). So if you have any mixed content warnings for your destination URLs you’ll be filtered out, no questions asked. Please also note that even though the destination URLs have to be HTTPS exclusively, any forwarder in use can be HTTP!
3. Do you have any page content that cannot be promoted with Nearby Notifications?
Did you know that there are a ton of requirements to meet with your content? These are the most basic types of content filtered out:
Adult Content
Content that exploits children
Dangerous and Widely Illegal Content
Content that is not clear, unprofessional in appearance and that is not useful for recipients
Harassing, bullying, or threatening behavior, and do not incite others to engage in these activities
Hate Speech
– Malicious Content Distribution
– Mature Text / Profanity
– Personally Identifiable Information
– Regulated Goods & Services
– Spam
– Terrorist Content
– Violence & Shocking Content

As you can see Google filters you out in pretty much the same cases as they do with Google search. Even if you’re not intending to publish any such content it is good to know that the filtering algorithms are in place. In case your notifications still do not appear, please make a page that contains no such text content (like a template page in Beeem for example) that you can be 100% sure it’s complying.

The future of apps is no apps: your mobile audience is just 2 taps away

We are pleased to announce the most important release of Beeem in our short history. It’s jam-packed with all of the top requests: unlimited storage for your page content, page, and project analytics even displaying movement from one page to the other! We’re also happy to announce our Free, Starter and PRO plans!

Your mobile audience is just 2 taps away

Beeem is the fastest way to create a mobile website. Now we will help you engage anyone on mobile in just a few minutes without a mobile app! Reach all of your mobile audience with Physical Web Beacons on Android and QR codes on iOS 11!

Physical Web on Android

QR codes in iOS Camera

91% of all Android phones out there today support the physical web! That means that all you have to do is place a Bluetooth beacon inside your location to engage anyone on Android! Cool right?

Well, your Bluetooth beacon is free with every annual Beeem subscription! Check out our plans @

Learn how the ITTF used Beeem as a mobile engagement service to engage 14% of the entire stadium attendance at the Table Tennis European Championships

Have you heard about the QR code scanner in the camera app coming in iOS 11?

Check out this video! We think it’s going to transform the mobile engagement space with all sorts of possibilities!

Think about it: the camera app is on the home screen of every device out there and finally, Apple developed QR code functionality that is actually cool: it works like a charm and it’s as fast as a Physical Web beacon on Android!

Find the perfect plan for your perfect page

TOP 4 things to watch out for on Chrome for Android with beacons!

TOP 4 things to watch out-for on Chrome for Android with beacons

As all of you know, Google has finally launched the new Chrome for Android (version 49) to push physical web capabilities to some 5 million users. Here are the key takeaways from the experience of our users:

1. Use HTTPS! 

Chrome for Android does not let any HTTP URLs through! Even though Chrome for iOS works with HTTP URLs, it seems that Chrome for Android does not let them pass at all! Last week we added full HTTPS support to Beeem to enable anyone to create a landing page with the physical web fully compliant with Google’s high security standards! This will add an extra layer of secutiry to users that will ensure that the physical web is going to be even more secure than the web itself!

2. Watch out for your OEM Android! 

With dozens of big Android vendors, everyone tries to get the maximum out of their phones. Several manufacturers use some sort of battery/performance optimization tools that tweak several things that might prevent from Chrome for Android in locating physical web beacons. The usual suspects are: Battery/performance profiles turning Bluetooth off (even if they are turned on in Android settings!) and preventing Chrome for Android launching on Boot. In our direct experience there is no single cure you should tweak around and wait as Google’s services may not locate physical web beacons on the fly (like on Chrome for iOS). Let’s hope this improves later on.

3. Turn it ON! 🙂

No matter how simple it seems, as Chrome does not prompt you to turn Bluetooth or the Physical web on, you might want to start with checking Bluetooth in your Android Settings and Enabling the Physical Web on Chrome @ Settings/Privacy/Physical Web! If you’re still stuck, you can take a look at Google’s help.

4. Make sure your URL makes sense to the visitor!

If you followed these key steps all you have to do is make sure you have a meaningful landing page for your Beacon: beacon URLs only make sense if the provide real value to users! Keep in mind that the key to the physical web is interaction on demand. We’ve created the simplest and most powerful landing page editor for the physical web. You should try it out @ now!

With these key steps, you should be good to go with the physical web on Chrome for Android! Enjoy!

5 ways the physical web will move beyond beacons

5 ways the physical web will move beyond beacons

A few days ago Jeanette Cajide, VP of Corporate Development for Dialexa wrote a post on the Huffington Post on beacons. The post is a great summary of the shortcomings of the iBeacon area: the adoption rate of beacons has been slow and users have not gotten a single, seamless point of entry on their UI for proximity-based content and interaction. 

In this post, We will elaborate on how Google’s concept of the physical web will move beyond the shortcomings of the iBeacon-area of proximity-based apps:

  1. No app downloads
    The physical web will remove the no. 1 obstacle between mobile users and the places they visit: the dreaded app download. With browsers (like Chrome on iOS soon available on Android too and Opera) and mobile Operating Systems (like Chrome OS and Firefox OS) getting physical-web enabled rapidly soon over a billion devices on the planet will have a single point of entry for proximity-based content and interaction: the lockscreen.
  2. No direct messaging
    The physical web will do away with the privacy concerns of smartphone users: Google has implemented several measures to make sure no contact is necessary during service discovery.
    As with web search, Google handles the storing and sorting of information but without any direct control over the content of the URLs the service completely open and free. The formal nature of the web will make sure that no nagging mobile messaging will be without opt-ins. The clear standardized vision of the W3C on the matter is already implemented by Google in Chrome 42 on Android.
  3. Users opt-in with taping at content they choose
    The alarming opt-out rates discussed in Jeanette’s post are a clear sign that users do not want their smartphones to turn to a proximity-enabled ad-machines.
    This will be best served by Eddystone beacons and Google’s back end services acting as a proxy between the advertised URLs and the smartphone users. Browsers do not talk to the web servers directly during discovery: only after taping at a particular URL will the browser be launched and direct communication between the user’s phone and the website begin.
  4. A clear path on the UI for proximity-based content and interaction
    We will get rid of looking for and downloading QR code reader apps, pointing cameras at codes that do not seem to work, we will get rid of service discovery issues in app-based beacon-enabled content and interaction. The browser will serve as the principal source of content and interaction around us and will serve the relevant places and things at our convenience at a single point of entry: the lock screen.
  5. No beacons!
    The most promising feature of the physical web is not requiring installed, dedicated hardware: The Wi-Fi Alliance is already pushing Wi-Fi Aware to rival Bluetooth Smart and both Mac OS X and Windows 10 have universal Bluetooth libraries that enable 240 000 000 PCs in the world to power the physical web and act as Bluetooth beacons today.

With these advances, app-less proximity-based content and interaction will soon be available to practically anyone regardless of mobile platform, physical location and market size.

Try world’s first content and interaction platform for the physical web that will enable all of these advantages, sign up for Beeem now!

#physicalweb #ibeacon #eddystone #beacon

4 peeks at the future of mobile life

4 peeks at the future of mobile life

With a host of exciting news in recent weeks the future of proximity-based interaction on mobile looks ever more promising. Innovation in the domain is stepping up with several players producing wonderful results from the likes of the Wi-Fi Alliance, Opera Software, the Mozilla Foundation and Google.  

In this post, we will take a look at the 4 major areas of innovation that will shape proximity-based content and interaction on mobile:

  1. Proximity-based content and interaction from Bluetooth to WiFi
    With the Wi-Fi Alliance introducing the specification of Wi-Fi Aware the most obvious networking base technologies already actively support proximity-based mobile interaction. In the near future there will be a host of possibilities to advertise proximity-based content and interaction to nearby mobile devices: with the Bluetooth stack inching towards massive acceptance, the rival Wi-Fi stack is catching up.
    Patrick Keane’s recent tutorial on how to set up a simple mDNS physical web advertiser is a great example of what’s to come: beacons will play a role whenever infrastructure is not set for a long term for example at events. In other industries like retail Wi-Fi-based technologies will compete beside Bluetooth beacons for the role of infrastructure for the physical web.
  2. Engage with Mac and Windows without beacons
    The most attention in proximity-based mobile technologies was stolen by beacons: the iBeacon vs. Eddystone war is a great example of how the big tech companies can steal the attention of the media with a standards war.
    But there is a large untapped set of beacons available right now everywhere in the world: users of Mac OS X and Windows 10.0 can simulate beacons with the Bluetooth radios of their computers. With Mac OS X hovering around a 5% global market share and the affected version of Windows holding a close to 7% according to PC World, 1 in 4 computers in the world is capable of proximity-based content and interaction right now. That is a whopping 240 000 000 potential software-based beacons compared to a few million beacons currently in use.
    The first attemt at simulating physical web beacons was made available by Mikael Jergefelt on Github. A big thank you is well deserved for all contributors! The project is available at the following link.
    Another noteworthy project on the subject is Chrome OS. François Beaufort’s recent post points out that Chrome OS devices are now capable of advertising as an Eddystone beacon that will play a major role in digital signage among other areas.
  3. Go app-less in any mobile browser with the physical web
    Opera Physical Web Beacons with Beeem
    One of the most exciting pieces of news in recent weeks has been the post of Opera Software’s Bruce Lawson on Opera Labs’s latest Android release with their implementation of the physical web. The early development release is a very pleasant surprise. The interface is well thought out, the recognised eddystone beacons are well complemented with georeferenced wikipedia and other complementary content that creates a great UX. We truly see the future in this release and hope other browser developers are soon recognizing the importance of implementing the physical web in their strategies to provide proximtiy-based content and interaction on mobile.
    Among the innovators from Norway, the folks at Firefox OS team have already implemented the physical web and are hard at work at WebBluetooth. Jan Jongboom’s post on the matter is a great read and a wonderful look at the future of mobile computing in general.
  4. Mobile notifications from your favourite website
    Mobile notifications on Chrome 42 on AndroidWith the release of Chrome 42 on Android mobile notifications can be pushed to a Chrome user even when the browser is not running. With app usage concentrating to just a few apps Google’s vision is to empower the web with a set of features that will make it much more easy and convenient to use websites on mobile just like any app. This vision of the mobile web is further expanded with the physical web: adding a layer of physical context of the places and events around us will open up new advances in mobile computing.

Try world’s first content and interaction platform for the physical web that will enable all of these advantages, sign up for Beeem now!

#physicalweb #ibeacon #eddystone #beacon