Set up push notifications

Updated October 15, 2024

There's a new version available!

These pages cover version 2 of our SDK, but a newer version is available. In general, we suggest that you update to the latest version to take advantage of new features and fixes.

Are you new to our SDKs? Check out the latest docs.
Otherwise, learn about updating to the latest version

Our React Native SDK supports push notifications over APN or FCM—including rich push messages with links and images. Use this page to add support for your push provider and set your app up to receive push notifications.

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 push 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 -.-> in-app(Receive in-app) click getting-started href "/sdk/react-native/getting-started/#install" click B href "/sdk/react-native/getting-started/#initialize-the-sdk" click identify href "/sdk/react-native/identify" click track-events href "/sdk/react-native/track-events/" click register-token href "/sdk/react-native/push" click push href "/sdk/react-native/push" click rich-push href "/sdk/react-native/rich-push" click in-app href "/sdk/react-native/in-app" click test-support href "/sdk/react-native/test-support" style push fill:#B5FFEF,stroke:#007069

How it works

Under the hood, our React Native SDK takes advantage of our native Android and iOS SDKs. This helps us keep the React Native SDK up to date. But, for now, it also means you’ll need to add a bit of code to support your iOS users. For Android, you’re ready to go if you followed our getting started instructions.

Before a device can receive a push notification, you must:

(iOS) Add push notification capabilities in XCode.
(iOS) Integrate push notifications: code samples on this page help you do that.
Identify a person. This associates a token with the person; you can’t send push notifications to a device until you identify the recipient.
Request, or check for, push notification permissions. If your app’s user doesn’t grant permission, notifications will not appear in the system tray.

While push providers support a number of features in their payloads, our React Native package only supports deep links and images right now. If you want to include action buttons or other rich push features, you need to add your own custom code. When writing your own custom code, we recommend that you use our SDK as it is much easier to extend than writing your own code from scratch.

Did you already set up your push providers?

To send, test, and receive push notifications, you’ll need to set up your push notification service(s) in Customer.io. If you haven’t already, set up Apple Push Notification Service (APNs) and/or Firebase Cloud Messaging (FCM).

Set up push on Android

If you followed our Getting Started instructions, you’re already set up to send standard push notifications to Android devices.

Set up push on iOS

You’ll need to add some additional code to support push notifications for iOS. You’ll need to add push capabilities in XCode and integrate push capabilities in your app.

Add push capabilities in Xcode

Before you can work with push notifications, you need to add Push Notification capabilities to your project in XCode.

In your React Native project, go to the ios subfolder and open <yourAppName>.xcworkspace.
Select your project, and then under Targets, select your main app.
Click the Signing & Capabilities tab
Click Capability.
Add Push Notifications to your app. When you’re done, you’ll see Push Notifications added to your app’s capabilities, but there are still a few more steps to finish setting things up.
Go to File > New > Target.
Select Notification Service Extension and click Next.
Enter a product name, like NotificationServiceExtension (which we use in our examples on this page), and click Finish.
When presented with the dialog below, click Cancel. This will help Xcode continue debugging your app and not just the extension you just added.

Now you have another target in your project navigator named NotificationServiceExtension. We’ll configure this extension when we Integrate Push Notifications in the following section.

Integrate push capabilities in your app

Pick your push provider (APN or FCM) and the language your native files are written in to get started (Objective C or Swift).

Open the file ios/Podfile and make the following modifications:
```
 pod 'CustomerIO/MessagingPushAPN', '~> 2.14.2'  
```
Want to automatically get the latest versions?
The example above includes the full version number. If you remove the patch and/or minor version numbers, you’ll always get the latest minor release when you run pod update --repo-update --project-directory=ios. See Updating iOS Dependencies for information about updating your Podfile.
Outside your main target, add the following line to the Podfile.
```
 pod 'CustomerIO/MessagingPushAPN', '~> 2.14.2'  
```
Open your terminal, go to your project path and run pod install --project-directory=ios. When dependencies finish installing, you should see a message like this:
```
Pod installation complete! There are X dependencies from the Podfile and Y total pods installed.
```
Open ios/<YourAppName>.xcworkspace in Xcode, and add a new Swift file to your project. In our examples, we’ve named this file MyAppPushNotificationsHandler.swift but you should use a name that makes sense to you.
Replace the file contents with the code below. We’re calling our class MyAppPushNotificationsHandler, but you might want to rename it to fit your app.

import Foundation
import CioMessagingPushAPN
import UserNotifications
import CioTracking

@objc
public class MyAppPushNotificationsHandler : NSObject {

  public override init() {}

  @objc(setupCustomerIOClickHandling:)
  public func setupCustomerIOClickHandling(withNotificationDelegate notificationDelegate: UNUserNotificationCenterDelegate) {    
    // This line of code is required in order for the Customer.io SDK to handle push notification click events. 
    // We are working on removing this requirement in a future release.
    // Remember to modify the siteId and apiKey with your own values.
    // let siteId = "YOUR SITE ID HERE"
    // let apiKey = "YOUR API KEY HERE"
    CustomerIO.initialize(siteId: siteId, apiKey: apiKey, region: Region.US) { config in
      config.autoTrackDeviceAttributes = true
    }
    
    let center  = UNUserNotificationCenter.current()
    center.delegate = notificationDelegate    
  }

  @objc(application:deviceToken:)
  public func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) {
    MessagingPush.shared.application(application, didRegisterForRemoteNotificationsWithDeviceToken: deviceToken)
  }

  @objc(application:error:)
  public func application(_ application: UIApplication, didFailToRegisterForRemoteNotificationsWithError error: Error) {
    MessagingPush.shared.application(application, didFailToRegisterForRemoteNotificationsWithError: error)
  }

  @objc(userNotificationCenter:didReceiveNotificationResponse:withCompletionHandler:)
  public func userNotificationCenter(_ center: UNUserNotificationCenter, didReceive response: UNNotificationResponse, withCompletionHandler completionHandler: @escaping () -> Void) {
    let handled = MessagingPush.shared.userNotificationCenter(center, didReceive: response,
  withCompletionHandler: completionHandler)

    // If the Customer.io SDK does not handle the push, it's up to you to handle it and call the
    // completion handler. If the SDK did handle it, it called the completion handler for you.
    if !handled {
      completionHandler()
    }
  }
}

Open AppDelegate.h and add the following import statements and the UNUserNotificationCenterDelegate delegate.

#import <RCTAppDelegate.h>
#import <UIKit/UIKit.h>
#import <UserNotifications/UserNotifications.h>
@interface AppDelegate: RCTAppDelegate<UNUserNotificationCenterDelegate>

@end

Open AppDelegate.m and import your project’s Objective-C header file.
```
#import <MyAppProject-Swift.h>
```
Inside AppDelegate’s implementation, create an object of MyAppPushNotificationsHandler (remember to substitute the name of your handler).

@implementation AppDelegate
  // Create Object of class MyAppPushNotificationsHandler
  MyAppPushNotificationsHandler* pnHandlerObj = [[MyAppPushNotificationsHandler alloc] init];
  ...

If you get a compile-time error…

See our troubleshooting section if you receive a message that reads Error: Initializer element is not a compile-time constant.

Update AppDelegate.m to register a device to the current app user and handle push notifications. See comments in the sample below to understand what the code does!

 - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
   ...

   [pnHandlerObj setupCustomerIOClickHandling:self];

   return YES;
 }

 - (void)application:(UIApplication *)application didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken {
   // Register device to receive push notifications with device token
   [pnHandlerObj application:application deviceToken:deviceToken];
 }

 - (void)application:(UIApplication *)application didFailToRegisterForRemoteNotificationsWithError:(NSError *)error {
   [pnHandlerObj application:application error:error];
 }

 // Send push notification click events to the Customer.IO SDK for processing
 - (void)userNotificationCenter:(UNUserNotificationCenter *)center didReceiveNotificationResponse:(UNNotificationResponse *)response withCompletionHandler:(void(^)(void))completionHandler {
   [pnHandlerObj userNotificationCenter:center didReceiveNotificationResponse:response withCompletionHandler:completionHandler];
 }

 // (Optional) Add the following code to show your push notifications even when your app is in the foreground.
 - (void)userNotificationCenter:(UNUserNotificationCenter* )center willPresentNotification:(UNNotification* )notification withCompletionHandler:(void (^)(UNNotificationPresentationOptions options))completionHandler {
   completionHandler(UNNotificationPresentationOptionAlert + UNNotificationPresentationOptionSound);
 }

Is your app using other SDKs that work with push notifications?

The code snippet above configures the Customer.io SDK to process all push notifications when they are clicked. If your app is using other SDKs that work with push notifications (such as expo-notifications, react-native-push-notification, or rnfirebase), you will need to follow these instructions to ensure that all SDKs work together.

In XCode, select your NotificationServiceExtension. Go to File > New > File > Swift File and click Next.
Enter a file name, like MyAppNotificationServicePushHandler, and click Create. This adds a new swift file in your extension target.

Copy the content from the snippet below and replace the code in your MyAppNotificationServicePushHandler.swift file. You might change the name of the class to fit your project. Refer the comments in the snippet below for more information.

This code is based on our iOS 2.x SDK!

If you’ve integrated based on an earlier version (your podfile targets a MessagingPushAPN version before 2.0), CustomerIO.initialize does not support the config object. It’s simply: CustomerIO.initialize(siteId: "YourSiteID", apiKey: "YourAPIKey", region: .US)

 import Foundation
 import UserNotifications
 import CioMessagingPushAPN
 import CioTracking

 @objc
 public class MyAppNotificationServicePushHandler : NSObject {

   public override init() {}

   @objc(didReceive:withContentHandler:)
   public func didReceive(_ request: UNNotificationRequest, withContentHandler contentHandler: @escaping (UNNotificationContent) -> Void) {

     // You can configure the SDK here
     // Update region to .EU for your EU-based workspace 
     CustomerIO.initialize(siteId: "YourSiteID", apiKey: "YourAPIKey", region: .US) { config in
         config.autoTrackDeviceAttributes = true
         config.logLevel = .info
     }
     MessagingPush.shared.didReceive(request, withContentHandler: contentHandler)
   }

   @objc(serviceExtensionTimeWillExpire)
   public func serviceExtensionTimeWillExpire() {
     MessagingPush.shared.serviceExtensionTimeWillExpire()
   }
 }

In your NotificationServiceExtension.m file, import the auto-generated header file—e.g. YourTargetName-Swift.h.
```
 #import <NotificationServiceExtension-Swift.h>
```

Create an object of class MyAppNotificationServicePushHandler in your NotificationServiceExtension implementation and call the functions below.

 #import "NotificationService.h"
 #import <NotificationServiceExtension-Swift.h>
 @interface NotificationService ()

 @property (nonatomic, strong) void (^contentHandler)(UNNotificationContent *contentToDeliver);
 @property (nonatomic, strong) UNMutableNotificationContent *bestAttemptContent;

 @end

 @implementation NotificationServiceExtension

 // Create object of class MyAppNotificationServicePushHandler
 MyAppNotificationServicePushHandler* nsHandlerObj = nil;

 // Initialize the object
 + (void)initialize{
   nsHandlerObj = [[MyAppNotificationServicePushHandler alloc] init];
 }
 - (void)didReceiveNotificationRequest:(UNNotificationRequest *)request withContentHandler:(void (^)(UNNotificationContent * _Nonnull))contentHandler {
   [nsHandlerObj didReceive:request withContentHandler:contentHandler];
 }

 - (void)serviceExtensionTimeWillExpire {
   [nsHandlerObj serviceExtensionTimeWillExpire];
 }

 @end

Now you can run your app on a physical device and send yourself a push notification with images and deep links to test your implementation. You’ll have to use a physical device because simulators can’t receive push notifications.

Open the file ios/Podfile and make the following modifications:
```
 pod 'CustomerIO/MessagingPushAPN', '~> 2.14.2'  
```
Want to automatically get the latest versions?
The example above includes the full version number. If you remove the patch and/or minor version numbers, you’ll always get the latest minor release when you run pod update --repo-update --project-directory=ios. See Updating iOS Dependencies for information about updating your Podfile.

Add the following line to your Podfile.

 target 'NotificationServiceExtension' do
   pod 'CustomerIO/MessagingPushAPN', '~> 2.14.2'  
 end

Open your terminal, go to your project path and run pod install --project-directory=ios. When dependencies finish installing, you should see a message like this:
```
Pod installation complete! There are X dependencies from the Podfile and Y total pods installed.
```

In your iOS subfolder, open AppDelegate.swift and add a line inside the application function. We have an example in our sample app. This is a workaround for an issue preventing iOS devices from being added to the Podfile after being identified.

  func application(_ application: UIApplication, didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?) -> Bool {

   // Important to call this code *before* you call registerForPushNotifications.
   CustomerIO.initialize(siteId: "YOUR SITE ID", apiKey: "YOUR API KEY", region: Region.US, configure: nil)

Add the following code to your app.

This sample includes a work-around

For now, it’s important that you call CustomerIO.initialize before registerForPushNotifications. This fixes an issue in which the SDK identifies the podfile, but doesn’t add a device to the podfile—preventing the user from receiving notifications.

import CioTracking
import CioMessagingPushAPN

class AppDelegate: NSObject, UIApplicationDelegate {

    func application(
         _ application: UIApplication,
         didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil
     ) -> Bool {

         // This fixes an issue in which the React Native SDK identifies
         // a profile, but an iOS device isn't added to the profile.
         // Important to call this code before calling `registerForRemoteNotifications`. 
         CustomerIO.initialize(siteId: "YOUR SITE ID", apiKey: "YOUR API KEY", region: Region.US, configure: nil)
         // It's a good practice to register for remote push when the app starts.
         // This asserts that the Customer.io SDK always has a valid device token.
         UIApplication.shared.registerForRemoteNotifications()

         return true
     }
  }

 // PUSH NOTIFICATIONS
  func application(_ application: UIApplication, didRegisterForRemoteNotificationsWithDeviceToken deviceToken: Data) {
     MessagingPush.shared.application(application, didRegisterForRemoteNotificationsWithDeviceToken: deviceToken)
 }

 func application(_ application: UIApplication, didFailToRegisterForRemoteNotificationsWithError error: Error) {
     MessagingPush.shared.application(application, didFailToRegisterForRemoteNotificationsWithError: error)
 }

Add a notification service extension to call the appropriate Customer.io functions. This lets your app display rich push notifications, including images, etc. However, if you want to enable deep links, you should continue to the Deep links section below.

This code is based on our iOS 2.x SDK!

 import UserNotifications
 import CioMessagingPushAPN
 import CioTracking

 class NotificationService: UNNotificationServiceExtension {

   override func didReceive(_ request: UNNotificationRequest,
                           withContentHandler contentHandler:
                           @escaping (UNNotificationContent) -> Void) {

     // You can configure the SDK here
     // Update region to .EU for your EU-based workspace 
     CustomerIO.initialize(siteId: "YourSiteID", apiKey: "YourAPIKey", region: .US) { config in
       config.autoTrackDeviceAttributes = true
       config.logLevel = .info
     }

     MessagingPush.shared.didReceive(request, withContentHandler: contentHandler)
   }

   override func serviceExtensionTimeWillExpire() {
     MessagingPush.shared.serviceExtensionTimeWillExpire()
   }

 }

Open the file ios/Podfile and make the following modifications:

 pod 'CustomerIO/MessagingPushFCM', '~> 2.14.2'
 pod 'Firebase'
 pod 'FirebaseMessaging'

Add the following line outside your main target.

# You may need to add this line, as required by FCM, to your Podfile if you encounter errors during 'pod install'
use_frameworks! :linkage => :static

target 'NotificationServiceExtension' do
  pod 'CustomerIO/MessagingPushFCM', '~> 2.14.2'
end

Open your terminal, go to your project path and run pod install --project-directory=ios. When dependencies finish installing, you should see a message like this:
```
Pod installation complete! There are X dependencies from the Podfile and Y total pods installed.
```
Open ios/<YourAppName>.xcworkspace in Xcode, and add a new Swift file to your project. In our examples, we’ve named this file MyAppPushNotificationsHandler.swift but you should use a name that makes sense to you.
Replace the file contents with the code below. We’re calling our class MyAppPushNotificationsHandler, but you might want to rename it to fit your app.

import Foundation
import CioMessagingPushFCM
import UserNotifications
import FirebaseMessaging
import CioTracking

@objc
public class MyAppPushNotificationsHandler : NSObject {

  public override init() {}

  @objc(setupCustomerIOClickHandling:)
  public func setupCustomerIOClickHandling(withNotificationDelegate notificationDelegate: UNUserNotificationCenterDelegate) {    
    // This line of code is required in order for the Customer.io SDK to handle push notification click events. 
    // We are working on removing this requirement in a future release.
    // Remember to modify the siteId and apiKey with your own values.    
    // let siteId = "YOUR SITE ID HERE"
    // let apiKey = "YOUR API KEY HERE"
    CustomerIO.initialize(siteId: siteId, apiKey: apiKey, region: Region.US) { config in
      config.autoTrackDeviceAttributes = true
    }
    
    let center  = UNUserNotificationCenter.current()
    center.delegate = notificationDelegate    
  }

  // Register device on receiving a device token (FCM)
  @objc(didReceiveRegistrationToken:fcmToken:)
  public func didReceiveRegistrationToken(_ messaging: Messaging, didReceiveRegistrationToken fcmToken: String?) {
    MessagingPush.shared.messaging(messaging, didReceiveRegistrationToken: fcmToken)
  }

  @objc(userNotificationCenter:didReceiveNotificationResponse:withCompletionHandler:)
  public func userNotificationCenter(_ center: UNUserNotificationCenter, didReceive response: UNNotificationResponse, withCompletionHandler completionHandler: @escaping () -> Void) {
    let handled = MessagingPush.shared.userNotificationCenter(center, didReceive: response,
  withCompletionHandler: completionHandler)

    // If the Customer.io SDK does not handle the push, it's up to you to handle it and call the
    // completion handler. If the SDK did handle it, it called the completion handler for you.
    if !handled {
      completionHandler()
    }
  }
}

Open AppDelegate.h and add the following import statements, the UNUserNotificationCenterDelegate delegate, and the FIRMessagingDelegate delegate.

#import <RCTAppDelegate.h>
#import <UIKit/UIKit.h>
#import <UserNotifications/UserNotifications.h>
#import <FirebaseMessaging/FIRMessaging.h>
@interface AppDelegate: RCTAppDelegate<UNUserNotificationCenterDelegate, FIRMessagingDelegate>

@end

In AppDelegate.m, import your project’s Objective-C Generated header file and FirebaseCore.
```
#import <MyAppProject-Swift.h>
#import <FirebaseCore.h>
```
Inside AppDelegate’s implementation, create an object of MyAppPushNotificationsHandler (remember to substitute the name of your handler).

@implementation AppDelegate
  // Create Object of class MyAppPushNotificationsHandler
  MyAppPushNotificationsHandler* pnHandlerObj = [[MyAppPushNotificationsHandler alloc] init];
  ...

If you get a compile-time error…

See our troubleshooting section if you receive a message that reads Error: Initializer element is not a compile-time constant.

Make the following updates to your AppDelegate.m file. See comments in the sample below to understand what the code does!

 - (BOOL)application:(UIApplication *)application didFinishLaunchingWithOptions:(NSDictionary *)launchOptions {
   // Configure Firebase
   [FIRApp configure];
   // Set FCM messaging delegate
   [FIRMessaging messaging].delegate = self;
   ...

   [pnHandlerObj setupCustomerIOClickHandling:self];

   return YES;
 }

 - (void)messaging:(FIRMessaging *)messaging didReceiveRegistrationToken:(NSString *)fcmToken {
   [pnHandlerObj didReceiveRegistrationToken:messaging fcmToken: fcmToken];
 }

 // Send push notification click events to the Customer.IO SDK for processing
 - (void)userNotificationCenter:(UNUserNotificationCenter *)center didReceiveNotificationResponse:(UNNotificationResponse *)response withCompletionHandler:(void(^)(void))completionHandler {
   [pnHandlerObj userNotificationCenter:center didReceiveNotificationResponse:response withCompletionHandler:completionHandler];
 }

 // (Optional) Add the following code to show your push notifications even when your app is in the foreground.
 - (void)userNotificationCenter:(UNUserNotificationCenter* )center willPresentNotification:(UNNotification* )notification withCompletionHandler:(void (^)(UNNotificationPresentationOptions options))completionHandler {
   completionHandler(UNNotificationPresentationOptionAlert + UNNotificationPresentationOptionSound);
 }

Is your app using other SDKs that work with push notifications?

In XCode, select your NotificationServiceExtension.
Select File > New > File > Swift File and click Next.
Enter a file name, like MyAppNotificationServicePushHandler, and click Create. This adds a new swift file in your extension target.

This code is based on our iOS 2.x SDK!

 import Foundation
 import UserNotifications
 import CioMessagingPushFCM
 import CioTracking

 @objc
 public class MyAppNotificationServicePushHandler : NSObject {

   public override init() {}

   @objc(didReceive:withContentHandler:)
   public func didReceive(_ request: UNNotificationRequest, withContentHandler contentHandler: @escaping (UNNotificationContent) -> Void) {

     // You may choose to configure the SDK here
     // Update region to .EU for your EU-based workspace 
     CustomerIO.initialize(siteId: "YourSiteID", apiKey: "YourAPIKey", region: .US) { config in
         config.autoTrackDeviceAttributes = true
         config.logLevel = .info
     }
     MessagingPush.shared.didReceive(request, withContentHandler: contentHandler)
   }

   @objc(serviceExtensionTimeWillExpire)
   public func serviceExtensionTimeWillExpire() {
     MessagingPush.shared.serviceExtensionTimeWillExpire()
   }
 }

In your NotificationServiceExtension.m file, import the auto-generated header file—e.g. YourTargetName-Swift.h.
```
 #import <NotificationServiceExtension-Swift.h>
```

Create an object of class MyAppNotificationServicePushHandler in your NotificationServiceExtension implementation and call the functions below.

 #import "NotificationService.h"
 #import <NotificationServiceExtension-Swift.h>
 @interface NotificationService ()

 @property (nonatomic, strong) void (^contentHandler)(UNNotificationContent *contentToDeliver);
 @property (nonatomic, strong) UNMutableNotificationContent *bestAttemptContent;

 @end

 @implementation NotificationServiceExtension

 // Create object of class MyAppNotificationServicePushHandler
 MyAppNotificationServicePushHandler* nsHandlerObj = nil;

 // Initialize the object
 + (void)initialize{
   nsHandlerObj = [[MyAppNotificationServicePushHandler alloc] init];
 }
 - (void)didReceiveNotificationRequest:(UNNotificationRequest *)request withContentHandler:(void (^)(UNNotificationContent * _Nonnull))contentHandler {
   [nsHandlerObj didReceive:request withContentHandler:contentHandler];
 }

 - (void)serviceExtensionTimeWillExpire {
   [nsHandlerObj serviceExtensionTimeWillExpire];
 }

 @end

Open the file ios/Podfile and make the following modifications:

 pod 'CustomerIO/MessagingPushFCM', '~> 2.14.2'
 pod 'Firebase'
 pod 'FirebaseMessaging'

<div class="fly-panel bg-info border-info">
<div class="fly-panel-body">
<p class="callout-head text-info mrg-b-none mrg-t-none text--bold"><svg class="icon"><use href="#pin" /></svg>&nbsp;Want to automatically get the latest versions?</p>

<div class='text-info'><p>The example above includes the full version number. If you remove the patch and/or minor version numbers, you&rsquo;ll always get the latest minor release when you run <code>pod update --repo-update --project-directory=ios</code>. See <a href="#update-ios-dependencies">Updating iOS Dependencies</a> for information about updating your Podfile.</p></div>

</div>
</div>

Add the following line to your Podfile.

 target 'NotificationServiceExtension' do
   pod 'CustomerIO/MessagingPushFCM', '~> 2.14.2'  
 end

Open your terminal, go to your project path, and run pod install --project-directory=ios. When dependencies finish installing, you should see a message like this:
```
Pod installation complete! There are X dependencies from the Podfile and Y total pods installed.
```

Update your AppDelegate.swift file to handle push notifications.

This sample includes a work-around

For now, it’s important that you call CustomerIO.initialize before registerForPushNotifications. This fixes an issue in which the SDK identifies the profile, but doesn’t add a device to the profile—preventing the user from receiving notifications.

 import CioMessagingPushFCM
 import CioTracking
 import Firebase
 import FirebaseMessaging

 class AppDelegate: NSObject, UIApplicationDelegate {
 func application(
     _ application: UIApplication,
     didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil
 ) -> Bool {
     // This fixes an issue in which the React Native SDK identifies
     // a profile, but an iOS device isn't added to the profile.
     // Important to call this code before calling `registerForRemoteNotifications`. 
     CustomerIO.initialize(siteId: "YOUR SITE ID", apiKey: "YOUR API KEY", region: Region.US, configure: nil)

     // Configure Firebase
     FirebaseApp.configure()

     // Set FCM messaging delegate
     Messaging.messaging().delegate = self

     // You should register for remote push when the app starts.
     UIApplication.shared.registerForRemoteNotifications()

     return true
   }
 }

 extension AppDelegate: MessagingDelegate {
   func messaging(_ messaging: Messaging, didReceiveRegistrationToken fcmToken: String?) {
     MessagingPush.shared.messaging(messaging, didReceiveRegistrationToken: fcmToken)
   }
 }

(Optional) Add this function to AppDelegate.swift if you want to show your push notifications even when the app is in the foreground.

 func userNotificationCenter(
 _ center: UNUserNotificationCenter,
 willPresent notification: UNNotification,
 withCompletionHandler completionHandler: @escaping (UNNotificationPresentationOptions) -> Void
 ) {
   completionHandler([.list, .banner, .badge, .sound])
 }

This code is based on our iOS 2.x SDK!

 import UserNotifications
 import CioMessagingPushFCM
 import CioTracking

 class NotificationService: UNNotificationServiceExtension {

   override func didReceive(_ request: UNNotificationRequest,
                           withContentHandler contentHandler:
                           @escaping (UNNotificationContent) -> Void) {

     // You may choose to configure the SDK here
     // Update region to .EU for your EU-based workspace 
     CustomerIO.initialize(siteId: "YourSiteID", apiKey: "YourAPIKey", region: .US) { config in
         config.autoTrackPushEvents = true
         config.logLevel = .info
     }

     MessagingPush.shared.didReceive(request, withContentHandler: contentHandler)

   }

   override func serviceExtensionTimeWillExpire() {
     MessagingPush.shared.serviceExtensionTimeWillExpire()
   }

 }

Sound in push notifications (iOS Only)

When you send a push notification to iOS devices that uses our SDK, you can opt to send the Default system sound or no sound at all. If your audience’s phone is set to vibrate, or they’ve disabled sound permissions for your app, the Default setting will cause the device to vibrate rather than playing a sound.

In most cases, you should use the Default sound setting to make sure your audience hears (or feels) your message. But, before you send sound, you should understand:

Your app needs permission from your users to play sounds. This is done by your app, not our SDKs. Here’s an example from our iOS sample app showing how to request sound permissions.
iOS users can go into System Settings and disable sound permissions for your app. Enabling the Default setting doesn’t guarantee that your audience hears a sound when your message is delivered!

We don’t support custom sounds yet

If you want to send a custom sound, you’ll need to handle it on your own, outside the SDK and use a custom payload when you set up your push notifications.

Prompt users to opt-into push notifications

Your audience has to opt into push notifications. To display the native iOS and Android push notification permission prompt, you’ll use the CustomerIO.showPromptForPushNotifications method.

You can configure push notifications to request authorization for sounds and badges as well (only on iOS). If a user opts into push notifications, the CustomerIO.showPromptForPushNotifications method will return Granted, otherwise it returns Denied as a string. If the user has not yet been asked to opt into notifications, the method will return NotDetermined (only for iOS).

var options = {"ios" : {"sound" : true, "badge" : true}}
CustomerIO.showPromptForPushNotifications(options).then(status => {
  switch(status) {
    case "Granted":
      // Push permission is granted, your app can now send push notifications to the user
      break;
    case "Denied":
      // App is not allowed to send push notifications to the user
      // You might need to explain users why your app needs permission to send notifications
      break;
    case "NotDetermined": // Only for iOS
      // Push permission status is not determined
      break;
  }
}).catch(error => {
  // Failed to show push permission prompt
  console.log(error)
})

Get a user’s permission status

To get a user’s current permission status, call CustomerIO.getPushPermissionStatus() method. This returns a promise with the current status as a string.

CustomerIO.getPushPermissionStatus().then(status => {
  console.log("Push permission status is - " + status)
})

Optional: Remove `POST_NOTIFICATIONS` permission from Android apps

By default, the SDK includes the POST_NOTIFICATIONS permission which is required by Android 13 to show notifications on Android device. However, if you do not want to include the permission because don’t use notifications, or for any other reason, you can remove the permission by adding the following line to your android/app/src/main/AndroidManifest.xml file:

<uses-permission android:name="android.permission.POST_NOTIFICATIONS" tools:node="remove"/>

Test your implementation

After you set up rich push, you should test your implementation. Below, we show the payload structure we use for iOS and Android. In general, you can use our regular rich push editor; it’s set up to send messages using the JSON structure we outline below.

If you want to fashion your own payload, you can use our custom payload.

iOS APNs payload

{
    "aps": {
        // basic iOS message and options go here
        "mutable-content": 1,
        "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
        }
    }
}

CIO object
Contains options supported by the Customer.io SDK.
- push object
  Required Describes push notification options supported by the CIO SDK.
  - image string
    The URL of an HTTPS image that you want to use for your message.
  - link string
    A deep link (to a page in your app), or a link to a web page.
aps object
A push payload intended for an iOS device.
- alert
  
  string
  A simple alert message.
  - body string
    The body of your push notification.
  - launch-image string
    The name of the launch image file you want to display. When a user launches your app, they’ll see this image or storyboard file rather than your app’s normal launch image.
  - loc-args array of [ strings ]
    An array of replacement value strings for variables in your message text. Each %@ character in the loc-key is replaced by a value from this array, in the order they appear in the message body.
  - loc-key string
    The key for a localized message string in your app’s Localizable.strings file.
  - subtitle string
    Additional information that explains the purpose of the notification.
  - subtitle-loc-args array of [ strings ]
    An array of replacement value strings for variables in your subtitle string. Each %@ character in the subtitle-loc-key is replaced by a value from this array, in the order they appear in the subtitle string.
  - subtitle-loc-key string
    The key for a localized subtitle string in your app’s Localizable.strings file.
  - title string
    The title of your push notification.
  - title-loc-args array of [ strings ]
    An array of replacement value strings for variables in your title string. Each %@ character in the title-loc-key is replaced by a value from this array, in the order they appear in the title string.
  - title-loc-key string
    The key for a localized title string in your app’s Localizable.strings files.
- badge integer
  The number you want to display on your app’s icon. Set to 0 to remove the current badge, if any.
- category string
  The notification’s type. This string must correspond to the identifier of one of the UNNotificationCategory objects you register at launch time.
- content-available integer
  The background notification flag. Use 1 without an alert to perform a silent update. 0 indicates a normal push notification.
- interruption-level string
  Indicates the importance and delivery timing of a notification.
  Accepted values:passive,active,time-sensitive,critical
- mutable-content integer
  If you use the Customer.io SDK, you must set this value to 1 to support images and “delivered” metrics from your push notifications. When the value is 1, your notification is passed to your notification service app extension before delivery. Use your extension to modify the notification’s content.
- relevance-score number
  A number between 0 and 1. The highest score is considered the “most relevant” and is featured in the notification summary.
- sound
  
  string
  The name of a sound file in your app’s main bundle or in the Library/Sounds folder of your app’s container directory. Use “default” to play the system sound. For critical alerts, you’ll pass an object instead.
  - critical integer
    1 indicates critical. 0 is not critical.
  - name string
    The name of a sound file in your app’s main bundle or in the Library/Sounds folder of your app’s container directory. Use “default” to play the system sound.
  - volume number
    The volume for a critical alert between 0 and 1, where 0 is silent and 1 is full volume.
- target-content-id string
  The identifier of the window brought forward.
- thread-id string
  An identifier to group related notifications.

iOS FCM payload

{
  "message": {
    "apns": {
      "payload": {
        "aps": {
          // basic iOS message and options go here
          "mutable-content": 1,
          "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
      }
    } 
  }
}

message object
Required The base object for all FCM payloads.
- apns object
  Required Defines a payload for iOS devices sent through Firebase Cloud Messaging (FCM).
  - headers object
    Headers defined by Apple’s payload reference that you want to pass through FCM.
  - payload object
    Required Contains a push payload.
    - CIO object
      Contains properties interpreted by the Customer.io iOS SDK.
      - push object
        Required A push payload for the iOS SDK.
        body string
        The body of your push notification.
        image string
        The URL of an HTTPS image that you want to use for your message.
        link string
        A deep link (to a page in your app), or a link to a web page.
        title string
        The title of your push notification.
    - aps object
      A push payload intended for an iOS device.
      - alert
        
        string
        A simple alert message.
        body string
        The body of your push notification.
        launch-image string
        The name of the launch image file you want to display. When a user launches your app, they’ll see this image or storyboard file rather than your app’s normal launch image.
        loc-args array of [ strings ]
        An array of replacement value strings for variables in your message text. Each %@ character in the loc-key is replaced by a value from this array, in the order they appear in the message body.
        loc-key string
        The key for a localized message string in your app’s Localizable.strings file.
        subtitle string
        Additional information that explains the purpose of the notification.
        subtitle-loc-args array of [ strings ]
        An array of replacement value strings for variables in your subtitle string. Each %@ character in the subtitle-loc-key is replaced by a value from this array, in the order they appear in the subtitle string.
        subtitle-loc-key string
        The key for a localized subtitle string in your app’s Localizable.strings file.
        title string
        The title of your push notification.
        title-loc-args array of [ strings ]
        An array of replacement value strings for variables in your title string. Each %@ character in the title-loc-key is replaced by a value from this array, in the order they appear in the title string.
        title-loc-key string
        The key for a localized title string in your app’s Localizable.strings files.
      - badge integer
        The number you want to display on your app’s icon. Set to 0 to remove the current badge, if any.
      - category string
        The notification’s type. This string must correspond to the identifier of one of the UNNotificationCategory objects you register at launch time.
      - content-available integer
        The background notification flag. Use 1 without an alert to perform a silent update. 0 indicates a normal push notification.
      - interruption-level string
        Indicates the importance and delivery timing of a notification.
        Accepted values:passive,active,time-sensitive,critical
      - mutable-content integer
        If you use the Customer.io SDK, you must set this value to 1 to support images and “delivered” metrics from your push notifications. When the value is 1, your notification is passed to your notification service app extension before delivery. Use your extension to modify the notification’s content.
      - relevance-score number
        A number between 0 and 1. The highest score is considered the “most relevant” and is featured in the notification summary.
      - sound
        
        string
        The name of a sound file in your app’s main bundle or in the Library/Sounds folder of your app’s container directory. Use “default” to play the system sound. For critical alerts, you’ll pass an object instead.
        critical integer
        1 indicates critical. 0 is not critical.
        name string
        The name of a sound file in your app’s main bundle or in the Library/Sounds folder of your app’s container directory. Use “default” to play the system sound.
        volume number
        The volume for a critical alert between 0 and 1, where 0 is silent and 1 is full volume.
      - target-content-id string
        The identifier of the window brought forward.
      - thread-id string
        An identifier to group related notifications.
    - Custom key-value pairs* any type
      Additional properties that you've set up your app to interpret outside of the Customer.io SDK.

Android payload

{
  "message": {
    "data": {
      "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
      "link": "string" //Deep link in the format remote-habits://deep?message=hello&message2=world
    }
  }
}

message
Required The parent object for all push payloads.
- android object
  Contains properties that are not interpreted by the SDK but are defined by FCM. You need to write your own code to handle these Android push features.
  - notification object
    Properties supported specifically by Android on FCM.
    - body_loc_arg string
      Variable string values used in place of the format specifiers in body_loc_key to localize the body text to the user’s current localization. See Formatting and Styling for more information.
    - body_loc_key string
      The key to the body string in the app’s string resources that you want to use to localize the body text to the user’s current localization. See String Resources for more information.
    - click_action string
      The action that occurs when a user taps on the notification. Launches an activity with a matching intent filter when a person taps the notification.
    - color string
      The notification’s icon color in #rrggbb format.
    - icon string
      Sets the notification icon to myicon for drawable resource myicon. If you don’t send this key, FCM displays the launcher icon from your app manifest.
    - sound string
      The sound that plays when the device receives the notification. Supports "default" or the filename of a sound resource bundled in your app. Sound files must reside in /res/raw/.
    - tag string
      
      Identifier to replace existing notifications in the notification drawer. If empty, each request creates a new notification.
      If you specify a tag, and a notification with the same tag is already being shown, the new notification replaces the existing one in the notification drawer.
    - title_loc_arg string
      Variable string values used in place of the format specifiers in title_loc_key to localize the title text to the user’s current localization. See Formatting and Styling for more information.
    - title_loc_key string
      The key to the title string in the app’s string resources that you want to use to localize the title text to the user’s current localization. See String Resources for more information.
- data object
  Required Contains all properties interpreted by the SDK.
  - body string
    The body of your push notification.
  - image string
    The URL of an HTTPS image that you want to use for your message.
  - link string
    A deep link (to a page in your app), or a link to a web page.
  - title string
    The title of your push notification.
- android object
  Contains properties that are not interpreted by the SDK but are defined by FCM. You need to write your own code to handle these Android push features.
  - notification object
    Properties supported specifically by Android on FCM.
    - body_loc_arg string
      Variable string values used in place of the format specifiers in body_loc_key to localize the body text to the user’s current localization. See Formatting and Styling for more information.
    - body_loc_key string
      The key to the body string in the app’s string resources that you want to use to localize the body text to the user’s current localization. See String Resources for more information.
    - click_action string
      The action that occurs when a user taps on the notification. Launches an activity with a matching intent filter when a person taps the notification.
    - color string
      The notification’s icon color in #rrggbb format.
    - icon string
      Sets the notification icon to myicon for drawable resource myicon. If you don’t send this key, FCM displays the launcher icon from your app manifest.
    - sound string
      The sound that plays when the device receives the notification. Supports "default" or the filename of a sound resource bundled in your app. Sound files must reside in /res/raw/.
    - tag string
      
      Identifier to replace existing notifications in the notification drawer. If empty, each request creates a new notification.
      If you specify a tag, and a notification with the same tag is already being shown, the new notification replaces the existing one in the notification drawer.
    - title_loc_arg string
      Variable string values used in place of the format specifiers in title_loc_key to localize the title text to the user’s current localization. See Formatting and Styling for more information.
    - title_loc_key string
      The key to the title string in the app’s string resources that you want to use to localize the title text to the user’s current localization. See String Resources for more information.
- data object
  Contains the link property (interpreted by the SDK) and additional properties that you want to pass to your app.
  - link string
    A deep link (to a page in your app), or a link to a web page.
- notification object
  Required Contains properties interpreted by the SDK except for the link.
  - body string
    The body of your push notification.
  - image string
    The URL of an HTTPS image that you want to use for your message.
  - title string
    The title of your push notification.

Copied to clipboard!

Latest features at Customer.io

Data warehouse outputs for objects and campaign names

React Native 4.0 release

Our SDKs support Firebase v11

Set up push notifications

How it works

Set up push on Android

Set up push on iOS

Add push capabilities in Xcode

Integrate push capabilities in your app

Sound in push notifications (iOS Only)

Prompt users to opt-into push notifications

Get a user’s permission status

Optional: Remove `POST_NOTIFICATIONS` permission from Android apps

Test your implementation

Latest features at Customer.io

Data warehouse outputs for objects and campaign names

React Native 4.0 release

Our SDKs support Firebase v11

Set up push notifications

How it works

Set up push on Android

Set up push on iOS

Add push capabilities in Xcode

Integrate push capabilities in your app

Sound in push notifications (iOS Only)

Prompt users to opt-into push notifications

Get a user’s permission status

Optional: Remove POST_NOTIFICATIONS permission from Android apps

Test your implementation

How can we make it better?

Optional: Remove `POST_NOTIFICATIONS` permission from Android apps