GitHub project

Rich push notifications

With rich push, you can do more than just send a simple notification; you can send an image, open a deep link when someone taps your message, and more!

This page is part of a setup flow for the SDK. Before you continue, make sure you've implemented previous features—i.e. you can't receive in-app notifications before you identify people!

graph LR getting-started(Install SDK) -->B(Initialize SDK) B --> identify(identify people) identify -.-> track-events(Send events) identify -.-> push(Receive push) identify -.-> rich-push(Receive Rich Push) track-events --> test-support(Write tests) push --> test-support rich-push --> test-support identify -.-> in-app(Receive in-app) in-app --> test-support click getting-started href "/integrations/sdk//getting-started/#install" click B href "/integrations/sdk//getting-started/#initialize-the-sdk" click identify href "/integrations/sdk//identify" click track-events href "/integrations/sdk//track-events/" click push href "/integrations/sdk//push" click rich-push href "/integrations/sdk//rich-push" click in-app href "/integrations/sdk//in-app" click test-support href "/integrations/sdk//test-support" style rich-push fill:#B5FFEF,stroke:#007069

Set up rich push

Rich push is included with the messaging-push-fcm SDK. For now, our rich push feature only supports images and deep links. We’ll add additional features here as we continue to develop our SDKs.

Send a rich push

To send a rich push through Customer.io, you need to use our Custom Payload editor, which takes a JSON structure. In the editor, you’ll select the type of device you want to send your message to: you can have separate payloads for Android and iOS. In our case, you’ll click Android.

The custom payload editor for a push notification

The following example shows a rich push with an image and a link. See the Deep links section below for help enabling deep links in your app.

{
  "message": {
    "notification": {
      "image": "https://thumbs.dreamstime.com/b/bee-flower-27533578.jpg",
      "title": "Hi there",
      "body": "How're you doing?"
    },
    "data": {
      "link": "remote-habits://deep?message=hello&message2=world"
    }
  }
}
  • The parent object for all push payloads.

If you use CustomerIOUrlHandler, set your SDK target to 11

Android 12 changes the way apps handle deep links when the app is in the background or closed. Our next version (3.x) will include updates to the CustomerIOUrlHandler to handle deep links gracefully. In the meantime, you should set your SDK target in your Android manifest to version 11 to ensure that your deep links work properly.

Deep links provide a way to link to a screen in your app. There are two ways to set up deep links. If you use both methods, the CustomerIOUrlHandler takes precedence.

  • Using intent filters in your AndroidManifest.xml file.

    Click here to learn more about intent filters.

    <intent-filter android:label="deep_linking_filter">
        <action android:name="android.intent.action.VIEW" />
        <category android:name="android.intent.category.DEFAULT" />
        <category android:name="android.intent.category.BROWSABLE" />
        <!-- Accepts URIs that begin with "remote-habits://deep” -->
        <data
            android:host="deep"
            android:scheme="remote-habits" />
    </intent-filter>
  • Using CustomerIOUrlHandler—a URL handler feature provided by the SDK. When configuring your CustomerIO instance, attach a listener using the setCustomerIOUrlHandler method of CustomerIO.Builder. You should do this in the entry point of the application, which is usually the Application class.
class MainApplication : Application(), CustomerIOUrlHandler {

    override fun onCreate() {
        super.onCreate()
        val builder = CustomerIO.Builder(
            siteId = "YOUR-SITE-ID",
            apiKey = "YOUR-API-KEY",
            appContext = this
        )
        builder.setCustomerIOUrlHandler(this)
        builder.build()
    }
    override fun handleCustomerIOUrl(uri: Uri): Boolean {
        // return true if you plan to handle the deep link yourself
        // return false if you want CustomerIO SDK to do it for you
        TODO("Pass the link to your Deep link managers")
    }
}

Tip

When someone taps a push notification with a deep link, the SDK calls the urlHandler specified in your CustomerIO.Builder object first. If the handler is not set or returns false, the SDK will open the link in a browser.

Test Rich Push

After you set up rich push, you should test your implementation. Use the payloads below to send a push in the Customer.io web app with a Custom Payload.

In both of the test payloads below, 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.

Rich Push Payloads

To send a rich push in Customer.io, you need to use our Custom Payload editor, which takes a JSON structure. In the editor, you’ll select the type of device you want to send your message to: you can have separate payloads for Android and iOS. In our case, you’ll click Android.

The part of your payload interpreted by the Android SDK is contained in the message.data object. This object can contain other custom data for your app, but you’ll need to do additional development to support keys beyond title, body, link, and image—all of which are handled by the SDK.

{
  "message": {
    "notification": {
      "title": "string", //(optional) The title of the notification.
      "body": "string", //The message you want to send.
      "image": "string" //https URL to an image you want to include in the notification
    },
    "data": {
      "link": "string", //Deep link in the format remote-habits://deep?message=hello&message2=world
    }
  }
}
  • The parent object for all push payloads.
Updated August 20, 2026