> 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/in-app-messaging/how-to-send-yourself-a-test-for-in-app-messages.md).
# How to send yourself a test for In-App messages?
Here are the steps you need to take to preview an In-App message on your iOS or Android device.
In-App Messaging allows you to communicate with your users while they are browsing the app, even if they did not accept push notifications. You can easily send a preview to your device before turning the automation on for all your users.
To achieve that, Batch simulates the In-App display by sending you a push notification with your In-App message displayed as a landing page in your app. This only lets you check that your content (text, images, buttons) is displayed properly.
#### Send a test
Open the In-App or Mobile Landing message editor, then send a test in one of two ways:
* To a **saved recipient:** click **Send test > Saved recipients**, select the recipient you want to send the test to, then click **Send test:**
* To a **one-time recipient:** click **Send test > One-time recipient**, choose the identifier type (**Custom ID**, **Installation ID** or **Push Token**), enter it in the field, then click **Send test:**
You will receive a push notification: open it to see a preview of the message you are editing on your device.
{% hint style="info" %}
To avoid entering your ID every time, save your device as a test recipient. Click **Manage recipients** in the Send a test window, or go to **Settings > Channels > Push > Test recipients**. \
You can also save a device directly from a profile: go to **Data > Find Profile**, open the device, then click **Save test device**.
{% endhint %}
If you don’t see the message right away, refer to the [**Mobile Landing**](https://doc.batch.com/developer/troubleshooting/my-mobile-landing-does-not-show) debugging article.
{% hint style="warning" %}
A test only previews how your message looks. To test the trigger, targeting or timing, turn the automation on with an **audience** limited to your test profiles.
{% endhint %}
---
# 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/in-app-messaging/how-to-send-yourself-a-test-for-in-app-messages.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.
