> For the complete documentation index, see [llms.txt](https://doc.batch.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.batch.com/guides-and-best-practices/message/push-notifications/how-to-send-a-test-push-notification-to-your-mobile.md).

# How to send a test push notification to your mobile?

You can add a test device and target it from the dashboard to ensure your notification is displayed correctly.

Batch allows you to find information on your installation and test your integration or make sure the notification you are editing works as expected on a real device (deeplink, image, mobile landing, etc).

The easiest way is to use either your Installation ID ([iOS](https://doc.batch.com/developer/sdk/ios/troubleshooting#displaying-a-stable-debug-id)/[Android](https://doc.batch.com/developer/sdk/android/troubleshooting#displaying-a-stable-debug-id)) if it is displayed in your app, your Custom ID ([iOS](https://doc.batch.com/developer/sdk/ios/profile-data/custom-user-id)/[Android](https://doc.batch.com/developer/sdk/android/profile-data/custom-user-id)) if it is sent to Batch, or the email address linked to the profile if there is one. Once you retrieve your ID, go to point 2.

## 1. Locate your Installation ID

💡 From version 1.18 of our SDK, you can find your Installation using the "**Find my Install**" feature.

Batch will copy the Installation ID to the clipboard when the application appears in the foreground 4 times within 20 seconds.

{% hint style="warning" %}
Here is how to find your Installation ID:

* [On iOS](https://doc.batch.com/developer/technical-guides/how-to-guides/how-to-find-my-installation-id-on-an-ios-device)
* [On Android](https://doc.batch.com/developer/technical-guides/how-to-guides/how-to-find-my-installation-id-on-an-android-device)
  {% endhint %}

## 2. Find your device <a href="#id-2-find-information-on-your-device" id="id-2-find-information-on-your-device"></a>

On the dashboard, go to **Data** > **Find Profile**, and paste your ID (with the correct ID type selected):

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FW9QSV9CEkTqppmqqfXh9%2FCleanShot%202026-10-20%20at%2017.35.10%402x.png?alt=media&amp;token=71b1931e-fd14-45b0-92f0-29a09bf59533" alt=""><figcaption></figcaption></figure>

In the **Platforms** section, find your device and click on **Inspect:**

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FUaduXMqIuaMoWV9TfPzm%2FCleanShot%202026-10-20%20at%2017.38.25%402x.png?alt=media&amp;token=057b9c92-950b-4c90-9984-fc002750c244" alt=""><figcaption></figcaption></figure>

This opens the device pop-in, which shows the information Batch has on your device. From this pop-in, you can send a test push and save the device as a test device:

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FC7iw0QL67t3ZCYm8VCEc%2FCleanShot%202026-10-20%20at%2017.40.20%402x.png?alt=media&amp;token=7c735a5f-35d5-4ab7-9ad2-1d84483de25f" alt=""><figcaption></figcaption></figure>

## 3. Send a test notification <a href="#id-3-sending-a-test-notification" id="id-3-sending-a-test-notification"></a>

You can send a test notification from 2 places:

### a) From the device pop-in <a href="#a-from-the-debug-tool" id="a-from-the-debug-tool"></a>

In case you just need to test your integration, open the device pop-in (see step 2) and click **Send test push**. Batch sends a test notification to this device.

### b) From the message editor <a href="#c-from-the-campaign-editor" id="c-from-the-campaign-editor"></a>

To see how your own notification looks on your device, send a test from the message editor. You can send a test two ways:

* Click on **Send Test** **> Saved recipients** and select the recipient you want to send the test to, then hit **Send test.**

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FjYESedJvLc9li2In3MNc%2FCleanShot%202026-06-30%20at%2014.19.47%402x.png?alt=media&amp;token=5b086f61-42e7-4ebf-bc55-b3ef1cf56272" alt=""><figcaption></figcaption></figure>

* Click on **Send Test** **> One-time recipient**, choose the identifier type (**Custom ID**, **Installation ID** or **Push Token**), enter it in the corresponding field, then hit **Send test:**

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2FcYG5utZATps0VvcnVXqn%2FCleanShot%202026-06-30%20at%2014.20.49%402x.png?alt=media&amp;token=37ece370-5d56-4cfb-82cc-9a66ed4564c3" alt=""><figcaption></figcaption></figure>

## 4. Save your device as a test recipient <a href="#b-from-the-list-of-registered-test-devices" id="b-from-the-list-of-registered-test-devices"></a>

You can save a test device once and reuse it for every future test, instead of looking up its Installation ID or Custom ID each time. There are two ways to do it:

* From the device pop-in in **Data > Find Profile** (see step 2): click **Save test device**.
* From **Settings > Channels > Push**, under the **Test recipients** tab. Click **New recipient**, give it a name, and enter its Custom ID, Installation ID, or Push Token:

<figure><img src="https://509463063-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FfiAYaWDWqtFZeXxyg67F%2Fuploads%2Fw4sMgrcVMviMxLAqowya%2FCleanShot%202026-06-30%20at%2013.39.18%402x.png?alt=media&amp;token=4d520ccd-e909-481c-b266-f7b8e34fab86" alt=""><figcaption></figcaption></figure>

Recipients saved this way are available at the project level and can be selected directly when sending a test from the Push, In-App, or Mobile Landing message editor.


---

# 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://doc.batch.com/guides-and-best-practices/message/push-notifications/how-to-send-a-test-push-notification-to-your-mobile.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.