> For the complete documentation index, see [llms.txt](https://user.netmera.com/netmera-user-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://user.netmera.com/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/go.md).

# Push step 5: GO

Review the full mobile push campaign summary on the GO step, send a test notification to a device and finalize the campaign before it goes out.

**GO!** stage provides a summary of your campaign setup and allows you to **test and finalize your push notification** before sending it to your audience. At this stage, you can review all configuration details, including:

* **Message Content (What)** – the content or parameters you defined.
* **Selection Criteria (Who)** – the target audience filters and segments you selected.
* **Schedule (When)** – the delivery time and delivery settings.

{% @arcade/embed url="<https://app.arcade.software/share/C6Oq0KzcSRpnKDP5Dlk3>" flowId="C6Oq0KzcSRpnKDP5Dlk3" %}

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2Fa0foGLDC7psH0yaECl0d%2FScreenshot%202023-04-14%20at%2017.14.21.png?alt=media&#x26;token=a38bbdcf-3367-4067-9e9e-002fb1351e73" alt="" width="563"><figcaption><p>Step 5: GO!</p></figcaption></figure>

Message content (What), selection criteria (Who), and schedule (When) all of which you have set before can be checked before sending your notification to your audience. If you notice any details that need adjustment, click the **Change** button next to the relevant section to return and edit it easily.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FADmZhmCZWKfik2Dt0xPJ%2FScreenshot%202023-04-14%20at%2017.15.36.png?alt=media&#x26;token=8a6dd252-b380-43e5-a09b-57e8aa736897" alt="" width="563"><figcaption><p>Step 5: GO!</p></figcaption></figure>

### Test on device

On the right side of the page, you can preview how your push notification will appear on both iOS and Android devices. Before launching your campaign, you can test your notification on your **registered test devices**, on **your personal test device**, or on a **specific list of recipients** you build here. Testers are managed under **Settings >** [test-devices](/netmera-user-guide/panel-settings/settings/administration/test-devices.md)

{% hint style="info" %}
Testing your notification on multiple devices allows you to check how it appears across different operating systems, device types, and screen sizes. This helps you identify any potential display or content issues before sending the notification to your entire audience, ensuring a consistent and high-quality user experience.
{% endhint %}

{% columns %}
{% column width="50%" %}

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2F5xttuYwbSoXOs00O9Vtn%2Fimage.png?alt=media&#x26;token=1c809ab0-3787-4b8b-93f3-3df680c44371" alt=""><figcaption></figcaption></figure>
{% endcolumn %}

{% column width="50%" %}

<div align="center"><figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FulScFxqk3I7DMGpaa6ro%2FScreenshot%202023-04-14%20at%2017.16.24.png?alt=media&#x26;token=52267449-77b9-4263-8a37-da83d25e6d6f" alt="" width="375"><figcaption></figcaption></figure></div>
{% endcolumn %}
{% endcolumns %}

#### Test options

The test panel offers three options, which you combine as needed:

| Option                              | What it does                                                              |
| ----------------------------------- | ------------------------------------------------------------------------- |
| **Append \[TEST] to test messages** | Prefixes the test notification so it is distinguishable from a live send. |
| **Only Send to My Devices**         | Limits the test to the devices registered to your own panel user.         |
| **Send to Specific Users**          | Limits the test to a recipient list you build by External ID.             |

With both toggles off, **Test On Device** sends to every tester registered in Test Devices.

{% hint style="info" %}
**Only Send to My Devices** works by matching the External ID on your panel user (**Settings > Administration > Users**) with the External ID on the device. If the two do not match, **My iOS Test Devices** shows 0 and the send button stays disabled. **Send to Specific Users** does not depend on this setting.
{% endhint %}

#### Send a test to specific users

**Send to Specific Users** lets you choose exactly who receives a test, directly from the campaign screen. Instead of sending to every tester registered in Test Devices, you build a short recipient list by External ID and the test goes only to the people on it.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FZOPPHxTNm3v1WYXt9Qzz%2FEkran%20Resmi%202026-09-22%2016.29.17.png?alt=media&#x26;token=ca530f86-ec7f-4e15-bb9b-b14097e19b8e" alt="" width="563"><figcaption></figcaption></figure>

{% stepper %}
{% step %}

#### Turn on Send to Specific Users

An External ID field, an **Add to Test List** button, and a recipient list appear, and the send button is relabeled **Send a Test**.

The list always starts empty. No registered tester or device is added automatically, and the send button stays disabled until at least one recipient is on the list.
{% endstep %}

{% step %}

#### Add recipients by External ID

Enter an External ID and click **Add to Test List**. Matching is exact; leading and trailing spaces are trimmed. Each recipient is added to the list as a chip.
{% endstep %}

{% step %}

#### Select devices when prompted

If the External ID belongs to someone who is not yet a tester and has more than one push-enabled device, a device selection step opens inline, showing platform, device model, and app version for each device. Only the devices selected here are registered as testers.
{% endstep %}

{% step %}

#### Send a Test

The notification goes only to the recipients on the list. The result is reported as **X Successful, Y Failed**, counted per device.
{% endstep %}
{% endstepper %}

#### What happens for each External ID

| Case                                       | Result                                                                                       |
| ------------------------------------------ | -------------------------------------------------------------------------------------------- |
| Already registered in Test Devices         | No device selection step. The most recently active device becomes the default target.        |
| Not a tester, one push-enabled device      | The device is added to Test Devices with **Active** status and the recipient joins the list. |
| Not a tester, several push-enabled devices | The inline device selection step opens. Only the selected devices are added as testers.      |
| Not found in the application               | "The external id is not found in the current application" — not added.                       |
| No push-enabled device                     | "No push-enabled device found for this External ID." — not added.                            |
| Already on the list                        | "External ID is already in the test list." — no duplicate entry.                             |

Device selection is available only at the moment a recipient is added. To change it, remove the recipient from the list and add it again.

<figure><img src="https://1642824329-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FX6uilbEAw42gqsudlclY%2Fuploads%2FY0iN62Hyp8ykh18yRlrX%2FEkran%20Resmi%202026-09-22%2016.25.31.png?alt=media&#x26;token=4fdc10be-7cb0-48e6-a721-224b222fb573" alt="" width="375"><figcaption></figcaption></figure>

#### Things to know about the recipient list

* **The list is not saved.** It resets when the panel is closed or another campaign is opened, so a test always goes to the recipients added in that session.
* **Removing a recipient does not remove a tester.** Clearing a chip with (x) or using **Clear List** leaves the Test Devices records untouched. Testers are deleted only on the [test-devices](/netmera-user-guide/panel-settings/settings/administration/test-devices.md) page.
* **Recipients are revalidated at send time.** A recipient deleted from Test Devices, or left without a push-enabled device, counts toward **Failed**, and the send continues for everyone else.

After checking the details and testing on your device, it's finally time to send your notification to your audience. Just click on "Send" and wait for your Reports!


---

# 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://user.netmera.com/netmera-user-guide/omnichannel-engagement/mobile-push/create-mobile-push/go.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.