Your campaign (markdown card, custom URL or an interactive form) is initially treated as a message. 

The message is seen in the Nearby section of Google Settings and the Nearby Notification Quick Settings tile lights up on supported devices. Once this message starts performing well, it gets raised to a notification.

Read how to create an effective notification.

Some other reasons why notifications may not show up

  • Links to play.google.com are not supported. Use the App Intent feature on Beaconstac to send users to open or download your app. 
  • Only URLs containing HTTPS are allowed
  • Content that violates Nearby Notification policies is not allowed.
  • If the campaign is not well received by users, notifications won't show up.
  • Google Nearby scans for beacon signals for a few seconds after the screen is turned on. If the screen hasn't been turned on for a while, the device will not discover new beacons. 
  • The user needs to be in the range of the beacon for at least 1-5 minutes for notifications to show up.
  • If a user dismisses a notification on a device, it will not show up another notification for a period of time. This is known as the backoff policy and can be reset if the user opens the Nearby section of Google Settings. 

Destination requirements that notifications must meet

Notifications need to meet some destination requirements. Once a user clicks on a notification, it should take them to a URL or app that is secure, functional, useful, and easy to navigate.

Sites that do not meet the destination requirement are - 

  • Websites or apps that are still under construction or are parked domains or do not work.
  • Websites that cannot be viewed in commonly used browsers.
  • Websites that have the browser's back button disabled. 
Did this answer your question?