> This page is part of the [Customer.io documentation](https://docs.customer.io). For the complete index, see [llms.txt](https://docs.customer.io/llms.txt).
> Last updated: July 10, 2026

# Test push notifications

When it comes to testing your push configuration and messages for quality assurance (QA) purposes, we recommend that you keep separate development/test and production workspaces—*especially* if your workspaces don’t share configuration credentials.

For example, if you have an iOS app, you may have a sandbox environment set up to test your push notifications before you start your campaigns. This often has the same certification credentials as your production environment. We still recommend setting up a separate test workspace with the “Send to sandbox” option turned on:

[![image.png](https://docs.customer.io/images/image%28312%29.png)](#2247e7364b1abc4f53242a0ff59608a5-lightbox)

To send any type of test message, you’ll need a device token. [Here’s how to find one](/messaging/channels/push/faq#how-do-i-find-a-device-token-so-i-can-send-a-test-push-from-the-composer).

**Looking for A/B testing** for push notifications? [We've got you covered](https://customer.io/push-getting-started#ab-tests).

## Find your device token

Go to *People*, click your test user, and go to the **Devices** tab to find your device token. Hover over a device and click to copy the token to a push notification.

[![image.png](https://docs.customer.io/images/image%28309%29.png)](#a15ca71653ad0854e6f84ad76e81add5-lightbox)

## Testing your configuration

Once you have a device token, if you want to test **if your push setup is working**, we recommend that you send this message from the configuration page:

[![image.png](https://docs.customer.io/images/image%28313%29.png)](#f2b061fdfb544aefc3dc7a9e4a00c72b-lightbox)

Enter your platform type and the token you’d like to test with (see how to find those [here](/messaging/channels/push/faq#how-do-i-find-a-device-token-so-i-can-send-a-test-push-from-the-composer)), and you’ll hopefully get a test push to that device with the following content: “If you’re reading this, it means your integration with Customer.io is working!” and you’re set to start adding push notifications to your campaigns.

## Send a single push notification

If you want to see how your push notification looks on a single device, you can send a test from within the push notification composer:

[![image.png](https://docs.customer.io/images/image%28314%29.png)](#340c1ad7dddc7b950b3a1c3e09dcc4b6-lightbox)

This is the modal you should see:

[![image.png](https://docs.customer.io/images/image%28315%29.png)](#d49246b86485c846b6fe77133a904a74-lightbox)

If the message includes redacted data (that is, an admin has [hidden sensitive attribute values](/accounts/settings/team/intro-account-access/#hide-sensitive-attributes) from you), then test sends will not show the values for those sensitive attributes.

*   *   [Find your device token](#find-your-device-token)
    *   [Testing your configuration](#testing-your-configuration)
    *   [Send a single push notification](#single-message-qa-test)

Copy page

Copy page [Download .md](/messaging/channels/push/qa-testing.md)

Is this page helpful?

![](https://docs.customer.io/images/export-success.png) ![](https://docs.customer.io/images/export-failure.png)

# How can we make it better?

Close

Do you need help from Customer.io support?  No  
 Yes

What part of Customer.io do you need help with? 

How can we improve this page?

Email (optional):  Please provide a valid email address

 I am not a bot

 

We appreciate your feedback!

Our support team will contact you as soon as possible