> 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/retrieve-push-user-id.md).

# Retrieve Push User ID

For individual user troubleshooting, your Account Manager may ask you to supply your Push User ID

If a member of your team or a subscriber are having consistent difficultly seeing the opt-in flow, getting Notifications, or other cases related to subscriber experience, please follow the below instructions for retrieving the applicable Push User ID (PUID). This information can be sent to your Account Manager for additional assistance: 

* Using the device on which you subscribed or wish to subscribe - go to the homepage of the site on which you are having issues, [<mark style="color:blue;">alloceannews.com</mark> ](https://documentation.pushly.com/faq/web-browser-push/www.alloceannews.com)for example<br>
* Add *?push\_debug=1* to the end of the  URL and press Enter. The resulting URL in this example would be:
  * [<mark style="color:blue;">https://www.alloceannews.com/?push\_debug=1</mark>](https://www.alloceannews.com/?pushly_debug73485=1)
  * Replace “alloceannews.com” with the domain on which you are trying to solve an issue, resulting in <https://www>.*yourdomain.com*/?push\_debug=1<br>
* Scroll until you see the blue “Push SDK” tab (usually on the left side of the screen, towards the bottom of the page)<br>
* Click on the tab and Copy the details and send the information to your account manager[<br>](https://www.alloceannews.com/?pushly_debug73485=1)

  <figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2Fi7MUjX06FO0U836uJFgj%2FScreen%20Shot%202022-09-09%20at%209.56.28%20AM.png?alt=media&amp;token=77f35aad-8797-4c6a-bea9-dd21585d255e" alt=""><figcaption></figcaption></figure>

<figure><img src="https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2FqEvsJTx4GKUVVCkJvJDH%2FScreen%20Shot%202022-09-09%20at%209.56.35%20AM.png?alt=media&amp;token=294820ce-58aa-48ac-b0c0-36992b63ccbd" alt=""><figcaption></figcaption></figure>


---

# 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/retrieve-push-user-id.md?ask=<question>&goal=<user_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.