# Testing Your External Client App Push Configuration

To run a quick test of your push notification setup, use the Send Test Notification page. Troubleshoot round-trip push notifications in a synchronous mechanism without having to configure custom notification types, Apex calls, or REST calls. You can also gain insights into what’s going on behind the scenes in the asynchronous environment of real-world push notifications.

| Required Editions                                                                                                                                                                                                    |
| -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Available in: both Salesforce Classic ([not available in all orgs](https://help.salesforce.com/s/articleView?id=xcloud.overview_edition_lex_only.htm&type=5)) and Lightning Experience                               |
| External client apps can be created in: **Group**, **Professional**, **Enterprise**, **Essentials**, **Performance**, **Unlimited**, and **Developer** Editions Connected Apps can be installed in: **All** Editions |

<sfdocstbl><table>

<col>
</col>
<col>
</col>
<thead>
  <tr>
    <th>
      User Permissions Needed
    </th>
    <th>
       
    </th>
  </tr>
</thead>
<tbody>
  <tr>
    <td>
      To send a push notification from the Test Push Notifications page:
    </td>
    <td>
      <p>
        Author Apex
      </p>
      <p>
        AND
      </p>
      <p>
        Create, edit, and delete External Client Apps
      </p>
    </td>
  </tr>
</tbody>
</table></sfdocstbl>

## About the Send Test Notification Page

The Send Test Notification page uses information from your Apple Push Notification Service (APNS) or Firebase Cloud Messaging (FCM) for Android setup to configure a synchronous push mechanism. You select a device to receive the push notification by entering a connection token string. If you don’t know the token string, you can use the Search tool to select from the list of devices that are registered for your external client app. The Search tool automatically displays the five most recently registered devices. You can also enter a user’s name to search for devices that are registered to that user.

For Android FCM push notifications, you can select the Dry Run option to test your FCM setup. This option sends the notification to the FCM server but doesn’t forward it to a device.

You can use any JSON-formatted payload for a dry-run test. For example, you can start with something as simple as `{"alert": "test"}`.

Each push attempt returns a status message that indicates success or failure.

To reach the test page:

1. In Setup, enter `External Client App` in the Quick Find box, then select **External Client App Manager**.
2. Click **Edit Settings** in the action menu for your external client app.
3. Click **Send test notification** next to Supported Push Platform. This link appears only if you’ve configured your external client app to support mobile push notifications.

:::important
Successful test push notifications apply against the push notification daily limits for your organization.
:::

- **[Check a User's Mobile Push Registrations](/docs/platform/mobile-push-notifications/guide/pns-check-user-device-registrations.md)**

  From a User page in your organization, an administrator can easily check which of the user’s devices are currently registered for push notifications. Checking the registrations may help you troubleshoot push notification failures.