I want to find the statics of beacon.
How can i find that how many push notification is sent for Beacon from chrome application.
If you are asking about the number of devices that received your notifications, you can use an URL shortener such as goo.gl and get the stats from there.
Related
I ask the user for a review at the end of the conversation using a basicCard.
It is not possible on a device with no screen or web browser so essentially I can only ask for reviews when my action is used on an android or iOS device.
So, is it possible to send a notification from the user's non screen device to his phone?
You can use multi-surface conversations, which will allow you to send a notification from a speaker to a phone to continue the conversation with the same session.
Google has discontinued Near By API by the end of 2018. Android OS had built in support for Near by API and hence without a custom APP , the device was able to capture the beacon based push notifications.My requirement is as follows:
With Digital loyalty pass on Google wallet, when the end customer enters the vicinity of a beacon , the device should receive offers as push notification. There is no custom app developed . With out a custom app , how to receive the push notifications with just the Digital loyalty pass on google wallet? . Please help with a solution.
Please refer https://android-developers.googleblog.com/2018/10/discontinuing-support-for-android.html
Unfortunately after Google Nearby was discontinued, there is no longer a solution to send notifications to a user on BLE detection without a third party app installed to do so.
The only workaround is to develop a third party app to do the detecting and notifying. Keep in mind that the way Google implemented this was with the Google Play Services app, so an app was still required to send the notifications. (It was just an app that was installed by default on most phones sold outside of mainland China.). And it didn't even work unless a user had opted in, something that few ever did.
Google's Nearby discontinuation basically says Google is no longer willing to use their app to send notifications for you. So you must use your own app or the app of a different partner.
There are other third party apps that track a user's location and send notifications -- such apps are often popular "free" games. But while the install base of these apps can be in the hundreds of millions they do not approach the install base of Google Play Services. These apps can also be a bit "shady" about their practices, and to my knowledge do not have a public policy about how you can get them to send notifications for you or let users opt-in or opt-out.
I have a beacon that is transmitting Eddystone - URL. I can locate my beacon using the Physical Web app in Android. I read that from Chrome 49 Physical web is by default supported by chrome but I'm using Chrome 69 version but I didn't get any nearby notification. In short my questions are,
Does Chrome by default support physical web? and if it does should I have to open the chrome app to get my notifications displayed?
Do people need to have any specific app to get nearby notifications?
You must actively turn on Physical Web in Chrome for Android's privacy settings as described here.
These notifications can also be delivered by Nearby, which requires Google Play Services, but no other apps on the phone. Most Android devices outside of China have Google Play Services installed, but those in China as well as Amazon Fire tablets and some other devices do not, and will not receive these notifications. The link above also describes how users must opt-in to Nearby notifications. If they do not opt-in, they will not get the notifications.
I want to push notification to users when in my beacon's proximity. That's pretty easy if I register my beacon on Google Beacon Platform using Proximity Beacon API and then register Nearby Notification against it. I do not want to register the beacon on Google Beacon Platform and still throw a notification to user through Nearby Notification API.
If you want to Google Nearby to be triggered by a beacon, you have no choice but to register the beacon with the Google Beacon Platform. That's how it works. Nearby is a system that relies on server-side configuration to send messages to a user.
That said, it is possible to send regular Android notifications to a user when they come across your beacon without registering with the Google Beacon Platform. To do this, you must have your own custom app installed on the user's phone.
You can see an example of how to do this with the Android Beacon Library in the "Getting Notified When Beacons Appear in the Area" section of this page. A more sophisticated example that scans in the background and sends a notification to the lock screen on beacon detection is in the library's reference app.
I have a beacon which support eddystone protocol. And I see some app through which you can change the UID of beacon. Even tough when I scan my beacon with android beacon tool I am unable to register it as it says that "the beacon is locked". My question how it is possible to change UID when it is hard-coded inside a chip? I may be totally wrong. And also when I use eddystone validator app it display the becaon but the UID is blank.
Look for a mobile app from the company that sold you the beacon. Identifiers are typically configured over a connectable Bluetooth service. Vendor-specific apps allow you to enter a new identifier and send it to the beacon when it is in Bluetooth range.