Mobile push notifications sent through Campaign traditionally rely on the APNS or FCM providers. Industry-wide reports show that only 30 to 40% of these traditional pushes are delivered. If you use SDK versions 3.8.2 and above, you can check the deliverability report metrics from the Reports > Reports (classic) > Report center > Mobile reports push notifications. For more information, see Push deliverability reporting for marketers and Mobile reports.

There are various factors and reasons why traditional push notifications are not delivered, such as the following:

• Delivering push notifications to Chinese devices.
• Certain manufacturer devices disable the push service channel in favor of their own push services, such as OPPO.
• Devices disable the push channel to manage power usage.

Campaign mobile provides the Certify Send feature as an enhanced channel to send mobile push notifications that avoid the common failures that traditional provider channels encounter. It increases the deliverability of push notifications. The certify send feature requires Campaign mobile SDK versions 3.8.2 and above.

Note: For iOS, you must have the push notification extension added to your project. If you enable the Certify Send feature without the push notification extension, the notifications will be delivered/displayed twice. For more information, see Add the iOS notification service framework to your project.

Note: Enabling the certify send feature will increase your Campaign billing. Certify Send feature is currently in beta, contact your customer success focal for more information.

You can certify the notifications for Simple, Simple + Inbox, and Data notification types.

1. Go to Add settings page to configure the Delivery Options settings.
2. Enable the Certify Send toggle. Once the certify toggle is enabled, you can set the expiration time limit for the delivery of this notification to be certified. You can set a time limit of up to 336 hours (2 weeks in hours).

When you enable Certify Send for notifications, the notifications are first pushed through the traditional providers; if the notifications are dropped or fails to deliver, Campaign checks if the notifications are certified. If they are certified, the notifications are then delivered using the same pull technology used for our inbox and in-app features.

Note: The synchronization does not require the inbox plugin.

When the SDK synchronizes with the server, the notifications are delivered and displayed as simple notifications. In Android applications, the SDK server sync typically happens at a set time defined in the SDK. It is set to sync every 24 hrs by default. You can use the Sync API to change the server sync time. For more information, see Android SDK message sync API.

Note: When you set the expiration time limit for the notification to be certified, you must take into account the server sync set in the SDK. 

In iOS applications, since there is no background processing, the server sync happens upon foreground activation.

For example, if the user hasn't opened the app for two weeks:

• In Android: The server sync is always active in the background.
• In iOS: The server sync occurs only when the user opens the app.

Whenever the server sync happens, the notification's duration time for certify send is verified, and the notification is only displayed if it has not expired.

Note: The notification delivery will be time offset, but the notifications are pulled down to the device and presented to the customer. Whether the users see the notification and take action is not guaranteed as they may still ignore the notification. If the device doesn't pull the notification until after they expire, the notifications will not be displayed.

Certified pushes create UB events that are available in the query tool and Acoustic Exchange.

You can also view the deliverability report metrics for certified push notifications from the mobile reports page. You can filter the reports and view metrics for all certified notifications and data-only notifications based on whether they were delivered by APNs/FCM providers or server sync. You can also filter for certified push notifications that were not delivered due to expired notifications or devices that have disabled push notifications. For more information, see Push deliverability reporting for marketers.