[null,null,["最后更新时间 (UTC):2025-08-13。"],[[["\u003cp\u003eTo maximize effectiveness, Nearby Notifications attachments should be relevant to the user's location, broadly appealing, and have a clear call to action.\u003c/p\u003e\n"],["\u003cp\u003eAttachments must adhere to content policies, use HTTPS URLs, and avoid unsupported link formats.\u003c/p\u003e\n"],["\u003cp\u003eNotifications may not appear if the attachment has low user engagement, the device screen has been off for a while, or the notification was recently dismissed.\u003c/p\u003e\n"],["\u003cp\u003eNearby Notifications supports Android 4.4 (KitKat) and newer and works in conjunction with Eddystone-URL and Physical Web.\u003c/p\u003e\n"],["\u003cp\u003eAttachments require a specific data format and should be registered using the Proximity Beacon API, often by the beacon owner.\u003c/p\u003e\n"]]],[],null,["# Frequently Asked Questions\n\nHow do I make a great attachment?\n---------------------------------\n\nNearby Notifications will display messages in the Nearby section of Google Settings,\nlight up the Nearby Quick Settings tile on supported devices, and will promote\nthe best performing attachments as notifications.\n\nFor maximum effectiveness, attachments should:\n\n- Point users to apps or websites that some users already visit in that location.\n- Be appealing to most users who will receive the notification.\n- Optimizing the beacon location may help target only interested users.\n- Have a direct call to action and avoid surprising the user.\n- Strive for messages that receive positive user engagement.\n- Adhere to the [Nearby Notifications policies](/nearby/notifications/policies) to maintain a positive experience for our users.\n\nMy attachment doesn't show in the Nearby section of Google Settings. Why?\n-------------------------------------------------------------------------\n\n- There are a few constraints on messages we show, such as only allowing HTTPS URLs and disallowing content that violates our [policies](/nearby/notifications/policies).\n- Links to play.google.com are not supported. Instead use [App Intent attachments](/nearby/notifications/attachment_data_format#app_intent) to enable an experience powered by an app.\n\nMy message is not being shown as a notification. Why?\n-----------------------------------------------------\n\nThere are several reasons a notification may not appear.\n\n1. A notification won't show if the attachment is not well received by users. Tips for creating a great attachment can be found above.\n2. Nearby Notifications typically scans for beacons for a few seconds after the screen is turned on. If the screen has not been turned on for a while, the device won't discover new beacons.\n3. An attachment in Debug mode will only show on debug mode devices. Also see [Debug mode](/nearby/notifications/debug_mode)\n4. If the notification has been dismissed on a device recently, that device may not show another notification a period of time. The backoff policy is also reset if the user opens the Nearby section of Google Settings.\n5. A notification may not show if it violates the [Nearby Notifications\n policies](/nearby/notifications/policies).\n\nWhich Android versions support Nearby Notifications?\n----------------------------------------------------\n\nNearby Notifications is supported on Android 4.4 (KitKat) and newer.\n\nHow does Nearby Notifications relate to Eddystone-URL or Physical Web?\n----------------------------------------------------------------------\n\nNearby Notifications works in parallel with Eddystone-URL and Physical Web with the\nexact behavior depending on your use-cases and capabilities. For example, if you\nhave one use-case that is available on your website, you might use an\nEddystone-URL beacon. If the use-case is available in your app, you might use\nNearby Notifications with an app intent.\n\nWhat is the required format for Nearby Notifications attachments in the Proximity Beacon API?\n---------------------------------------------------------------------------------------------\n\nSee [Attachment Data Format](/nearby/notifications/attachment_data_format) for\ndetails. In short, attachments should take the following form: \n\n {\n \"title\": \"Example\",\n \"url\": \"https://www.example.com\"\n }\n\nIn the Nearby Notifications attachments, how is title used?\n-----------------------------------------------------------\n\nThe title will appear in the notifications and lists that are displayed by\nNearby Notifications. For example, if your title is set to\n\"Example action at place\", the notification text will appear as\n`\"Example action at place\"` in addition to the app name or URL.\n\nDoes Nearby Notifications install the app in the background?\n------------------------------------------------------------\n\nNo. Nearby Notifications will redirect users to the Google Play Store to install\nfrom there.\n\nHow do I know if a user came to my app via Nearby Notifications?\n----------------------------------------------------------------\n\nNearby Notifications links are standard Android deep links, but if you want to\nsupply additional tags, for example, for metrics or analytics, you can add query\nstring parameters into the path component of the intent URL.\n\nDoes Nearby Notifications support iBeacon?\n------------------------------------------\n\nYes, as long as the beacon has a static iBeacon ID. These IDs can be registered\nin the Proximity Beacon API, and can have Nearby Notifications attachments.\n\nWhere and when does the scanning happen, if not in my app?\n----------------------------------------------------------\n\nThe scanning is performed by Google Play Services, and only at \"screen-on\"\nevents.\n\nWho is responsible for registering the beacons in the Proximity Beacon API?\n---------------------------------------------------------------------------\n\nAnyone can register the beacon, as long as the attachment has the right\nnamespace and type. In most cases this will be the owner of the beacon, but may\nbe the beacon OEM if you are under contract with them.\n\nWhat is the format of the app intent URI?\n-----------------------------------------\n\nFirst, with the [Beacon Dashboard](https://developers.google.com/beacons/dashboard)\nyou can let the web frontend construct a valid URI for you provided you\nunderstand the scheme, host, and path parts of the URI. Here's an example:\n\nIf you want Nearby Notifications to launch the activity in your app that has the\nfollowing intent filter: \n\n \u003cdata android:host=\"item\"\n android:pathPrefix=\"/scanner\"\n android:scheme=\"myapp\" /\u003e\n\nThe corresponding intent:// URI would be: \n\n intent://item/scanner#Intent;scheme=myapp;package=com.myapp;end\n\nThat is, the URI can be broken up as such: \n\n intent://\u003chost\u003e/\u003cpath\u003e#Intent;scheme=\u003cscheme\u003e;package=\u003cpackage name\u003e;end\n\nIf your activity requires intent extras, these should be added just before\n`;end`: \n\n intent://item/scanner#Intent;scheme=myapp;package=com.myapp;S.string_extra=value%20one;B.bool_extra=true;end\n\nThe following types can be used in extras:\n\n- Boolean\n- Byte\n- Char\n- Double\n- Float\n- Int\n- Long\n- Short\n\nAlso see [Intent.java#parseUri()](https://developer.android.com/reference/android/content/Intent.html#parseUri(java.lang.String,%20int))\nand [Intent.java#toUri(int)](https://developer.android.com/reference/android/content/Intent.html#toUri(int))\nin the context of [URI_INTENT_SCHEME](https://developer.android.com/reference/android/content/Intent.html#URI_INTENT_SCHEME)\nfor more details about this intent URL.\n\nWhat about localization of the title Nearby Notifications uses?\n---------------------------------------------------------------\n\nNearby Notifications attachments must include the language/locale as part of the\nnamespace/type, and Nearby Notifications will only surface those attachments that\nmatch the user's locale settings."]]