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

# Retrieve Push User ID

You can retrieve your Push User ID using the following steps. This ID can be used for sending test notifications using the `Subscriber ID / Push ID` segment condition or provided to your account manager for debugging purposes.

Using the device on which you are subscribed to notifications, bring your application into the foreground and background 4 times within 20 seconds. The Push User ID is then copied to your device's clipboard.

Paste it anywhere you can type — a note, an email, a chat message — to retrieve it. It will look like this:

```
553a886c1dfc39fc59fbfa477b31b527
```

The ID is copied on its own, so it can be pasted directly into the `Subscriber ID / Push ID` segment condition.

## Performing the steps correctly

Each repetition has to be a genuine background and return, so a few details matter:

* **Leave the app entirely.** Send it to the Home Screen, or switch to a different app. On iOS, opening the app switcher and tapping back into the app is *not* enough — the app never actually goes to the background, so those repetitions do not count.
* **Pause about a second before returning.** Flicking away and immediately back can be too fast for the device to register that the app was backgrounded.
* **Complete 4 cycles within 20 seconds.** The 20-second window slides, so any 4 qualifying cycles that fall inside a 20-second stretch will work — you do not have to start over if you were slow at the beginning.

## What you will see

**iOS**

Nothing is displayed on screen. The ID is placed on the clipboard silently, so paste it somewhere to confirm you have it.

**Android**

A clipboard preview appears in the bottom left of the screen, with options to share the copied Push ID.

![](https://810756845-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lry9Z27iWOZyQEGAgY7%2Fuploads%2FjEk9aZa3zQQutTLcXMtd%2FScreenshot_20230810-085509.png?alt=media\&token=ae6a1b1b-59c4-40a0-97bd-a54d17b02d49)

## If nothing is copied

If your clipboard is unchanged after several attempts:

* Make sure you are reaching the Home Screen or another app on every cycle, rather than only opening the app switcher.
* Slow down slightly and pause about a second in the background each time.
* This feature can be disabled for an individual application. If it has been turned off for yours, the sequence will do nothing — contact your account manager to confirm.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://documentation.pushly.com/faq/native-app-push/retrieve-push-user-id.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.
