Why does my push campaign have no direct opens?

Here is everything you should check if the number of opens is too low for your push campaigns.

If your campaigns have a very low number of Opens, something may be misbehaving in your integration.

The problem can come from different places depending on the platform:

iOS: Possible SDK Conflict

On iOS, the issue may be caused by a conflict with another SDK that automatically integrates with your application delegate (such as but not limited to Firebase).

You can fix this by manually integrating Batch. If you implement your own UNUserNotificationCenterDelegate, you need to make sure that Batch is integrated into it (learn more about this advance setting).

Android: Possible Integration Issue

On Android, it can mean that Batch is not integrated into all activities. If you are using a Custom Receiver (or Interceptor) and displaying your own notifications, you might not have copied the data Batch needs in the intent.

If you use a Custom Receiver, we recommend checking if the interceptor meets your needs instead. It greatly reduces the likeliness of this kind of errors. ​

Also, Opens might not be detected if the splash screen ends too soon. We recommend using the feature Excluding activities to exclude the splash screen from Batch's lifecycle handling.

Testing Your Integration

Once you have made the fixes, you can test your integration by taking the following steps:

1. Run the Xcode or Android Project on a device in debug mode.

2. Send a notification while outside of the app (in background mode, do not kill the app).

3. Open the notification.

4. Check your Xcode logs or your logcat. You should see the following logs: "App was opened from a Batch push".