GitHub project

Test your push implementation

After you set up push notifications, you should send some test messages. You can send messages through the Customer.io push composer. If your app is set up to send more than the standard title, body, image, and link, you’ll need to send a custom payload.

The custom payload editor for a push notification

The payloads below represent what your app can expect to receive from Customer.io. If you use a custom payload, you’ll need to use the format(s) below to make sure that the SDK receives your message properly.

When testing, you should:

  • Set the link to the deep link URL that you want to open when your tester taps your notification.
  • Set the image to the URL of an image you want to show in your notification. It’s important that the image URL starts with https:// and not http:// or the image might not show up.
JSON
{
    "aps": {
        // basic iOS message and options go here
        "mutable-content": 1,
        "sound": "default",
        "alert": {
            "title": "string", //(optional) The title of the notification.
            "body": "string" //(optional) The message you want to send.
        }
    },
    "CIO": {
        "push": {
            "link": "string", //generally a deep link, i.e. my-app:://...
            "image": "string" //HTTPS URL of your image, including file extension
        }
    }
}
  • A push payload intended for an iOS device.
  • Contains options supported by the Customer.io SDK.
JSON
{
  "message": {
    "apns": {
      "payload": {
        "aps": {
          // basic iOS message and options go here
          "mutable-content": 1,
          "sound": "default",
          "alert": {
            "title": "string", //(optional) The title of the notification.
            "body": "string" //(optional) The message you want to send.
           }
        },
        "CIO": {
          "push": {
            "link": "string", //generally a deep link, i.e. my-app://... or https://yourwebsite.com/...
            "image": "string" //HTTPS URL of your image, including file extension
          }
        }
      },
      "headers": {
        // (optional) headers to send to the Apple Push Notification Service.
        "apns-priority": 10
      }
    }
  }
}
  • messageobjectrequired
    The base object for all FCM payloads.
    • apnsobjectrequired
      Defines a payload for iOS devices sent through Firebase Cloud Messaging (FCM).
      • Contains a push payload.
      • headersobject
        Headers defined by Apple's payload reference that you want to pass through FCM.

Check delivery metrics

To check that Customer.io reports Delivered, send a broadcast or automation message to your own profile, and check that message for Delivered. Test sends from the composer or Workspace settings might not create delivery metrics, so they can’t confirm that delivery tracking works. Your app only reports Delivered for iOS push notifications if it includes a Notification Service Extension (NSE). A message can appear on your device without the NSE, so seeing the notification doesn’t confirm that delivery tracking works.

If your message appears but doesn’t report Delivered, see iOS delivery reporting and Problems with rich push notifications.

Updated November 9, 2026