> For the complete documentation index, see [llms.txt](https://documentation.pushly.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://documentation.pushly.com/faq/web-browser-push.md). # Web / Browser Push - [Common Questions](https://documentation.pushly.com/faq/web-browser-push/common-questions.md) - [Browser Support](https://documentation.pushly.com/faq/web-browser-push/browser-support.md): Pushly supports all browsers that currently implement Web Push. - [Retrieve Push User ID](https://documentation.pushly.com/faq/web-browser-push/retrieve-push-user-id.md): For individual user troubleshooting, your Account Manager may ask you to supply your Push User ID - [Not Getting Prompted](https://documentation.pushly.com/faq/web-browser-push/not-getting-prompted.md): When internal users at a Pushly partner are not seeing the opt-in flow, it is often caused by having dismissed or blocked the Notification opt-in flow. Follow these steps to opt-in. - [Not Receiving Notifications](https://documentation.pushly.com/faq/web-browser-push/not-receiving-notifications.md): When users have opted-in to web push notifications on a website, but are not receiving notifications, there could be a few different things causing this. Follow these four steps to help. - [How to Unsubscribe](https://documentation.pushly.com/faq/web-browser-push/how-to-unsubscribe.md): If a subscribers wishes to stop receiving Notifications from your site, you can send them the information below. Your Account Manager can supply you with step-by-step instructions for use as well. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://documentation.pushly.com/faq/web-browser-push.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.